On Fri, Sep 21, 2012 at 2:57 PM, PJ Eby p...@telecommunity.com wrote:
This is no more guesswork than the PyPI /simple index discovery protocol is.
You have zero idea what's at the end of a URL link. You're just hoping
it's the file you expect.
Cheers,
Nick.
--
Nick Coghlan |
On Fri, Sep 21, 2012 at 3:06 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Sep 21, 2012 at 2:57 PM, PJ Eby p...@telecommunity.com wrote:
This is no more guesswork than the PyPI /simple index discovery protocol is.
You have zero idea what's at the end of a URL link. You're just hoping
On Fri, Sep 21, 2012 at 1:28 AM, Donald Stufft donald.stu...@gmail.comwrote:
On Friday, September 21, 2012 at 12:57 AM, PJ Eby wrote:
As far as the practicality vs. purity question, Python has already had
Provides/Requires in the metadata format for several years, and it
contained all the
Let's agree that there is/should be an --ignore flag for
dependency_links.txt and argue about whether it is on by default.
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
On Fri, Sep 21, 2012 at 1:28 AM, Donald Stufft donald.stu...@gmail.com wrote:
These fields were _not_ for saying that it required a particular
distribution/project
and _were_ for saying it requires a particular module or package (in the
import sense).
Yes, but that was still sufficient
On Fri, Sep 21, 2012 at 11:04 AM, Brett Cannon br...@python.org wrote:
Agreed. While I might have a suggestion to grab some project from some place
on e.g. bitbucket,
This might've been buried in the thread, but that's *precisely* what
dependency links are: a *suggestion* as to where a
On Friday, September 21, 2012 at 11:14 AM, PJ Eby wrote:
Yes, but that was still sufficient information to implement a
dependency system, in theory. Specifically, it would have worked for
the case where all projects are on PyPI and have correct metadata.
If you assume that condition, you can
On Fri, Sep 21, 2012 at 12:59 PM, Donald Stufft donald.stu...@gmail.com wrote:
How would you take ``requires: tastypie`` and turn it into
`django-tastypie`?
By matching Requires with Provides at the index level. That is, by
having PyPI index packages' Provides so that you can search for
On Friday, September 21, 2012 at 3:09 PM, PJ Eby wrote:
On Fri, Sep 21, 2012 at 12:59 PM, Donald Stufft donald.stu...@gmail.com
(mailto:donald.stu...@gmail.com) wrote:
How would you take ``requires: tastypie`` and turn it into
`django-tastypie`?
By matching Requires with Provides at
On Fri, Sep 21, 2012 at 3:25 PM, Donald Stufft donald.stu...@gmail.com wrote:
And when you have 2 packages that both provides: tastypie? Which is a real
world occurence.
Hey, I didn't say it would work in practice, I said it would work in
*theory*. ;-) The point was, if you only have to have
FWIW bdist_wheel knows about dependency_links.txt. It deletes it if it
is only whitespace, otherwise it keeps it.
As of last May when I downloaded pypi,
16984 of the latest sdists
13028 have dependency_links.txt
The 211 in the postscript have a non-empty dependency_links.txt
These point at
On Thu, Sep 20, 2012 at 4:24 PM, Daniel Holth dho...@gmail.com wrote:
And they answer most of your questions. A few call-outs below:
dependency_links.txt: url's of the package's dependencies. Speak up if
you use this; it is very surprising, and has a much better replacement
with pip --index
On Fri, Sep 21, 2012 at 12:57 AM, PJ Eby p...@telecommunity.com wrote:
I'm not seeing how a documented file discovery protocol is
guesswork. Perhaps you've not read the documentation? e.g.:
http://peak.telecommunity.com/DevCenter/setuptools#dependencies-that-aren-t-in-pypi
On Fri, Sep 21, 2012 at 3:06 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Sep 21, 2012 at 2:57 PM, PJ Eby p...@telecommunity.com wrote:
This is no more guesswork than the PyPI /simple index discovery protocol is.
You have zero idea what's at the end of a URL link. You're just hoping
On Sun, Sep 16, 2012 at 9:40 PM, Daniel Holth dho...@gmail.com wrote:
I've been chatting to Chris McDonough a bit as well, and one
potentially useful thing would be to clearly document the
setuptools/distribute metadata precisely as it is generated today.
The official docs for all egg formats
And they answer most of your questions. A few call-outs below:
dependency_links.txt: url's of the package's dependencies. Speak up if
you use this; it is very surprising, and has a much better replacement
with pip --index options and requirements files.
I will check to see how often this is
On Thursday, September 20, 2012 at 4:24 PM, Daniel Holth wrote:
It's probably a style thing, but I like to distribute this information
out-of-band. So as the author of foopackage (an application) I list
all the requirements and their requirements and where they can be
found, including
On Thu, Sep 20, 2012 at 4:53 PM, Donald Stufft donald.stu...@gmail.com wrote:
On Thursday, September 20, 2012 at 4:24 PM, Daniel Holth wrote:
It's probably a style thing, but I like to distribute this information
out-of-band. So as the author of foopackage (an application) I list
all the
On Thursday, September 20, 2012 at 9:24 PM, PJ Eby wrote:
As a practical matter (and practicality beats purity), it's sometimes
necessary to provide this information in order to depend on packages
that aren't cataloged in PyPI, or when third-party build support is
required, and your goal is to
On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft donald.stu...@gmail.com wrote:
Maybe that's just me though.
Nope, it's In the face of ambiguity, refuse the temptation to guess
applied to dependency metadata. It's one of the core philosophical
differences between the stdlib and systems like
On Thu, Sep 20, 2012 at 10:51 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft donald.stu...@gmail.com
wrote:
Maybe that's just me though.
Nope, it's In the face of ambiguity, refuse the temptation to guess
applied to dependency metadata.
How are
On Fri, Sep 21, 2012 at 12:24 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Sep 21, 2012 at 1:58 PM, PJ Eby p...@telecommunity.com wrote:
On Thu, Sep 20, 2012 at 10:51 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft donald.stu...@gmail.com
On Friday, September 21, 2012 at 12:57 AM, PJ Eby wrote:
As far as the practicality vs. purity question, Python has already had
Provides/Requires in the metadata format for several years, and it
contained all the features that were needed for a pure dependency
resolution system. In *theory*
I've been chatting to Chris McDonough a bit as well, and one
potentially useful thing would be to clearly document the
setuptools/distribute metadata precisely as it is generated today.
Currently these formats are entirely implicit in the implementation of
the code that reads and writes them,
24 matches
Mail list logo
