-
Notifications
You must be signed in to change notification settings - Fork 93
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
missing setup.py-files for packaging #82
Comments
Hi, this was one item on my large TODO list, but so far I was not able to get to it :) I have no experience with Python packaging myself, do you think you could provide a proof-of-concept PR adding this? Thank you! |
Idk if I would complete this #97 , might work on it later |
This will have to be fixed for the next Pelican release (5.x) which supports importable modules. The old method is still supported, but it does not work for a package like plugin system which m.css has. See: https://pelican.readthedocs.io/en/latest/plugins.html |
Closing for the reasons described in #253. Might revisit this in the future, but for now packaging and especially regular versioned releases is extra effort I don't have bandwidth for. Sorry. |
The pelican theme and plugins don't have a
setup.py
associated with it to make packaging easier.https://packaging.python.org/tutorials/packaging-projects/
The text was updated successfully, but these errors were encountered: