On 21 June 2013 15:52, Nick Coghlan wrote:
> In the meantime, once sdist 2.0 is officially defined in a PEP, build
> tools will be able to define their own metadata extensions to record
> whatever they want in the sdist files. They'll also be free to add
> arbitrary files to the dist-info directo
On 22 June 2013 00:10, Paul Moore wrote:
> On 21 June 2013 14:30, Ronald Oussoren wrote:
>>
>> > Yes, I was thinking more of the sdist side - and also of how a pure
>> > Python package can specify whether separate wheels are needed for Python 2
>> > and Python 3, for example. There's a wheel-spec
On 21 June 2013 14:30, Ronald Oussoren wrote:
> > Yes, I was thinking more of the sdist side - and also of how a pure
> Python package can specify whether separate wheels are needed for Python 2
> and Python 3, for example. There's a wheel-specific setup.cfg extension for
> this, but should it be
devpi, the caching pypi server and its optional upload/test/install helper
tool, just got a devpi-0.9.2 release. See the full updated docs here:
http://doc.devpi.net
Apart from some streamlining, there is a new upload option::
devpi upload --from-dir path/to/dir [--only-latest]
which
On 21 Jun, 2013, at 1:24, Nick Coghlan wrote:
> >
> > 1. Python setup.py sdist and python setup.py dist_info will be changed to
> > generate pymeta.json files. But that will be for Python 3.4 only (there's a
> > big problem if this doesn't make it into 3.4...). Unless there's a
> > distutils
On 21 Jun, 2013, at 14:21, Paul Moore wrote:
> On 21 June 2013 12:35, Nick Coghlan wrote:
> The quick compatibility check is actually part of the wheel file
> naming specification (it's covered by the compatibility tags defined
> in PEP 425).
>
> Yes, I was thinking more of the sdist side - an
On 21 June 2013 12:35, Nick Coghlan wrote:
> The quick compatibility check is actually part of the wheel file
> naming specification (it's covered by the compatibility tags defined
> in PEP 425).
>
Yes, I was thinking more of the sdist side - and also of how a pure Python
package can specify whe
On 21 Jun 2013 19:52, "Paul Moore" wrote:
>
> On 21 June 2013 00:24, Nick Coghlan wrote:
>>
>> > How close am I to reality here?
>>
>> Close, except that this is explicitly an "ecosystem first" plan, with the
>> standard library playing catch up later. That's the big reason I sought (and
>> rec
On 21 June 2013 00:24, Nick Coghlan wrote:
> > How close am I to reality here?
>
> Close, except that this is explicitly an "ecosystem first" plan, with the
> standard library playing catch up later. That's the big reason I sought
> (and received) agreement at this year's language summit for us t
