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

Allow installing with pip #213

Open
mrfuxi opened this issue May 25, 2014 · 3 comments
Open

Allow installing with pip #213

mrfuxi opened this issue May 25, 2014 · 3 comments

Comments

@mrfuxi
Copy link

mrfuxi commented May 25, 2014

It would be great if plugins could be installed with pip

@kura
Copy link
Member

kura commented Jun 11, 2014

Some plugin developers, such as myself, do make our plugins pip installable. Sadly it's down to the original developer to do this really.

@lioman
Copy link
Contributor

lioman commented Feb 8, 2017

It could be encouraged by only letting pip installable plugins into the catalog

@moorepants
Copy link
Contributor

Agreed, it is so much easier to manage if plugins are all installable by package managers. It would enable pinning plugin versions, dependency resolution, remove the need to clone a giant repository of many plugins, and just make it much easier to manage plugins (ant themes!).

calfzhou pushed a commit to calfzhou/pelican-plugins that referenced this issue Sep 28, 2019
Utilizes the jinja `default` function instead of the `or` operator.

More information about how to use this function can be found in the jinja documentation: http://jinja.pocoo.org/docs/2.10/templates/#default

Closes getpelican#213
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

No branches or pull requests

4 participants