I’ve moved the old fastai/ folder to old/fastai/. I’ve also updated the symlinks in all course folders. So everything should continue to work fine, if you’re using the conda environment and symlink approach recommended for the course. You won’t be able to use the pip version of fastai in the future, since that will be updated to v1, which isn’t compatible with the course - unless you pin your pip installed version to <1.
If you are using fastai for any course.fast.ai course, please do NOT install fastai from pip or conda using the instructions below; the instructions below are for fastai v1, but the courses use fastai 0.7. For the courses, you should simply conda env update , and the notebooks will work (there is a symlink to old/fastai/, which is fastai 0.7, in each course notebook directory).
I used the conda env update method for installing fastai. Nonetheless I’m having problems running the below lines from the DL1 course:
from fastai.transforms import *
from fastai.conv_learner import *
from fastai.model import *
from fastai.dataset import *
from fastai.sgdr import *
from fastai.plots import *
I get an error
ModuleNotFoundError Traceback (most recent call last)
in ()
----> 1 from fastai.transforms import *
2 from fastai.conv_learner import *
3 from fastai.model import *
4 from fastai.dataset import *
5 from fastai.sgdr import *
ModuleNotFoundError: No module named ‘fastai.transforms’
And the same for all the other lines, if I run them individually. I notice that all of these are located in the fastai/old/fastai folder. What should I do?
Hi, I’m going to sound like a meddling manager who knows nothing (mostly true…I haven’t even started the class yet!) but is there a list somewhere of major changes between 0.7 and v1? I’m just trying to think ahead: once I finish the course, what will I need to be able to transition to v1, and use it in real world applications?
Would it be possible for someone (with github access) to tag and cut a release right before the v1.0 migration happened. I see a tag from May '18 but a lot has happened since then.
Not entirely sure but this commit seems like a reasonable stopping point
This is the easiest way, but means that the date of that tag will be the current day (day of the commit) and NOT in the past. This can be manipulated though if that is important to somebody, see answer below the one chosen as correct:
BTW, perhaps what you shared about needing to make a release is no longer needed. At least, once I pushed the tag, github immediately created a release. i.e. no extra steps was necessary.
and I combined a bunch of answers to make a one-liner solution that sets the tag date to when it actually happened, uses annotated tag and requires no git checkout :
tag="v0.1.3" commit="8f33a878" bash -c 'GIT_COMMITTER_DATE="$(git show --format=%aD $commit)" git tag -a $tag -m $tag $commit'
git push --tags origin master
where tag is set to the desired tag string, and commit to the commit hash.