-
Notifications
You must be signed in to change notification settings - Fork 85
Switch to Flit for packaging #94
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
Comments
I tested Flit out in https://github.com/crccheck/project_runpy and it was... pretty nice. The downside is you can't |
pip install should work, if you have the right pyproject.toml: https://github.com/caravancoop/configstore/blob/master/pyproject.toml (build-system section, the rest is equivalent to flit.ini) |
Thanks, I was going to tackle this soon as cleanup before I start removing support for Django v1 since Django v3 is around the corner. |
I'm not planning on doing a Sphinx site, so let's use Markdown to make the documentation easier to maintain. Part of #94
looks like
|
There is an ongoing discussion to determine whether pip editable installs should be pluggable (similar to how pip install can call any build system to get a wheel). In the meantime, people have to use lower-level mecanisms specific to the build tool, like |
semantic release solves the problems I had with Poetry, so I'm sticking with Poetry |
https://flit.readthedocs.io/en/latest/index.html
The text was updated successfully, but these errors were encountered: