Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 12 February 2016 at 01:19, Barry Warsaw wrote: > On Feb 11, 2016, at 01:58 PM, Nick Coghlan wrote: >>Anyway, the core point is wanting to ensure we can automate not only >>"direct to binary" installation with Python specific tools, but also >>the "convert to alternate source

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On Feb 11, 2016, at 01:58 PM, Nick Coghlan wrote: >Hmm, I got the py2dsc reference from https://wiki.debian.org/Python/Packaging >but the newer https://wiki.debian.org/Python/LibraryStyleGuide doesn't appear >to mention any particular way of generating the initial packaging skeleton >from the

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 11 February 2016 at 11:12, Barry Warsaw wrote: > On Feb 10, 2016, at 10:08 AM, Paul Moore wrote: > >>But those people will then find that distributing their sources isn't >>something that flit covers, so they'll make up their own approach (if it were >>me, I'd probably just

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On Thu, Feb 11, 2016 at 12:23 PM, Brett Cannon wrote: > > > On Thu, 11 Feb 2016 at 10:01 M.-A. Lemburg wrote: > >> On 11.02.2016 17:48, Donald Stufft wrote: >> > >> >> On Feb 11, 2016, at 11:08 AM, M.-A. Lemburg wrote: >> >> >> >> Then why

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

I'm a little over this particular subthread of the topic - we did it to death late last year. So apologies in advance if I get a little terse. On 12 February 2016 at 05:08, M.-A. Lemburg wrote: > On 10.02.2016 19:46, Robert Collins wrote: >> On 11 February 2016 at 02:36, M.-A.

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On Feb 11, 2016 1:23 PM, "Robert Collins" wrote: > > I'm a little over this particular subthread of the topic - we did it > to death late last year. So apologies in advance if I get a little > terse. > > On 12 February 2016 at 05:08, M.-A. Lemburg

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10.02.2016 19:46, Robert Collins wrote: > On 11 February 2016 at 02:36, M.-A. Lemburg wrote: > >>> Currently what pip does is to >>> invoke >>> >>> $ python setup.py egg_info --egg-base $TEMPDIR >>> >>> to get the metadata. It is not possible to get the metadata without

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 12 February 2016 at 08:45, Wes Turner wrote: > > On Feb 11, 2016 1:23 PM, "Robert Collins" wrote: >> We already have a command which outputs the needed info (as egg info) >> - and my draft PEP has a similar one, using PEP427 wheel METADATA >>

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

> On Feb 11, 2016, at 11:08 AM, M.-A. Lemburg wrote: > > Then why not fix distutils' sdist command to add the needed > information to PKG-INFO and rely on it ? > > Or perhaps add a new distutils command which outputs the needed > information as JSON file and fix the sdist

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 11.02.2016 17:48, Donald Stufft wrote: > >> On Feb 11, 2016, at 11:08 AM, M.-A. Lemburg wrote: >> >> Then why not fix distutils' sdist command to add the needed >> information to PKG-INFO and rely on it ? >> >> Or perhaps add a new distutils command which outputs the needed

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On Thu, 11 Feb 2016 at 10:01 M.-A. Lemburg wrote: > On 11.02.2016 17:48, Donald Stufft wrote: > > > >> On Feb 11, 2016, at 11:08 AM, M.-A. Lemburg wrote: > >> > >> Then why not fix distutils' sdist command to add the needed > >> information to PKG-INFO and rely

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

Let me speak up about a different and pressing problem: the problem of source code that is not distributed with a GNU automake script. First, any alleged "software" that doesn't use GNU automake is not real and/or should be considered closed source. Second, automake is the best build system that I

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10.02.2016 14:00, Oscar Benjamin wrote: > On 10 February 2016 at 12:21, M.-A. Lemburg wrote: >>> So "easy to achieve" still needs someone to take the time to deal with >>> these sorts of issue. It's the usual process of the people willing to >>> put in the effort get to choose

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 11 February 2016 at 01:21, M.-A. Lemburg wrote: > On 10.02.2016 12:10, Paul Moore wrote: >> On 10 February 2016 at 10:23, M.-A. Lemburg wrote: >>> IMO, that's easy to achieve, though, with the existing de-facto >>> standard interface we already have: the

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On Feb 10, 2016, at 10:08 AM, Paul Moore wrote: >But those people will then find that distributing their sources isn't >something that flit covers, so they'll make up their own approach (if it were >me, I'd probably just point people at the project's github account). > >Once people get set up

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 11 February 2016 at 13:48, Nick Coghlan wrote: > On 11 February 2016 at 08:12, Barry Warsaw wrote: >> It's not impossible to migrate to something else, but it's impractical to >> migrate to dozens of something elses. Right now, if we can count on PyPI >>

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

> Paul Moore writes: > >> But as I said in my response to Nathaniel, it may be that all that is >> needed is some context in the PEP explaining how we require[1] people >> to upload source to PyPI in the new world where we support build >> systems which don't have a "sdist"

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10 February 2016 at 10:23, M.-A. Lemburg wrote: > IMO, that's easy to achieve, though, with the existing de-facto > standard interface we already have: the setup.py command line API. > We'd just need to publish the minimal set of commands and options, > installer will want to

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10 February 2016 at 09:34, M.-A. Lemburg wrote: > I'm not sure I'm parsing your comment correctly, but if you are > suggesting that PyPI should no longer allow supporting > non-open-source packages, this is definitely not going to > happen. Not at all. Although as far as I

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10.02.2016 11:08, Paul Moore wrote: > On 10 February 2016 at 09:34, M.-A. Lemburg wrote: >> I'm not sure I'm parsing your comment correctly, but if you are >> suggesting that PyPI should no longer allow supporting >> non-open-source packages, this is definitely not going to >>

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10.02.2016 12:10, Paul Moore wrote: > On 10 February 2016 at 10:23, M.-A. Lemburg wrote: >> IMO, that's easy to achieve, though, with the existing de-facto >> standard interface we already have: the setup.py command line API. >> We'd just need to publish the minimal set of

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10 February 2016 at 12:21, M.-A. Lemburg wrote: >> So "easy to achieve" still needs someone to take the time to deal with >> these sorts of issue. It's the usual process of the people willing to >> put in the effort get to choose the direction (which is also why I >> just

Re: [Distutils] Ensuring source availability for PyPI entries / PEP: Build system abstraction for pip/conda etc

On 10 February 2016 at 22:21, M.-A. Lemburg wrote: > Wait. You are missing the point that the setup.py interface > already does work, so no extra effort is needed. All that's > needed is some documentation of what's currently being used, > so that other tools can support the