Replies: 3 comments
-
Video (ES)newtvm.mp4 |
Beta Was this translation helpful? Give feedback.
0 replies
-
This is great @Alec4r. I like quite a lot the mechanism to have one single The fact that you have a working prototype is also amazing. I would like to make this possible by making smaller scope PRs that solve one issue at the time. For instance:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
This has been merged #10 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How is working now?
Currently, we need a step sequence.
To use tvm in local project
In a directory (example/stack):
tvm setup
this will create a symlink from example/stack/.tvm/switcher to venv/bin/tutortvm install v12.2.0
, this will clone the tag in example/stack/.tvm/v12.2.0tvm use v12.2.0
, this will update the switcher file (example/stack/.tvm/switcher)tutor config printroot
, this should return the tutor config default root (~.local/share/tutor)You only can run tutor and tvm commands if you have enabled the virtualenv.
To use tvm global
In a directory (example/stack):
tvm setup -g
this will create a symlink from example/stack/.tvm/switcher to usr/local/bin/tutortvm install v12.2.0
, this will clone the tag in example/stack/.tvm/v12.2.0tvm use v12.2.0
, this will update the switcher file (example/stack/.tvm/switcher)tutor config printroot
, this should return the tutor config default root (~.local/share/tutor)You can run tutor and tvm commands from anywhere.
What is the problem?
With this infrastructure, we have different problems:
To use tvm in a project is necessary to set up tvm in the project directory, this means that you need to create one .tvm directory in each project directory and clone there each version again.
If you want to set up it global and for a reason, you removed the project you will break all tutor commands, the reason why this happens is that you didn't remove the symlink.
You will always need to install tvm in a virtualenv to set up local.
To set up the tutor root, you need to export manually the TUTOR_ROOT variable.
What is the proposal?
Remove setup -g command
The plan is that all projects and versions will be cloned in a unique folder, I think that is a good idea to clone them in ~/.tvm
So in the first command or in the install process, we will create the files that need to tvm work.
Using tvm project init and tvm project enable instead of tvm setup
This command will create a .tvmrc file with the settings on the project directory, something like
git init
The file will have next settings:
tvm project init edunext --version="v12.2.0"
If you don't define the flag version in the command, tvm will create a new tvm project version with the name <tvm_version_in_use>@<project_name>
Then you should call the command
tvm project enable
this command will active the virtualenv created in the tvm project and it will set TUTOR_ROOT and TUTOR_PLUGIN_ROOTRunning pip commands
In both cases, you should call
tvm packages [options]
to install pip packagesWhat will be the new step by step?
Global
pip install git+https://github.com/eduNEXT/tvm.git
tvm install v12.2.0
, this will clone the tag in ~/.tvm/v12.2.0tvm use v12.2.0
, this will update the switcher file (~/.tvm/switcher)tutor config printroot
, this should return the tutor config default root (~.local/share/tutor)Local
pip install git+https://github.com/eduNEXT/tvm.git
tvm install v12.2.0
, this will clone the tag in ~/.tvm/v12.2.0tvm use v12.2.0
, this will update the switcher file (~/.tvm/switcher)tvm init example
, this will create a .tvmrc filewith version v12.2.0@example.
tvm enable
, this will activate the tvm project's virtualenv.tutor config printroot
, this should return your project path.Beta Was this translation helpful? Give feedback.
All reactions