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

No updates since more than two years: mature or out of date? #1

Open
guettli opened this issue Mar 7, 2017 · 2 comments
Open

No updates since more than two years: mature or out of date? #1

guettli opened this issue Mar 7, 2017 · 2 comments

Comments

@guettli
Copy link

guettli commented Mar 7, 2017

No updates since more than two years.

Is this project mature (no update are needed) or is it out of date?

It is no problem if you have no time to maintain it. If this is the case, please update the README and tell what you recommend for new comers. Thank you.

@konstantint
Copy link
Owner

konstantint commented Mar 7, 2017

It is mature in the sense that it is, in its core, a template which results in a well-structured project, which fits well with the age-old development practices. I personally still use it quite often, however I haven't needed the whole buildout setup for quite a while, so I'd typically only leave the internal package folder after initialization. For Flask apps I have made a separate template).

At the same time it must be becoming "out of date" in two senses. Firstly, "fashion trends" change. For example, I'm not sure whether paster is used much at all at the moment. For that reason there is a cookiecutter option. Another trend that I see is that buildout has gone gradually out of fashion over the years in general (in favor of manual requirements management in a virtualenv). I feel somewhat sad about it - it is a nice tool with no real alternative at the moment (manual package management is a bit messier for larger projects).

I am not sure there are some serious new trends at the moment that would be worth adding - if you can suggest something, do so. If you know nice alternative template projects, share them. The current README includes three links in the end - those would certainly need an update.

Secondly, it seems that at the moment the template is technically outdated in the sense that bootstrap.py probably needs to be updated to a newer version - otherwise it does not initialize for me. I'll see when I have time to fix it.

In general, maintaining cookiecutter templates is more comfortable from a development perspective, hence I'd probably mark this one as obsolete, and push the updates to the cookiecutter one. This is somewhat unfortunate because I personally prefer the paster simply because I can type paster create -t python_boilerplate from memory while cookiecutter requires copy-pasting the full repository path.

@guettli
Copy link
Author

guettli commented Mar 8, 2017

Thank you for this explanation.

I never used buildout, since when I needed it, it looked very dated.

We use salt for configuration management. We manage our virtualenvs and the root level with it.

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

2 participants