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

Convert to entry point plugin and publish on PyPI #23

Open
dgw opened this issue Apr 24, 2016 · 1 comment
Open

Convert to entry point plugin and publish on PyPI #23

dgw opened this issue Apr 24, 2016 · 1 comment
Assignees

Comments

@dgw
Copy link
Owner

dgw commented Apr 24, 2016

Now that the module is updated for Sopel, and Sopel supports third-party modules installable via pip, this one should be published in the repository.

Decision: cookiecutter modules actually reside in the sopel_modules/modname/modname.py file within the git repository. It's probably possible to rewrite the module history to look like it's always been there—and therefore preserve git-blame-ability—but is that worth doing? Probably not. It could mess up Github's Contributions calendar, and would certainly mess up any commit hashes that are referenced in issue/PR histories.

@dgw dgw self-assigned this Apr 24, 2016
@dgw dgw changed the title Convert to cookiecutter module and publish on PyPI Convert to entry point plugin and publish on PyPI Jul 12, 2019
@dgw
Copy link
Owner Author

dgw commented Jul 12, 2019

With support for entry points coming in Sopel 7, I don't see any reason to bother with the cookiecutter template any more. Sopel 6.x is so old it's not worth packaging for at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant