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

missing setup.py-files for packaging #82

Closed
Serkan-devel opened this issue Jan 12, 2019 · 4 comments
Closed

missing setup.py-files for packaging #82

Serkan-devel opened this issue Jan 12, 2019 · 4 comments
Labels
needs fermenting Not sure what to do with this yet, give it time.

Comments

@Serkan-devel
Copy link

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/

@mosra
Copy link
Owner

mosra commented Feb 2, 2019

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!

@Serkan-devel
Copy link
Author

Idk if I would complete this #97 , might work on it later

@ashwinvis
Copy link

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

@mosra
Copy link
Owner

mosra commented Dec 3, 2024

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.

@mosra mosra closed this as completed Dec 3, 2024
@mosra mosra closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs fermenting Not sure what to do with this yet, give it time.
Development

Successfully merging a pull request may close this issue.

3 participants