On Mon, Feb 4, 2013 at 3:38 AM, Donald Stufft donald.stu...@gmail.com wrote:
On Sunday, February 3, 2013 at 8:32 AM, Nick Coghlan wrote:
Keywords (optional)
---
A list of additional whitespace separated keywords to be used to assist
searching for the distribution in a
On Monday, February 4, 2013 at 8:01 AM, Nick Coghlan wrote:
Keywords are supposed to be short, and the field name is Keywords
rather than Keyword, so I don't think it's worth the hassle of
changing it. I at least clarified it to be explicitly
whitespace-separated in this version (that was
Nick Coghlan ncoghlan at gmail.com writes:
With Donald Stufft's assistance, I've created a new draft of PEP 426.
For the moment I'm listed as a co-author and no longer as
BDFL-Delegate - there's a separate discussion on python-dev about
that.
I think it's worth inserting in the Example
With Donald Stufft's assistance, I've created a new draft of PEP 426.
For the moment I'm listed as a co-author and no longer as
BDFL-Delegate - there's a separate discussion on python-dev about
that.
The major substantive changes from Daniel's last draft are to:
- remove the dependency on PEP 386
On Sun, Feb 3, 2013 at 11:32 PM, Nick Coghlan ncogh...@gmail.com wrote:
With Donald Stufft's assistance, I've created a new draft of PEP 426.
For the moment I'm listed as a co-author and no longer as
BDFL-Delegate - there's a separate discussion on python-dev about
that.
In addition to the
On 4 Feb 2013 00:30, Lele Gaifax l...@metapensiero.it wrote:
Nick Coghlan ncogh...@gmail.com writes:
…
Summary of Differences From \PEP 345
Spurious backslash?
Deliberate - it stops the automatic link generation in the PEP HTML
generator.
…
It
On Sunday, February 3, 2013 at 8:32 AM, Nick Coghlan wrote:
Keywords (optional)
---
A list of additional whitespace separated keywords to be used to assist
searching for the distribution in a larger catalog.
Example::
Keywords: dog puppy voting election
I wonder if it
.devN, aN, bN, cN, rcN, no suffix, .postN
ok, cool. my concern was that the general nature .dev might be lost, but
it's not.
i.e. what Toshio was talking about last year when he said:
People were very clear that they wanted to be able to stick dev versions
in the middle of their attempt to
Excellent rationale sections.
Let Extension: Name be legal without Name/ fields. Perhaps you would do
that to ask that the extension just needs to interpret the standard
metadata.
On Sun, Feb 3, 2013 at 4:07 PM, Marcus Smith qwc...@gmail.com wrote:
.devN, aN, bN, cN, rcN, no suffix, .postN
Nick Coghlan ncoghlan at gmail.com writes:
With Donald Stufft's assistance, I've created a new draft of PEP 426.
For the moment I'm listed as a co-author and no longer as
BDFL-Delegate - there's a separate discussion on python-dev about
that.
Still digesting the draft, but I notice that
.devN, aN, bN, cN, rcN, no suffix, .postN
like mentioned last year, the only case I can imagine some stakeholder
complaining about is the loss of a pre-release notion between a rc and
final that .dev served before.
the response I guess is that you can just tack on a .post to a rc?
1.0rc1.post1
The optional-features extra environment marker extension covers the test
requirements case and any other class of optional dependencies.
On Feb 3, 2013 4:37 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Nick Coghlan ncoghlan at gmail.com writes:
With Donald Stufft's assistance, I've created
12 matches
Mail list logo
