cmd2 says that:

"Python 2.7 support is EOL

Support for adding new features to the Python 2.7 release of |cmd2| was discontinued on April 15, 2018. Bug fixes will be supported for Python 2.7 via 0.8.x until August 31, 2018.

Supporting Python 2 was an increasing burden on our limited resources. Switching to support only Python 3 will allow us to clean up the codebase, remove some cruft, and focus on developing new features."

See: https://github.com/python-cmd2/cmd2

Előd

On 2018-05-30 14:42, Julien Danjou wrote:
On Wed, May 30 2018, Elõd Illés wrote:

In the last two days the ceilometer [1] [2] [3] and tooz [4] [5] [6] tox-py27
periodic stable jobs are failing. The root cause is the following:
* cmd2 released version 0.9.0, which requires python >=3.4 from now on.
These projects have comment in their tox.ini that they do not consume
upper-constraints.txt (in which there is an upper constraints for cmd2).

My question is: could we use upper-constraints.txt on these projects as well,
or is there any reason why it isn't the case?
Of course an entry could be added to test-requirements.txt with "cmd2<0.9.0",
but wouldn't it be better to use the upper-constraints.txt?
The question is: why cmd2 0.9.0 does not work and how do we fix that?


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to