The App/Library point is partly why we haven’t jumped on this bandwagon, the distinction is important and keeping things separate has been done intentionally. Others (such as Nick or Donald) would be in a better position to speak to this since both have written about it extensively so while pushing in that direction would require a PEP it would also be a pretty big departure from what has been the accepted approach for some time as far as I understand
FWIW I don't mind where anything in particular goes, but pushing for everything to be defined by one file is not something I think is desirable if we want to maintain this separation as it will probably be confusing -- and the distinction is already subtle Dan Ryan gh: @techalchemy // e: d...@danryan.co From: Joni Orponen [mailto:j.orpo...@4teamwork.ch] Sent: Monday, September 24, 2018 11:43 AM To: distutils-sig Subject: [Distutils] Re: setuptools configuration in pyproject.toml On Mon, Sep 24, 2018 at 5:31 PM Bernat Gabor <gaborjber...@gmail.com> wrote: So what do people think? Should we encourage or discourage to have a single python project file? Apples and oranges. Libraries vs. applications vs. mystical and various 'enterprise deployables'. Which are you thinking of people working on? -- Joni Orponen -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/FN37IES4XTLCAXNDGQZJDS3O6AIIIRVB/
