2 ms·
If "Complexity is always exponential." then a 10KLOC project should take less than 1/2 of the 2 days time that you estimated for a 20KLOC project. Which is cont
by eesmith 9y ago
If "Complexity is always exponential." then a 10KLOC project should take less than 1/2 of the 2 days time that you estimated for a 20KLOC project. Which is contrary to my experience.
> This tweak is almost a no brainer in pure python 3.
The timing estimate I made assumed 4 changes per minute. That's already pretty no-brainer. Are you suggesting it should have been faster than that? I don't know how. Not all of the strings needed to be converted to byte strings.
> python-future provide all the helpers for that
First time I heard of it. I thought we were supposed to be using 'six', which is where I got the shims from.
If I understand correctly, that package should not be used for Python libraries which want to maintain Python 2 compatibility. That is, if I have library X, and some of my users are on Python 2, then I shouldn't use python-future because the 'standard_library.install_aliases()' call modifies builtins, which may change how Python 2 works for those users.
> 4 days of porting for an entire project one time in a 25 years old language feels ok in my book.
Yes. My point is that I think your original numbers are optimistic, not that they are fundamentally flawed.