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 *theor
On Fri, Sep 21, 2012 at 12:24 AM, Nick Coghlan wrote:
> On Fri, Sep 21, 2012 at 1:58 PM, PJ Eby wrote:
>> On Thu, Sep 20, 2012 at 10:51 PM, Nick Coghlan wrote:
>>> On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft
>>> wrote:
Maybe that's just me though.
>>>
>>> Nope, it's "In the face of am
On Fri, Sep 21, 2012 at 1:58 PM, PJ Eby wrote:
> On Thu, Sep 20, 2012 at 10:51 PM, Nick Coghlan wrote:
>> On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft
>> wrote:
>>> Maybe that's just me though.
>>
>> Nope, it's "In the face of ambiguity, refuse the temptation to guess"
>> applied to dependen
On Thu, Sep 20, 2012 at 10:51 PM, Nick Coghlan wrote:
> On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft
> 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 dependency links guessing anything
On Fri, Sep 21, 2012 at 12:08 PM, Donald Stufft 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 setuptools.
If *others* w
This is a timely discussion for me because I need to get back to packaging
some tools for RHEL/Centos that we have as dependencies. The tools are
available on pypi or from a git repository. They seem to be available in
older versions for Fedora 14 but not in EPEL or other sites for
RHEL/Centos.
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
On Thu, Sep 20, 2012 at 4:53 PM, Donald Stufft 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 requirements and their
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 git+h
> 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
On Sun, Sep 16, 2012 at 9:40 PM, Daniel Holth 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 can be foun
On Thu, Sep 20, 2012 at 1:32 PM, Erik Bray wrote:
> On Wed, Sep 19, 2012 at 9:26 PM, Daniel Holth wrote:
>> I am implementing requirements-in-setup.cfg for wheel because there is
>> no place to put environment markers in setup.py
>>
>> The Requires-Dist: lines in PKG-INFO use ; to separate enviro
On Wed, Sep 19, 2012 at 9:26 PM, Daniel Holth wrote:
> I am implementing requirements-in-setup.cfg for wheel because there is
> no place to put environment markers in setup.py
>
> The Requires-Dist: lines in PKG-INFO use ; to separate environment
> markers from the dep name. Is setup.cfg supposed
13 matches
Mail list logo
