$ ./bin/buildout
Develop: '/Users/stevepiercy/projects/plone-theming-ibew/plonetheme.tango/.'
Version and requirements information containing pycodestyle:
Requirement of flake8-todo: pycodestyle<3.0.0,>=2.0.0
Requirement of flake8>=2.4.0: pycodestyle<2.1.0,>=2.0.0
While:
Installing.
Getting section code-analysis.
Initializing section code-analysis.
Installing recipe plone.recipe.codeanalysis[recommended].
Error: There is a version conflict.
We already have: pycodestyle 2.3.1
but flake8 3.0.4 requires 'pycodestyle<2.1.0,>=2.0.0'.
I looked through the issue tracker, and tried various version combinations in buildout.cfg, but to no avail.
to be exact, these changes are already in the latest commit for bobtemplates.plone, so no need to file a ticket there. Just a release of bobtemplates.plone (or pull from source)
Huh, I could have sworn I set that under the [versions] stanza. Thank you, that worked.
Should I file a ticket/PR on the training documentation to use pip install git+https://github.com/plone/bobtemplates.plone.git instead of the tagged version or to tell the user to edit their buildout.cfg?
My plan is to also refacture the theming part to be a subcommand too, rather then a full package.
That will make the templates even more modular and flexible. Then we only need one package template to create a basic plone package and add needed stuff like, Content Types or a theme later to it. And this allows us to even combine theme as we need it. To finish this I still need a bit more time.
As this changes a lot how we work with the templates, I would describe this as 2.x.
We have already changed the current structure in master, to have separated theme and python packages. They are working, but as I mentioned above will refactored more in the next weeks. If it really needed to have a 1.0.6 release now, we could create a branch from the 1.0.5 tag and just fix the version pinning.
