And yes, 2to3 fixes 90% of porting problems. But in my experience, it was especially bad at handling, of all things, import statements. Definitely not a silver bullet.
And yes, 2to3 fixes 90% of porting problems. But in my experience, it was especially bad at handling, of all things, import statements. Definitely not a silver bullet.
HA ha ha ha ha. No. Not even a little.
There are a bunch of reasons for this, but the big ones are: 1. Scientists aren't developers (some of us are exceptions, but we prove the rule). 2. The objective function of a grad student is "publish and graduate" not "write good code and use it forever".
I've worked in academia (as a research assistant) before so I'm familiar with shitty grad student software. But going to the effort to document and present on the software without making sure it even worked? That seemed excessively stupid to me.
> document and present on the software without making sure it even worked? That seemed excessively stupid to me
It sounds like that individual is responding rationally to the incentive structure he's embedded in, and succeeding as a result.