Hi Nick,
On 18/02/2016 13:32, Nick Coghlan
wrote:
On 17 February 2016 at 04:37, Chris
Withers
wrote:
So, RHEL7, for worse or worse, ships with Python 2.7.5.
On 02/18/2016 12:00 PM, Daniel Holth wrote:
> On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote:
>> I saw PEP-0516 go through check-ins, and had a question about the
>> pypa.json portion of the proposal -- namely, why are we using a
>> .json file?
>>
>> I presume this is a file that will be
I'm still pulling for RFC 822 format :)
On Thu, Feb 18, 2016, 14:33 Nathaniel Smith wrote:
> On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote:
> > Greetings!
> >
> > I saw PEP-0516 go through check-ins, and had a question about the
> pypa.json
> > portion
On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote:
> Greetings!
>
> I saw PEP-0516 go through check-ins, and had a question about the pypa.json
> portion of the proposal -- namely, why are we using a .json file?
>
> I presume this is a file that will be created by hand, and
Greetings!
I saw PEP-0516 go through check-ins, and had a question about the
pypa.json portion of the proposal -- namely, why are we using a .json file?
I presume this is a file that will be created by hand, and while json is
not as ugly as xml, it's certainly not pretty.
Can we not use an
On 18 February 2016 at 13:48, Nick Coghlan wrote:
>> Yes, twine is a good, concrete example.
>
> I believe tools like pyp2rpm, conda skeleton, py2dsc and fpm also rely on
> that static sdist metadata (I'm not 100% sure on that, but it would make
> sense for them to do so).
Yes PKG-INFO is reasonably useful and easy to hand-edit. It would be easy
to maintain. If you were doing it manually the only thing you would need to
update frequently would be the version number.
On Thu, Feb 18, 2016 at 8:48 AM Nick Coghlan wrote:
> On 18 February 2016 at
On 18 February 2016 at 07:30, Paul Moore wrote:
> On 17 February 2016 at 21:01, Nathaniel Smith wrote:
> > On Feb 17, 2016 4:44 AM, "Donald Stufft" wrote:
> >>
> > [...]
> >> You could say that using twine to handle the uploading is a
On 17 February 2016 at 04:37, Chris Withers wrote:
> Hi All,
>
> (Apologies for copying in the maintainers of the two backports and
> django-netfields directly, I'm not sure you're on this distutils list...)
>
> This is painful and horrible, and I wish pip would prevent
>
Strong +1 for all Donald's proposals.
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
> On Feb 18, 2016, at 5:26 AM, Paul Moore wrote:
>
> [1] One downsides of managing PEPs as PRs against the packaging specs
> is that there is no easy quotable term to refer to them by - we could,
> and probably should, use the PR number. And as a consequence, it's
> hard to
On 17 February 2016 at 22:58, Robert Collins wrote:
>> The latter option is far easier (we're basically almost there) but it
>> will *not* suit build tools that can't (or won't) generate a sdist
>> that conforms to PEP 314 (i.e., contains PKG-INFO).
>
> I still don't
12 matches
Mail list logo