-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
pants 0.0.32 cannot build/run python3 binaries #1658
Comments
This requires a fix in pex which requires upgrading to the pex 1.0.0 series. I'm tackling the upgrade 1st in #1440 |
Many thanks, John. Really appreciate your time on this. Let us know if there's anything we can do to help! |
Working the underlying issue in pex here: |
Noting that pex RB https://rbcommons.com/s/twitter/r/2350/ is approved but pants still needs pex RB https://rbcommons.com/s/twitter/r/2341/ before it can upgrade to the new pex to solve this issue. I haven't forgotten about you over here. |
Thanks so much for the updates, John! |
The fix for pex resolves in https://rbcommons.com/s/twitter/r/2341/ is now in master so pants can consume the #127 compiler fix that will get this issue resolved with the next pex release. |
I just confirmed that my repro case above now work using a pantsbuild.pants sdist locally released from https://rbcommons.com/s/twitter/r/2438/: $ ./dist/main.pex
Traceback (most recent call last):
File "main.py", line 2, in <module>
print(1 / 0)
ZeroDivisionError: division by zero
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File ".bootstrap/_pex/pex.py", line 319, in execute
File ".bootstrap/_pex/pex.py", line 254, in _wrap_coverage
File ".bootstrap/_pex/pex.py", line 286, in _wrap_profiling
File ".bootstrap/_pex/pex.py", line 362, in _execute
File ".bootstrap/_pex/pex.py", line 420, in execute_entry
File ".bootstrap/_pex/pex.py", line 425, in execute_module
File "/usr/lib/python3.4/runpy.py", line 185, in run_module
return _run_code(code, {}, init_globals, run_name, mod_spec)
File "/usr/lib/python3.4/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "main.py", line 4, in <module>
raise RuntimeError("Something bad happened") from exc
RuntimeError: Something bad happened The https://rbcommons.com/s/twitter/r/2438/ change (upgrade to pex 1.0.1) will land before Friday and we now have regular pants releases every Friday, so this should all work for you by EOW. |
This is a minimal upgrade that does not engage any of the new pex features, but it does pull in a bugfix necessary to squash: #1658 Testing Done: CI went green here: https://travis-ci.org/pantsbuild/pants/builds/69824504 Bugs closed: 1440, 1658, 1761 Reviewed at https://rbcommons.com/s/twitter/r/2438/
Fix in master @ 3287103 This should go out in the 0.0.35 release on Friday, 7/10/15 |
Much gratitude, John! We'll upgrade to 0.0.35 and take it for a spin :) The team really appreciates your time! 👍 |
It works with python3 ? |
@Allan-Nava : Yep! Twitter is currently rolling out python3 internally, so it's a good time to give it a try. |
Perfect! But is working with django framework?
2018-03-27 19:46 GMT+02:00 Stu Hood <[email protected]>:
… @Allan-Nava <https://github.com/Allan-Nava> : Yep! Twitter is currently
rolling out python3 internally, so it's a good time to give it a try.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1658 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVdMg5DpOmQJU_6TCkFdVBbTv-npvKWmks5tinrbgaJpZM4E9zMC>
.
|
I do not know. That would be a separate ticket. |
@stuhood I used django 1.11.5 with python3 |
As initially reported by Grant here: https://groups.google.com/d/topic/pants-devel/dr_vUO_gG_4/discussion
I did a minimal repo like so:
Setup a pants python repo:
Setup Grant's case:
Repro the run ... not quite so fast
URG - tracked here: Pants requires ivy for a python-only project #940
Add the nailgun tool dep:
5.) Really do the repro:
The text was updated successfully, but these errors were encountered: