Re:How we rolled out one of the largest Python 3 migrations
by icebraining on Thursday September 27, 2018 @05:31AM
(#18083086)
Code pruning is a problem in Go too; as soon as your codebase or any of your dependencies use reflection, it gets disabled for the whole binary.
A simpler alternative would be for Numpy and Pandas to provide its features as subpackages, like Airflow does: https://airflow.readthedocs.io/en/latest/installation.html
Re:How we rolled out one of the largest Python 3 migrations
by weberc2 on Thursday September 27, 2018 @11:17AM
(#18085307)
I’m almost certain that only applies to individual compilation units and not the whole AST. In other words, if I use reflection in my main package, code pruning still works on dependencies, which is quite a lot better than the Python situation.
IMHO unacceptably large, but that's because Python doesn't know which parts of pandas it might need to execute the program.