On May 9, 2014, at 6:16 PM, Barry Warsaw wrote:
> A follow up.
>
> I've done a fair bit of prototyping a solution, and with Donald's gracious
> help and feedback, I think I have a plan that will work and should be
> compliant with policy. I'm beginning to make changes to various DPMT packages
A follow up.
I've done a fair bit of prototyping a solution, and with Donald's gracious
help and feedback, I think I have a plan that will work and should be
compliant with policy. I'm beginning to make changes to various DPMT packages
to build the whole stack, but I'm only uploading the simpler
On May 7, 2014, at 11:35 AM, Barry Warsaw wrote:
> The stuff vendorized inside there don't have to have the
> dist-info directories, so perhaps they don't need to be wheeled at all, but
> they *do* have to be vendorized because of technicalities in the way pip works
> within a virtual environme
On May 07, 2014, at 12:21 PM, Matthias Klose wrote:
>pip is a specical case here, because we want to mimic the wheel packages which
>come with python upstream. these can't be shipped in the debian python source
>package, but they are needed to make the pyvenv command work. so we have to
>construc
[Matthias Klose, 2014-05-07]
> Am 07.05.2014 10:16, schrieb Piotr Ożarowski:
> > [Barry Warsaw, 2014-05-07]
> >> Generating the wheels during package build is pretty easy I think. You
> >> just
> >> B-D on python*-wheel (which just got approved from NEW) and then if the
> >> package uses setuptoo
Am 07.05.2014 10:16, schrieb Piotr Ożarowski:
> [Barry Warsaw, 2014-05-07]
>> Generating the wheels during package build is pretty easy I think. You just
>> B-D on python*-wheel (which just got approved from NEW) and then if the
>> package uses setuptools, you just add something like:
>>
>> py
[Barry Warsaw, 2014-05-07]
> Generating the wheels during package build is pretty easy I think. You just
> B-D on python*-wheel (which just got approved from NEW) and then if the
> package uses setuptools, you just add something like:
>
> python3 setup.py bdist_wheel -d \
> debian/pyt
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 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
9 matches
Mail list logo
