Feature #9850

Specify exact versions for Python and its packages

Added by Evgeny Novikov over 1 year ago. Updated 12 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Published in build:


We have many annoying issues due to different versions of Python and its packages have different capabilities. Now its time to specify exact versions of Python and its packages that should work well for Klever. Users who will not follow recommendations will behave on their own risks. Nobody should use the most modern versions of Python and its packages for Klever. Of course it is recommended to set up a dedicated virtual environment for deploying Klever locally. One day I will fix deployment scripts as well - there is a corresponding task already.

Any update to newer versions of Python or/and its packages should be specified explicitly so that users will be aware that their environment is outdated. Of course, Klever should operate well within an updated environment.

Related issues

Blocks Klever - Feature #9897: Develop tutorialClosed10/30/2019




Updated by Evgeny Novikov about 1 year ago


Updated by Evgeny Novikov almost 1 year ago

  • Status changed from New to Resolved

I implemented the feature in branch python-package-versions. The branch undergoes testing.


Updated by Evgeny Novikov almost 1 year ago

  • Status changed from Resolved to Closed

Tests passed, so, I merged the branch to master in 0f99ee717.

There is a very important information for all developers. From now everybody should use a dedicated Python 3.7 and Python packages from source:requirements.txt for Klever development. You can find updated developer instructions here. Other versions of Python and its packages are not accepted if they will result in any failures for specified ones.


Updated by Evgeny Novikov 12 months ago

I forgot to add that all previous instances of Klever should be uninstalled prior to update of master! Besides, do not update them.

Also available in: Atom PDF