-
-
Notifications
You must be signed in to change notification settings - Fork 291
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
Support Python 2.6 #40
Conversation
This string formatting nicety was introduced in Python 2.7 and breaks Python 2.6 users like myself. This change is forwards and backwards compatible between all Pythons.
Thanks for the catch! Was unaware that this formatting quirk failed in 2.6. This points out the need for better integration/coverage testing of the pex tool itself since 2.6 is supported and definitely covered by the rest of the tests. |
You're welcome! Awesome tool, btw, we're playing with pex now to see if we can use it to manage a somewhat large codebase. So far it is looking great. |
Cool. If you have any questions or need any help, don't hesitate to reach out. We don't have a pex-specific mailing list but the pants mailing list can be pretty helpful, and there's usually at least one of us in #pypa or #pypa-dev. |
Hi @wickman, I know the change was trivial, but do you have any idea when a new version of |
unless i'm missing something, '{}'.format(foo) is not a syntax error in Python 2.6 so the toolchain should work just fine (just that the 'pex --version' command is broken.) we should still roll a patch release but i just wanted to be clear that you shouldn't be blocked. |
You're right, it's not a syntax error, but every command I try to run on Python 2.6 yields an error like this.
|
Ah, ok. I see. Thanks for the context. I'll get this published asap. |
Published. Thanks for the prod. |
Right on. Thank you for the quick response! |
This string formatting nicety was introduced in Python 2.7 and breaks
Python 2.6 users like myself. This change is forwards and backwards
compatible between all Pythons.