On 17 January 2018 at 12:51, Nick Coghlan wrote:
> I think tox provides a good precedent for what's needed when it comes
> to effectively targeting multiple environments: you want a venv per
> target environment per project, not just a venv per project.
After double-checking
On 18 January 2018 at 10:22, Dustin Ingram wrote:
>> Metadata 1.3 vs Metadata 2.0
>
> I agree with Nick here that since this version is backwards-compatible, that
> it
> should remain Metadata 1.3.
>
> In addition, I think we should avoid overloading the already-in-use "2.0"
>
Hi all,
Thanks very much for all your suggestions and feedback.
I want to take a moment to summarize & respond to some outstanding issues from
this thread & previous threads. [0][1][2]
First, I'd like to reiterate that the goal of this PEP is to:
1. Define the Core Metadata document as the