This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients a.badger, dstufft, eric.araujo, jaraco
Date 2019-09-11.15:03:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568214216.1.0.528077194077.issue36998@roundup.psfhosted.org>
In-reply-to
Content
Thanks all for investigating and discussing this issue. I'm reviewing the PR, and I can't help but wonder, does this same issue exist when building with setuptools? Do you care about older Python versions? Would addressing these issues in setuptools address your needs?

Additionally, the main use-case you describe is someone wishes to create an sdist referencing invalid filenames. That seems like an undesirable case. Could such a project not instead generate these invalid filenames on demand rather than materializing them in a distribution package?

I'm also concerned that by altering `write_file`, we're applying a change for a specific use-case to a utility probably shared by several use-cases.

Overall, I'm leaning -1 on this right now. Can you convince me this change is the best thing for the system?
History
Date User Action Args
2019-09-11 15:03:36jaracosetrecipients: + jaraco, eric.araujo, a.badger, dstufft
2019-09-11 15:03:36jaracosetmessageid: <1568214216.1.0.528077194077.issue36998@roundup.psfhosted.org>
2019-09-11 15:03:36jaracolinkissue36998 messages
2019-09-11 15:03:35jaracocreate