Grokproject in python2.6 environment creates Grok1.0 without complaining
Bug #541400 reported by
Roger Erens
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grok |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Grokproject 1.0.3 in a virtualenv that has python2.6 as its interpreter does not warn or refuse to procede when I enter the command
grokproject --grokversion=1.0
even though Grok 1.0 only runs with python2.4 or python2.5.
Or maybe grokproject should include the interpreter to use in the created buildout.cfg.
| Changed in grok: | |
| status: | New → Won't Fix |
Revision history for this message
| Christian Klinger (cklinger) wrote | #1 |
To post a comment you must log in.
Currently we can not put restrictions on the python interpreter version in setup.py. But maybe in the future we can look on integrationg pep 0390 into grok's setup.py.
We never thougt maintaining a matrix of compatibilities of grok and python versions in grokproject.
Patches are welcome...
Grok 1.2 support python 2.6.