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
Unfortunately, colab uses python 3.7 by default so pip install triage installs triage 5.1.1, the latest version to support this version of python. To use newer triage versions here, we'll need:
Install (and tell colab to use) and updated python version (should be first thing in the notebook). This stackoverflow looks like a start, but will only update the python at the command line, not the colab kernel, so we might need to do a bit of experimentation here. Maybe this, though unfortunately conda-based and requires reloading the page (simply restarting the runtime isn't enough)?
Update the config in the notebook to v8 (and check if other things need to change)
If getting the colab runtime to use a newer python proves too troublesome, another option might be to actually store the config.yaml, database.yaml, and run.py to disk and run them with a newer python at the commandline via the first method (I believe the stdout logs should still show up in the notebook). Then, interrogating the results in the database can still be done with the python 3.7 kernel. This might get messy, however, with the audition piece.
Since it's meant as an easy introduction, we may also want to take advantage of some of the improvements to the config in newer versions of triage, such as only needing to specify the label query, to simplify the flow of the tutorial as well.
The text was updated successfully, but these errors were encountered:
Unfortunately, colab uses python 3.7 by default so
pip install triage
installs triage 5.1.1, the latest version to support this version of python. To use newer triage versions here, we'll need:v8
(and check if other things need to change)If getting the colab runtime to use a newer python proves too troublesome, another option might be to actually store the config.yaml, database.yaml, and run.py to disk and run them with a newer python at the commandline via the first method (I believe the stdout logs should still show up in the notebook). Then, interrogating the results in the database can still be done with the python 3.7 kernel. This might get messy, however, with the audition piece.
Since it's meant as an easy introduction, we may also want to take advantage of some of the improvements to the config in newer versions of triage, such as only needing to specify the label query, to simplify the flow of the tutorial as well.
The text was updated successfully, but these errors were encountered: