Conflicting versions of lxml about pressurecooker

[benjaoming]

Running pip install -r requirements.txt one more time downgrades lxml 🤷

Installing collected packages: lxml
  Attempting uninstall: lxml
    Found existing installation: lxml 4.5.0
    Uninstalling lxml-4.5.0:
      Successfully uninstalled lxml-4.5.0
Successfully installed lxml-4.3.5

[ivanistheone]

Hi Ben. We were aware of this issue, and other technical debt issues around the content pipeline tooling. If you dig around, I am sure you'll find a lot of these!

In many cases there has been a conscious decision not to fix these issues right now because they do not prevent developers for installing and using the packages. Basically, we aggressively fix BLOCKER issues (anything preventing chef authors from working on content), but WARNING-class issues are allowed to persist due to the team limited capacity and emphasis on cheffing above tooling, especially for shared dependencies like le-utils and pressurecooker where a good fix would require involving Studio and Kolibri teams, who are themselves overstretched.

Also, I think it's important to follow the "Chesterton's fence" principle concerning some of these features—sometimes there were past, present, or future considerations and interactions that force certain non-standard decisions, which are not obvious at first sight.

Thanks for filing the issue so we can keep track of it though! I look forward to the time when we'll have the luxury of time and some breathing room to address these holistically.

[benjaoming]

@ivanistheone the PR doesn't seek to be merged right away -- the PR is there because it's easier to open and fix while wondering the question of which lxml that is the intended one.

I will skip future fixes if I sense that it somehow seems like a tech debt issue.. ?

[ivanistheone]

closing this because le-pycatpion no longer pins version of lxml, see https://github.com/learningequality/pycaption/blob/py27/setup.py#L12