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
Py2app 88 #103
Py2app 88 #103
Conversation
related to issue #88 |
Also - my apologies for not TDDing this. If I get some time, I'll try to add some test coverage for run-tests.py and start-app.py |
This was just rebased against master, so it should have the most recent plugins. |
I need to add a note to the docs about the fact that this requires a brewed or non-system python to be used. |
(venv)$ pip install -r dev-requirements.txt | ||
(venv)$ pip install -r py2app-requirements.txt | ||
|
||
The to build the the application, run ``make`` from the root directory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Then to build the application
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lekhajee Thanks for noticing this - I've fixed it.
Just as an FYI - I'm going to be on vacation until next Friday, so I'll have sporadic access to email. |
I'm going to try to setup tox to run the builder, then I'll put this up for review. |
Fantastic. Thanks. |
In order to get travis to build the application using an OSX builder, there is a feature flag that needs to be enabled manually by travis's staff. They ask that you send them an email requesting the OSX builder feature be turned on. The steps are detailed at http://docs.travis-ci.com/user/multi-os/#Manual-intervention-required. If this is ok, could you @glyph or @lekhajee send an email to them asking them to turn the feature on? Thanks! |
It looks like it (it being the py2app portion of setup.py) isn't pulling in the mimic/twisted/plugins/mimic.py file. |
Could this be because we added the |
I'm pretty sure it isn't - it is happening locally as well. |
Hrm. But only after merging master? |
Now I'm getting this: https://gist.github.com/glyph/fcc354d38222dd9d4ae0 |
It looks this is the commit that introduced the change: b71c72f |
Do you get the same error if you run ./build-app.sh? |
No, then I get |
Looking inside
|
Yes - I just found that as well! It looks like it generates a dropin.cache, but nothing else.. |
It's possible that |
Without |
With the scan_code error, which version of py2app are you running? If I remember correctly, newer versions of py2app have an issue. I need to pin the py2app dependencies, instead of just minimum requirements. |
Yeah, I was just messing around with py2app versions… |
I think the version with the error was 0.9? |
When pinning it to 0.8.1, I now get this at the end of the test run:
|
I'm now getting odd framework python build errors on my machine. |
I think one thing that might be screwing it up is the fact that if py2app is available at all, the |
I am deeply confused. py2app appears to have regressed in some way since the last time I was looking at this; and not just regressed in its current version, but older versions are broken too. I really don't understand what is going on, but clearly that |
I'm quite confused myself. One way or another, I'm now getting the following error, using the same steps as before. 2015-03-03 21:46:09.077 run-tests[33926:88303] A Python runtime not could be located. You may need to install a framework build of Python, or edit the PyRuntimeLocations array in this application's Info.plist file. The env is still being built using the system python too. |
one of the many bugs blocking us seems to be https://bitbucket.org/ronaldoussoren/py2app/issue/156/virtualenvpy-recipe-calls-methods-renamed so I've commented there... |
Since that bug is in the |
Merged #191, which includes all the commits from this PR. Closing this. Thanks! |
Pushing the first stages of the commit. As of right now, py2app will build the application, but when run, it will fail with the following error:
I'm pretty sure this is related to how my start-app.py script is working.
Also this has no tests, which will obviously need to change.