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
This PR silently removed Py2.7 support as a side-effect. There is no mention of it in the PR description, commit messages or discussion with the reviewers.
I'm the one who made the change, but it was several months ago, and I myself don't remember what the original intention was.
We need Python 2.7 support for the 3.8.3 release, because a significant number of users (not sure how many) still use that version of Python.
Get gensim building on Py2.7 again. Try working of the current develop branch, if not, consider alternatives.
My 2 cents: we don't need the whole automated machinery for 3.8.3. Further development will happen in the 4.0 branch without py2 anyway.
We just need to get py2 working, test it, and release it (once), for legacy users. And keep that branch around for potential critical bugfixes in the future (3.8.4…). But no need to introduce complex automation headaches for ourselves.
I guess it depends on how difficult it'll be to put py2.7 back into CI.
Another option: simply revert the "py3.5+ check" from setup.py and run the test suite manually, old-school.
And in case we also want precompiled wheels for py2.7 + 3.8.3, I can build them locally for Linux + Windows 8.1 + OSX El Capitan, as a one-off.
This PR silently removed Py2.7 support as a side-effect. There is no mention of it in the PR description, commit messages or discussion with the reviewers.
I'm the one who made the change, but it was several months ago, and I myself don't remember what the original intention was.
We need Python 2.7 support for the 3.8.3 release, because a significant number of users (not sure how many) still use that version of Python.
The text was updated successfully, but these errors were encountered: