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.

Sign up for GitHub

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

Jump to bottom

Optionally generate a package which uses flit instead of classic setup.py #24

Closed
nicoddemus opened this issue Aug 22, 2017 · 4 comments
Closed

Optionally generate a package which uses flit instead of classic setup.py #24

nicoddemus opened this issue Aug 22, 2017 · 4 comments
Labels
enhancement

Comments

@nicoddemus
Copy link
Member

nicoddemus commented Aug 22, 2017 •
edited
Loading

Howdy!

Just passing by to leave this feature suggestion: optionally use flit instead of the classic setup.py for package publishing.

I plan to try out flit some time soon, and realized this was a valid enhancement request for cookiecutter-pytest-plugin. 😉
@hackebrot
Copy link
Member

Hey @nicoddemus! 👋

I'm happy to add this as an option if you found it to be a suitable replacement for setup.py 👍

@nicoddemus
Copy link
Member Author

I didn't get a chance of using it myself, but it seems like a great alternative for pure-python projects as is the case with the majority pytest plugins. 😁

@gyermolenko
Copy link

@nicoddemus flint->flit

@nicoddemus nicoddemus changed the title Optionally generate a package which uses flint instead of classic setup.py Optionally generate a package which uses flit instead of classic setup.py Dec 20, 2018
bluetech added a commit that referenced this issue Jan 18, 2024
@bluetech
Convert setup.py -> pyproject.toml, flat layout -> src layout
0e6f67d 
pyproject.toml is the more modern way to do it, and we can remove all
setuptools dependence except for choosing it as the build backend.

src layout is less error prone than flat layout, given that tox is used.

Fix #38, #30, #24
bluetech added a commit that referenced this issue Jan 18, 2024
@bluetech
Convert setup.py -> pyproject.toml, flat layout -> src layout
b58973d 
pyproject.toml is the more modern way to do it, and we can remove all
setuptools dependence except for choosing it as the build backend.

src layout is less error prone than flat layout, given that tox is used.

Fix #38, #30, #24
bluetech added a commit that referenced this issue Jan 19, 2024
@bluetech
Convert setup.py -> pyproject.toml, flat layout -> src layout
02ebf29 
pyproject.toml is the more modern way to do it, and we can remove all
setuptools dependence except for choosing it as the build backend.

src layout is less error prone than flat layout, given that tox is used.

Fix #38, #30, #24
@bluetech
Copy link
Member

#61 switched to pyproject.toml, and has nothing setuptools specific other than the build backend, so there's not a whole lot of reason to use flit I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nicoddemus @bluetech @hackebrot @gyermolenko