Distribute to setuptools - #8161
Conversation
6e19ec4 to
4868a67
Compare
|
@feanil I have this branch running on setuptools.m.sandbox.edx.org, and it works -- and I verified that setuptools 16.0 is really installed. I imagine that we need to change some things about this PR before it can be merged, though. |
|
@singingwolfboy does this replace #7465? What's going on? |
4868a67 to
1b95f62
Compare
|
@sarina yes, this is intended to replace #7465, although I don't think this PR is ready to be merged yet, since it depends on my fork of NLTK. To make this merge-ready, we should either make an NLTK fork and put it on the edx GitHub account, or upgrade to NLTK 3 (and deal with the backwards-incompatibilities). I'm waiting for some review & feedback from @feanil. |
|
@singingwolfboy should #7465 be closed? Should an OSPR ticket be made for this, and be put for devops review? |
|
@singingwolfboy could you give us an estimate of how much work it would take to rev up to NLTK3? |
|
@benpatterson: The work to upgrade to NLTK 3 can be divided up into two parts. The first part is identifying all the different places that we use NLTK in our various different projects, finding backwards-incompatible usages, and rewriting them to be compatible with NLTK 3. (Ideally, using That's the first part. The second part is identifying any courses running on edx.org where the course author is running custom Python code as part of the course, and contacting those course authors to determine if they are using NLTK. If so, we'll also need to inform them that NLTK is going to be upgraded to version 3, point them to the documentation with the backwards-incompatibilities, and ideally show them how to write code that is compatible with either NLTK 2 or 3. I'm guessing that the first part will take a few days of work, mostly spent on testing. I have no idea how to estimate how much time and effort is involved in the second part. |
|
@singingwolfboy thanks for giving the details on it. |
1b95f62 to
d18b9a6
Compare
57fd57b to
a635bfe
Compare
|
jenkins test this please |
a635bfe to
0ed878b
Compare
33ec032 to
4bea63f
Compare
4bea63f to
3388c4b
Compare
|
@singingwolfboy Brought up a sandbox and verified that at the end of the provision, it's the correct version. 🎆 I did a quick smoke test of the demo course as well and didn't see any issues. I think it's time. 👍 |
|
@singingwolfboy @feanil what needs to happen next? |
|
@sarina we're trying to get ease and ora2 repos aligned before we can merge this. |
|
Is there specific work we can point to on the JIRA ticket that indicates what it's blocked on? |
49620e9 to
a673ce6
Compare
'distribute' is the ancestor of 'setuptools', and many packages require setuptools to be installed. Upgrade of MySQL-python from 1.2.4 to 1.2.5 is required because of an incompatibility with setuptools>0.7.
So that we can use setuptools instead of distribute
a673ce6 to
a31f685
Compare
There was a problem hiding this comment.
This should be pinned instead of using -e
There was a problem hiding this comment.
Out of curiosity to me, what does the -e do?
There was a problem hiding this comment.
-e make pip install the dependency in "editable" mode: https://pip.pypa.io/en/stable/reference/pip_install.html#editable-installs I'm actually not sure what that means.
Distribute to setuptools
|
Thanks everyone for the great work! |
|
@codref ansible no longer refers to post.txt as of two months ago: see https://github.com/edx/configuration/pull/1982 and https://github.com/edx/configuration/pull/1989. Can you make sure that you're updated to the latest version of the configuration repository, and let me know if you still get an error? If you do get an error, please post the traceback to a pastebin service (like Github Gist) and link to it, so that we can see what the problem is. |
|
We had to partially revert this pull request in #8929, because there was an unexpected interaction between adding |
Follow-on PR from #7465.
distributewithsetuptoolsMySQL-pythonto 1.2.5 forsetuptoolscompatibilitydistribute