I'm working on Python 3 versions of pip and virtualenv, with the idea of keeping a common codebase for Python 2.x and 3.x so as to make maintenance easier. To date, I've made good progress: My port of pip (working with my port of virtualenv) passes 100 tests (2 are skipped) on Python 3.2 and 3.3a0. However, one roadblock is that distribute 0.6.14 doesn't work with Python 3.2 and later, because of the "abiflags" configuration parameter which is new in 3.2. Toshio Kuratomi has a fix for this checked in, and my tests have used a tarball of the distribute 0.6-maintenance tip with a name of distribute-0.6.15dev.tar.gz. It would be good if an official 0.6.15 release of distribute were made, incorporating that fix, now that 3.2 is out. Can someone tell me if there is a plan to release a 0.6.15, and if so, when it will be? Regards, Vinay Sajip P.S. IMO Toshio Kuratomi's fix could be better implemented as self.config_vars['abiflags'] = getattr(sys, 'abiflags', '') in the same block as all the other self.config_vars[...] assignments.
On Sat, Mar 12, 2011 at 6:05 AM, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
I'm working on Python 3 versions of pip and virtualenv, with the idea of keeping a common codebase for Python 2.x and 3.x so as to make maintenance easier. To date, I've made good progress: My port of pip (working with my port of virtualenv) passes 100 tests (2 are skipped) on Python 3.2 and 3.3a0.
Yay!
However, one roadblock is that distribute 0.6.14 doesn't work with Python 3.2 and later, because of the "abiflags" configuration parameter which is new in 3.2. Toshio Kuratomi has a fix for this checked in, and my tests have used a tarball of the distribute 0.6-maintenance tip with a name of distribute-0.6.15dev.tar.gz.
It would be good if an official 0.6.15 release of distribute were made, incorporating that fix, now that 3.2 is out.
+1 I'm going to be working on a buildout port this week and will need a Python 3.2-compatible port too! Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton
On Sat, Mar 12, 2011 at 07:04, Jim Fulton <jim@zope.com> wrote:
On Sat, Mar 12, 2011 at 6:05 AM, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
I'm working on Python 3 versions of pip and virtualenv, with the idea of keeping a common codebase for Python 2.x and 3.x so as to make maintenance easier. To date, I've made good progress: My port of pip (working with my port of virtualenv) passes 100 tests (2 are skipped) on Python 3.2 and 3.3a0.
Yay!
However, one roadblock is that distribute 0.6.14 doesn't work with Python 3.2 and later, because of the "abiflags" configuration parameter which is new in 3.2. Toshio Kuratomi has a fix for this checked in, and my tests have used a tarball of the distribute 0.6-maintenance tip with a name of distribute-0.6.15dev.tar.gz.
It would be good if an official 0.6.15 release of distribute were made, incorporating that fix, now that 3.2 is out.
+1
I'm going to be working on a buildout port this week and will need a Python 3.2-compatible port too!
Also my previous effort for buildout exposed a bug, which I fixed, so we need a new release anyway. :-) So a new distribute release would be very appreciated.
I will cut a release during the sprint, unless someone involved in the project would like to volunteer to do a release. Cheers On Sat, Mar 12, 2011 at 7:46 AM, Lennart Regebro <regebro@gmail.com> wrote:
On Sat, Mar 12, 2011 at 07:04, Jim Fulton <jim@zope.com> wrote:
On Sat, Mar 12, 2011 at 6:05 AM, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
I'm working on Python 3 versions of pip and virtualenv, with the idea of keeping a common codebase for Python 2.x and 3.x so as to make maintenance easier. To date, I've made good progress: My port of pip (working with my port of virtualenv) passes 100 tests (2 are skipped) on Python 3.2 and 3.3a0.
Yay!
However, one roadblock is that distribute 0.6.14 doesn't work with Python 3.2 and later, because of the "abiflags" configuration parameter which is new in 3.2. Toshio Kuratomi has a fix for this checked in, and my tests have used a tarball of the distribute 0.6-maintenance tip with a name of distribute-0.6.15dev.tar.gz.
It would be good if an official 0.6.15 release of distribute were made, incorporating that fix, now that 3.2 is out.
+1
I'm going to be working on a buildout port this week and will need a Python 3.2-compatible port too!
Also my previous effort for buildout exposed a bug, which I fixed, so we need a new release anyway. :-) So a new distribute release would be very appreciated. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | http://ziade.org
On Sat, Mar 12, 2011 at 8:54 AM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
I will cut a release during the sprint, unless someone involved in the project would like to volunteer to do a release.
Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton
Tarek Ziadé <ziade.tarek <at> gmail.com> writes:
I will cut a release during the sprint, unless someone involved in the project would like to volunteer to do a release.
It's great that a 0.6.15 has been uploaded to PyPI, but there are still a couple of problems with it: 1. distribute_setup.py expects a .tar.gz, and fails with a 404 error because only the .zip is available. 2. Although the distribute_setup.py in the .zip refers to 0.6.15, the http://python-distribute.org/distribute_setup.py is still referring to 0.6.14. I've logged this as an issue on your Bitbucket repo (#193). Regards, Vinay Sajip
On Wed, Mar 16, 2011 at 10:41 AM, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
Tarek Ziadé <ziade.tarek <at> gmail.com> writes:
I will cut a release during the sprint, unless someone involved in the project would like to volunteer to do a release.
It's great that a 0.6.15 has been uploaded to PyPI, but there are still a couple of problems with it:
1. distribute_setup.py expects a .tar.gz, and fails with a 404 error because only the .zip is available. 2. Although the distribute_setup.py in the .zip refers to 0.6.15, the http://python-distribute.org/distribute_setup.py is still referring to 0.6.14.
I've logged this as an issue on your Bitbucket repo (#193).
Should be fixed now --
Regards,
Vinay Sajip
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | http://ziade.org
On Sat, Mar 12, 2011 at 11:05:50AM +0000, Vinay Sajip wrote:
P.S. IMO Toshio Kuratomi's fix could be better implemented as
self.config_vars['abiflags'] = getattr(sys, 'abiflags', '')
in the same block as all the other self.config_vars[...] assignments.
Committed as: diff -r f64c2d57df43 setuptools/command/easy_install.py --- a/setuptools/command/easy_install.py Tue Feb 22 12:05:49 2011 -0800 +++ b/setuptools/command/easy_install.py Sat Mar 12 06:47:42 2011 -0800 @@ -202,14 +202,10 @@ 'prefix': prefix, 'sys_exec_prefix': exec_prefix, 'exec_prefix': exec_prefix, + # Only python 3.2+ has abiflags + 'abiflags': getattr(sys, 'abiflags', ''), } - try: - self.config_vars['abiflags'] = sys.abiflags - except AttributeError: - # Only python-3.2+ has sys.abiflags - self.config_vars['abiflags'] = '' - if HAS_USER_SITE: self.config_vars['userbase'] = self.install_userbase self.config_vars['usersite'] = self.install_usersite -Toshio
participants (5)
-
Jim Fulton -
Lennart Regebro -
Tarek Ziadé -
Toshio Kuratomi -
Vinay Sajip