Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moved the metadata into setup.cfg #116

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

KOLANICH
Copy link

Added pyproject.toml
Version is now populated automatically from git using setuptools_scm.

I had to remove everything from meta except the version (it can be fetched and populated, but it will slow down loading the module and I really doubt anyone ever relied on this API) and also removed the very suspicious exec call that has no legit reason to be present in this lib.

@KOLANICH KOLANICH force-pushed the setup.cfg branch 2 times, most recently from 4094e05 to ab76eb2 Compare February 22, 2022 16:54
setup.py Outdated Show resolved Hide resolved
@alexmojaki
Copy link
Collaborator

+1 for removing exec, see #87

I quite like the setup in my own packages like https://github.com/alexmojaki/executing which was also initially introduced by @KOLANICH. It's minimal and very standard, see e.g. setup.py. @gruns are you attached to the commands in your setup.py? For publishing I use https://github.com/alexmojaki/executing/blob/master/make_release.sh. Is being able to run python setup.py test important?

@KOLANICH
Copy link
Author

@alexmojaki, BTW you should be able to remove setup.py completely since modern versions of pip support editable install in this case. I also think that we should get rid of setup.py here too.

Version is now populated automatically from git using `setuptools_scm`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants