On Mon, Feb 11, 2013 at 9:36 PM, Donald Stufft <donald.stu...@gmail.com>wrote:
> On Tuesday, February 12, 2013 at 12:13 AM, Éric Araujo wrote: > > Le 11/02/2013 13:37, Marcus Smith a écrit : > > Projects which wish to use non-compliant version identifiers must > restrict themselves to metadata v1.1 > > currently, "Projects" don't have control over this, right? > setuptools/distutils just writes 1.0 or 1.1 metadata, period. > > Yep, but projects can control the version used by distutils and others > by deliberately not using fields new in a given metadata version. I.e. > if you don’t have requires nor requires-dist not project-url, you’ll get > metadata 1.0; if you use setup-requires-dist you get 1.3 (from a tool > that knows about it, of course). > > I think the biggest point of contention here is how does a project > that doesn't _need_ any of those new fields opt into the stricter > version comparisons? > I guess the answer is that the next wave of tool updates has to give the user a way to specify this choice. and in talking with Nick, his idea is that it's up to each tool to gather this however they want from users. I.e. no PEP390 successor that standardizes how "users" put metadata into their projects. that's probably worth another thread... the lack of a PEP390ish successor. Marcus
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
