You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Came across the setup.py and wondered why it exists since we do not deploy to pypi, do we? Turns out we did in the past but the last update is of januari 2018.
What should've happened instead?
I would propose to remove the package for pypi completely since it contains outdated information and starting releasing again wouldn't be of much benefit.
Additional details
Since setup.py has no purpose I'm planning to merge it with pyproject.toml.
The text was updated successfully, but these errors were encountered:
The purpose of the pypi package is only to ensure that we own the package name and prevent it from being used by a malicious actor.
That said, it might be a good idea to update it and make its purpose clearer.
We can create a entrypoint cookiecutter-django which invokes cookiecutter cookiecutter https://github.com/cookiecutter/cookiecutter-django --version $version?
You're right—if we no longer deploy to PyPI and haven't updated the package since January 2018, it makes sense to consider removing it. Merging setup.py with pyproject.toml sounds like a good approach to streamline the project configuration.
This change could also help reduce confusion for contributors who might assume the PyPI deployment is still active.
What happened?
Came across the
setup.py
and wondered why it exists since we do not deploy to pypi, do we? Turns out we did in the past but the last update is of januari 2018.What should've happened instead?
I would propose to remove the package for pypi completely since it contains outdated information and starting releasing again wouldn't be of much benefit.
Additional details
Since setup.py has no purpose I'm planning to merge it with pyproject.toml.
The text was updated successfully, but these errors were encountered: