On 16 January 2014 01:25, Chris Jerdonek chris.jerdo...@gmail.com wrote:
Is there a description somewhere of the plan for what
packaging-related information will be covered in docs.python.org
proper (and the stages for getting there), and which information will
be off-loaded to the
On 16 Jan 2014 18:08, Paul Moore p.f.mo...@gmail.com wrote:
On 16 January 2014 01:25, Chris Jerdonek chris.jerdo...@gmail.com wrote:
Is there a description somewhere of the plan for what
packaging-related information will be covered in docs.python.org
proper (and the stages for getting
On 16 January 2014 09:40, Nick Coghlan ncogh...@gmail.com wrote:
Audrey Roy's cookiecutter project is just such a tool (although her
default config is far from minimal - setup.py, GitHub, ReadTheDocs, tox,
Travis, documentation skeleton, etc. It's all reasonable recommendations,
though)
On Jan 16, 2014, at 9:20 AM, Daniel Holth dho...@gmail.com wrote:
Has anyone ever written a setup.py that was *not* copy-and-pasted from
somewhere else?
On Thu, Jan 16, 2014 at 5:17 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 January 2014 09:40, Nick Coghlan ncogh...@gmail.com wrote:
Has anyone ever written a setup.py that was *not* copy-and-pasted from
somewhere else?
On Thu, Jan 16, 2014 at 5:17 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 January 2014 09:40, Nick Coghlan ncogh...@gmail.com wrote:
Audrey Roy's cookiecutter project is just such a tool (although her
On Thu, Jan 16, 2014 at 09:20:43AM -0500, Daniel Holth wrote:
Has anyone ever written a setup.py that was *not* copy-and-pasted from
somewhere else?
Presumably the 1st setup.py had to have been written by hand somehow.
Marius Gedminas
--
Five words to strike fear into the heart of any
On 16 January 2014 15:02, Marcus Smith qwc...@gmail.com wrote:
I still think that the best resource available would be a basic best
practice project template for a simple pure-python package with a few
tests. I started putting one together myself
(https://github.com/pfmoore/sampleproject).
On 16 January 2014 15:14, Paul Moore p.f.mo...@gmail.com wrote:
I'm happy to do that, if people think it's sufficiently representative
of best practice (and if they don't, they can always improve it :-))
Done.
___
Distutils-SIG maillist -
Like you said, it's more elaborate than you might expect at first, but all
the comments make it very clear.
I like it.
On Thu, Jan 16, 2014 at 7:14 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 January 2014 15:02, Marcus Smith qwc...@gmail.com wrote:
I still think that the best resource
On that note, the PUG index currently feels a little overwhelming
The main index is 2 levels deep currently. Let me drop it to one level and
see how that looks.
I personally like a deep index as my main entry point to docs, but I can
see it being a bit much.
the point of view of someone
I don't have a clear picture of the split myself but it seems to me
that docs.python.org should be the master reference data for
*distutils*. That's somewhat screwed, though, as we're recommending
use of setuptools, and setuptools messes round so invasively with
distutils that the
Could we stop cross-posting this thread to both pypa-dev and
distutils-sig? Seems like it belongs on pypa-dev to me, but I don't
really care so long as it isn't cross-posted to both :-)
Carl
___
Distutils-SIG maillist - Distutils-SIG@python.org
ok, let's do distutils-sig.
true, it is a pypa project, but non-pypa people are already in this
thread, and I imagine all pypa-dev people are on distutils-sig.
On Thu, Jan 16, 2014 at 9:49 AM, Carl Meyer c...@oddbird.net wrote:
Could we stop cross-posting this thread to both pypa-dev and
docs.python.org should provide a distutils reference, and drop the
Installing/Distributing Python Modules guides in deference to the PUG.
to be clearer, the 2 * Python Modules guides have some good content, but
I think it needs to be pushed into the distutils reference, not presented
in a
On 16 January 2014 17:46, Marcus Smith qwc...@gmail.com wrote:
I don't have a clear picture of the split myself but it seems to me
that docs.python.org should be the master reference data for
*distutils*. That's somewhat screwed, though, as we're recommending
use of setuptools, and setuptools
That makes sense. But I think it's a case of getting people to what
they need as quickly as possible (and having the details available
further on, if they need them). The pip documentation is great for
this. Go to the front page, first thing you see is Quickstart. First
thing that hits your
On 16 January 2014 18:39, Marcus Smith qwc...@gmail.com wrote:
given my previous arguments, if we have a Quickstart, I would just have it
contain links to the pip setuptools quickstarts (and wheel too I guess).
Yeah... Although I question the value of setting up a chain of 3 links
to get
Here's an example of what I was meaning (please excuse the fact that I
know nearly nothing about restructured text, and completely nothing
about Sphinx...):
https://github.com/pfmoore/python-packaging-user-guide/tree/quickstart
well, ok, if we keep it really tight (like 2 pages or less),
I've just released version 0.1.7 of distlib on PyPI [1]. For newcomers,
distlib is a library of packaging functionality which is intended to be
usable as the basis for third-party packaging tools.
The main changes in this release are as follows:
Fixed issue #39: Changed to work in a
I’ve just released virtualenv 1.11.1rc2 and pip 1.5.1rc1, it fixes a number
of issues with the latest releases of each one, but most importantly:
* virtualenvs created with —system-site-packages not getting pip or
setuptools installed into it
* Errors about setuptools being too old
* Bug fixes
20 matches
Mail list logo
