New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundlebuilder --lib mishandles frameworks #39858
Comments
The bundlebuilder command-line argument --lib is supposed to be able to include frameworks in the resulting Mac app. Unfortunately, the aliases in the resulting framework copy are all broken. For an example of this, use --lib to include Tcl.framework and then look through the framework in the resulting application package. Frameworks normally have quite a few handy aliases (such as .../Versions/Current) and all the aliases I tried were broken. I'm not entirely sure if this actually breaks anything. The one app I've managed to build with standalone=True and use of --lib to include the Tk and Tcl frameworks runs fine on my Mac (which has Python, Tcl and Tk frameworks installed) but fails with "True undefined" on another Mac running Jaguar that I happened to have handy. This 2nd problem may be a separate bug or user error on my part. I'm not yet sure. |
Logged In: YES I cannot repeat this, neither with 2.4a1 nor with 2.3: I always get /usr/bin/python /System/Library/Frameworks/Python.framework/ and I got symlinks just fine. Feel free to reopen the bug report if you |
Logged In: YES I see. I also can follow the links using the unix command line. However, I So there is a bug in bundlebuilder (or it is exposing a bug in Finder), but its |
Logged In: YES That's weird... Could it be that the original has symlinks that somehow Any ideas? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: