You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent release of Python 3.5, many Python developers are upgrading to a version of Python not officially supported by PyKMIP. Since PyKMIP already supports Python 3.3 and 3.4, adding official support for 3.5 should be trivial.
The text was updated successfully, but these errors were encountered:
Unfortunately it's not. It took me a little while to trace the issue but there's a weird error that occurs when you attempt to run py35 in tox when you have enum34 installed in older versions of Python. It has something to do how virtualenv works internally, which tox uses. Lots of nastiness.
This was the initial issue on the problem last year: pypa/virtualenv#763. It was supposed to be fixed, so either the issue's reappeared or I'm not doing the right thing in the right way. Apparently there's an ongoing effort to rewrite the bulk of virtualenv to play nice with different interpreters/platforms/environments/etc, so that may fix things eventually.
With the recent release of Python 3.5, many Python developers are upgrading to a version of Python not officially supported by PyKMIP. Since PyKMIP already supports Python 3.3 and 3.4, adding official support for 3.5 should be trivial.
The text was updated successfully, but these errors were encountered: