I have been doing some experimentation and preparation for trying to solve bug
#732703, i.e. fixing ensurepip in Python 3.4 and thus the pyvenv command.
Why this is tricky: ensurepip in the Python stdlib bundles two wheels, one for
setuptools and another for pip, and these wheels get installed int
On May 6, 2014, at 6:28 PM, Barry Warsaw wrote:
> PEP 427 does discourage direct import from wheels[1] but for the things we
> care about immediately, the two conditions should not affect us (i.e. no C
> extensions, and no bad use of __file__) so I think we could get away with it.
> I'm open to
On May 06, 2014, at 06:39 PM, Donald Stufft wrote:
>For what it’s worth, I’m the one who pushed hard against ZipImport
>capabilities being codified in PEP427 and I can say that we are *incredibly*
>unlikely to remove that ability without introducing a better way of achieving
>that. So even if the
On 05/06/2014 01:57 AM, Christophe Siraut wrote:
> Hi,
>
> I worked on the following bugs and need a quality review:
>
> - #705275 ITA: python-django-contact-form -- extensible contact-form
>application for Django
> - #686171 python-django-piston: Django 1.4 compatibility [RC]
>
> You can
* Thomas Goirand , 2014-05-07, 14:29:
Same remark also for the binary Depends: of python-django-piston. But
this time, if dh_python2 (see below) automatically adds the
dependencies by replacing ${python:Depends}, then probably you can
completely remove the manual dependencies (this will have to
5 matches
Mail list logo
