Re:Python Pip 20.3 Released with new resolver
by davidbrennerjr on Monday November 30, 2020 @12:30PM
(#25256351)
You should ask to talk to a developer before accepting an obviously complicated migration. Ask about the numbers since they're not IP/Properitary. How many lines of code? How many functions? How many standard modules? How many custom libraries? Is everything Python? Are other languages being used too? That way you will know whether or not they are intentionally hiding the real issues from you to get you to do free work.
[ Parent
| on HN ]
Re:Python Pip 20.3 Released with new resolver
by wp381640 on Monday November 30, 2020 @12:45PM
(#25256536)
Unit test coverage ...
Re:Python Pip 20.3 Released with new resolver
by davidbrennerjr on Friday December 04, 2020 @10:35PM
(#25311483)
A bit off topic, but unit test coverage trivializes the work that goes into conducting a migration. Unit test coverage really only pertains to upgrades. A migration is not synonymous with an upgrade. Migrations are serious work that typically span entire ecosystems.
When I mentioned "the numbers" I wasn't hinting at unit test coverage. I was giving examples as to what the numbers could be. Obviously OP should ask lots of questions about all of the software running on a legacy kernel.