Skip to content

SOURCES.txt should be regenerated on every use #211

@ghost

Description

Originally reported by: jurko (Bitbucket: jurko, GitHub: jurko)


I think the SOURCES.txt project manifest file should be regenerated on every use.

Older distutils versions, e.g. those from early 2.7.x or 3.1 Python releases, have bugs with how they generate the project's manifest file from its MANIFEST.in template (see CPython issue http://bugs.python.org/issue6884) which may cause the manifest to contain some extra entries.

This can cause problems because if you use an older Python versions to generate the SOURCES.txt, and later run a setup.py sdist operation using a later Python version (e.g. 3.4), your generated sdist will end up containing those extra entries. On the other hand, if you delete the old SOURCES.txt manifest and just let the new Python version regenerate it - the project's sdist will again contain the correct files.

Setuptools documentation already states:

#!text
The file is automatically generated by setuptools whenever the
egg_info or sdist commands are run, and it is not user-editable.

Hope this helps.

Best regards,
Jurko Gospodnetić


Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions