-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes tests in py3.8 #2432
fixes tests in py3.8 #2432
Conversation
@alvations or @stevenbird know this better than me, but I would suggest starting with the tox environment and getting that to work first. If there's a mismatch between that and the local setups of those using 3.8 we should fix it separately. Getting tox to work has the advantage that it'll also get tested by the github CI and we can officially say we support 3.8 until someone complains about their local setup (not a likely scenario). |
The problem with setting up a tox environment is scipy isn't installable via pip and I had to build from source in my venv to get it to work. Looks like scipy is working on releasing a 3.8 compatible version: scipy/scipy#10927. So, what do you suggest I do - is there a way to build from source while setting up a tox environment ? |
I'd go down the path of least resistance and set up an alert of some kind to notify me when scipy starts supporting 3.8 and then attempt stuff with NLTK. This is the cost of having dependencies... If, of course, you have time and interest, you could help adding 3.8 support to scipy, that's the more proactive approach. |
scipy is close to a release and I've subscribed to their issue re this. Will take this up as soon as they've released the wheels. |
[CI: retest] |
[CI: retest] |
@srhrshr any luck getting this to work? |
Will take this up this weekend. You can expect some chatter from me in about 12 hours. |
Thank you @srhrshr for the help in testing NLTK for python 3.8. We sorely need this =) Any idea why the python 3.8 isn't kicked in on the CI from the |
No worries @alvations - that must be because I didn't update the travis.yml - hopefully it should trigger now. Btw, here is a detailed log of the local tox run. tested w/ python 3.8.0:
—————————————————————————————————————— tested w/ python 3.7.4:
—————————————————————————————————————— tested w/ python 3.6.9:
—————————————————————————————————————— tested w/ python 3.5.4:
|
@srhrshr Thanks for updating the travis yml. Now that looks great!! @stevenbird @iliakur I think with From the CI side, it looks like it's LGTM for this. |
Thanks @srhrshr and @alvations |
@copper-head this is in response to your post on the
nltk-dev
google group to test out the repository against python version 3.8.0.There were a few hiccups setting up the dev environment with the requirements compatible with the python 3.8 version as running
pip install -r pip-req.txt
didn't directly work on my machine. I ended up having to install thescipy
andscikit-learn
dependencies from source. You can find the full list of requirements on my virtualenv here.In order to run the tests, I ran
python nltk/test/runtests.py
and fixed the import errors etc that I ran into along the way. This PR is a diff of changes I made for this.Does this state of the logs show that tests ran successfully?
Also, running
tox -v py38
didn't directly work because the tox.ini file was not configured to work with python 3.8 (Duh!). But, I can adapt and run this too if this is how you want me to test. Let me know.Thanks,
Harsha