Re: [Distutils] distlib and wheel metadata

> On Feb 15, 2017, at 11:44 AM, Donald Stufft wrote: > > >> On Feb 15, 2017, at 1:15 PM, Daniel Holth > > wrote: >> >> I also get a little frustrated with this kind of proposal "no pins" which I >> read as "annoy the publisher to

Re: [Distutils] Python installation not working

h...@python.org is also set up to provide this kind of assistance. On Wed, Feb 15, 2017 at 10:05 AM Brett Cannon wrote: > This actually isn't the right place to ask for installation help, Chitra > (this list is about how to package up Python projects). For general support >

Re: [Distutils] distlib and wheel metadata

> On Feb 15, 2017, at 1:15 PM, Daniel Holth wrote: > > I also get a little frustrated with this kind of proposal "no pins" which I > read as "annoy the publisher to try to prevent them from annoying the > consumer". As a free software publisher I feel entitled to annoy the

Re: [Distutils] distlib and wheel metadata

I also get a little frustrated with this kind of proposal "no pins" which I read as "annoy the publisher to try to prevent them from annoying the consumer". As a free software publisher I feel entitled to annoy the consumer, an activity I will indulge in inversely proportional to my desire for

Re: [Distutils] distlib and wheel metadata

On Feb 15, 2017 07:41, "Nick Coghlan" wrote: >> pipenv borrows the Ruby solution to modeling this by having Pipfile >> for abstract dependency declarations and Pipfile.lock for concrete >> integration testing ones, so the idea here is to propagate that model >> to pydist.json

Re: [Distutils] distlib and wheel metadata

Thanks for your reply, it was very helpful. On 15 February 2017 at 16:55, Freddy Rietdijk wrote: > Larger applications that have many dependencies that are fixed have been > kept out of Nixpkgs for now. I notice here (and in a few other places) you talk about

Re: [Distutils] distlib and wheel metadata

On Wed, Feb 15, 2017 at 11:55 AM, Freddy Rietdijk wrote: > > Sort of repeating my earlier question, but how often does this happen > in reality? > > From a quick check in our repo we have patched about 1% of our packages to > remove the constraints. We have close to 2000

Re: [Distutils] Python installation not working

This actually isn't the right place to ask for installation help, Chitra (this list is about how to package up Python projects). For general support questions you should email python-list. On Wed, 15 Feb 2017 at 05:11 Chitra Dewan via Distutils-SIG < distutils-sig@python.org> wrote: > Hello, > >

Re: [Distutils] distlib and wheel metadata

> Sort of repeating my earlier question, but how often does this happen in reality? >From a quick check in our repo we have patched about 1% of our packages to remove the constraints. We have close to 2000 Python packages. We don't necessarily patch all the constraints, only when they collide

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 15:50, Freddy Rietdijk wrote: > It's quite frustrating as a downstream having to deal with packages where > versions are pinned unnecessarily and therefore I've also requested on the > Setuptools tracker a flag that ignores constraints [1] (though I

Re: [Distutils] distlib and wheel metadata

On Wed, Feb 15, 2017, at 03:40 PM, Daniel Holth wrote: > It would make sense to go ahead and delete the obsolete fields, I'm > sure they were overlooked because they are not common in the wild. > > From PEP 345: > * Deprecated fields: >* Requires (in favor of Requires-Dist) >*

Re: [Distutils] distlib and wheel metadata

> Maybe it would help if you have a concrete example of a scenario where they would benefit from having this distinction? In the Nix package manager (source distribution with binary substitutes) and Nixpkgs package set we typically require the filename and hash of a package. In our expressions we

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 15:41, Nick Coghlan wrote: > My goal with the split is to get to a state where: > > - exactly zero projects on PyPI use "==" or "===" in their requires > metadata (because PyPI explicitly prohibits it) > - the vast majority of projects on PyPI *don't*

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 15:58, Paul Moore wrote: > On 15 February 2017 at 14:11, Nathaniel Smith wrote: >>> It's mainly a matter of incorporating >>> https://caremad.io/posts/2013/07/setup-vs-requirement/ into the core >>> data model, as this distinction

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 15:11, Nathaniel Smith wrote: > On Wed, Feb 15, 2017 at 5:27 AM, Nick Coghlan wrote: >> It's mainly a matter of incorporating >> https://caremad.io/posts/2013/07/setup-vs-requirement/ into the core >> data model, as this distinction

Re: [Distutils] distlib and wheel metadata

IIUC PEP 345, the predecessor of PEP 426, replaced Requires with Requires-Dist because the former was never very well specified, easier to re-name the field rather than redefine it. bdist_wheel's egg-info conversion assumes the only useful requirements are in the setuptools requires.txt. It would

Re: [Distutils] distlib and wheel metadata

> the full METADATA format is documented in the pre-JSON revision of PEP 426. Can you confirm which exact revision in the PEPs repo you mean? I could guess at 0451397. That version does not refer to a field "Requires" (rather, the more recent "Requires-Dist"). Your conversion function reads

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 14:11, Nathaniel Smith wrote: >> It's mainly a matter of incorporating >> https://caremad.io/posts/2013/07/setup-vs-requirement/ into the core >> data model, as this distinction between abstract development >> dependencies and concrete deployment

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 14:00, Wes Turner wrote: > On Wed, Feb 15, 2017 at 5:33 AM, Nick Coghlan wrote: >> I asked Daniel to *stop* using pydist.json, since wheel was emitting a >> point-in-time snapshot of PEP 426 (which includes a lot of >>

Re: [Distutils] distlib and wheel metadata

Wheel puts everything important in METADATA, except entry_points.txt. The requirements expressed there under 'Requires-Dist' are reliable, and the full METADATA format is documented in the pre-JSON revision of PEP 426. At runtime, once pkg_resources parses it, *.egg-info and *.dist-info look

Re: [Distutils] distlib and wheel metadata

On Wed, Feb 15, 2017 at 5:27 AM, Nick Coghlan wrote: > On 15 February 2017 at 12:58, Nathaniel Smith wrote: >> On Wed, Feb 15, 2017 at 3:33 AM, Nick Coghlan wrote: >>> - "requires": list where entries are either a string containing a PEP

Re: [Distutils] distlib and wheel metadata

On 15 February 2017 at 12:58, Nathaniel Smith wrote: > On Wed, Feb 15, 2017 at 3:33 AM, Nick Coghlan wrote: >> - "requires": list where entries are either a string containing a PEP >> 508 dependency specifier or else a hash map contain a "requires" key >> plus

Re: [Distutils] distlib and wheel metadata

On Wed, Feb 15, 2017 at 5:33 AM, Nick Coghlan wrote: > On 14 February 2017 at 21:21, Vinay Sajip via Distutils-SIG > wrote: > > > > > >> I thought the current status was that it's called metadata.json > >> exactly *because* it's not standardized,

[Distutils] Python installation not working

Hello, I am beginner in Python I am facing problems in installing Python 3.5  on my windows vista x32 machine.I downloaded python-3.5.2.exe from Python.org. It is downloaded as an exe. When I try to install it via  "Run as administrator" , nothing happens.  Same behavior with 3.6 version 

[Distutils] py2exe package for 2.7

Hi Good Afternoon, This is Venkat from HCL Technologies. Actually I have created executable file(test.exe) by using py2exe package on python 2.7 version on Windows. After that I have ran my application from the path C:\Python27\dist\test.exe, It was executed and working properly. But the

Re: [Distutils] distlib and wheel metadata

On Wed, Feb 15, 2017 at 3:33 AM, Nick Coghlan wrote: > - "requires": list where entries are either a string containing a PEP > 508 dependency specifier or else a hash map contain a "requires" key > plus "extra" or "environment" fields as qualifiers > - "integrates":

Re: [Distutils] distlib and wheel metadata

On 14 February 2017 at 21:21, Vinay Sajip via Distutils-SIG wrote: > > >> I thought the current status was that it's called metadata.json >> exactly *because* it's not standardized, and you *shouldn't* look at >> it? > > > Well, it was work-in-progress-standardised