+sources of truth for a single version. Having multiple sdists often times can +account for strange bugs that only expose themselves based on which sdist that +the person used.
You may not be aware, but developers that work on both Windows and Unix often have two sets of source code packages: one using Windows line ends, the other using Unix ones. The Windows ones can also include code which is only relevant on Windows while the Unix one includes parts that are only used on Unix, so having two sets (ZIP for Windows and .tar.gz for Unix) is a natural way to distribute your source code for those two target systems. Standardizing on two sdist formats is fine, but artificially limiting this to just one sdist upload removes useful functionality. On 25.08.2016 13:57, Donald Stufft wrote: > >> On Aug 25, 2016, at 7:30 AM, Nick Coghlan <ncogh...@gmail.com> wrote: >> >> On 25 August 2016 at 06:48, Donald Stufft <don...@stufft.io> wrote: >>> Ok, I’ve updated the PEP. You can see a diff at >>> https://github.com/python/peps/pull/74/files or the entire PEP at >>> https://www.python.org/dev/peps/pep-0527/ once that updated. However the >>> primary differences are: >>> >>> * Added Nick Coghlan as the BDFL Delegate (Thanks Nick!). >>> * Expanded upon rationale for dropping everything but sdist/wheel/egg. >>> * Allow an sdist to be either .tar.gz or .zip, but still drop all other >>> formats. >>> >>> Hopefully that can adequately address Marc-Andre’s concerns for the removal >>> of the other file types, and the inclusion of .zip will address other >>> folk’s concerns about losing .zip. >> >> Thanks for those updates. >> >> My one remaining question would be whether or not we have any projects >> that are in the habit of uploading both .zip and .tar.gz for the same >> release - if there are, the restriction to only one sdist per release >> will need to be included in the notification message to maintainers. >> (The introduction of that restriction could probably be clearer in the >> PEP text as well - previously it was implied by the single extension, >> but it may need to be called out more explicitly now that there are >> two permitted options). > > My querying shows that we have a total of 359 projects that have ever > uploaded two sdists for a single release. Looking at the number of > releases that have 2+ sdists per project, it appears like there are a > handful that do it regularly, and then the vast bulk have only done it > once or twice (see: https://bpaste.net/show/fdfce63673ec). > > I’ve gone ahead and explicitly call out the restriction of a single > sdist per release in the PEP, diff can be found online at > https://github.com/python/peps/pull/75/files. > >> >> Aside from that, I'm inclined to give folks another few days to raise >> questions and concerns, and then consider the PEP for acceptance early >> next week. >> > > Sounds good. > > > — > Donald Stufft > > > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Aug 25 2016) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
