> Not to mention the unicode implementation is broken.
Can you provide more details? The one thing that python3 did well is actually fixing the unicode/str mixup.
You posted some lines of code, but didn't tell exactly what's wrong with it.
> Python3 not operating on bytes by default is a mess
Why not just use the b'' prefix then and be explicit?
> can't move to Python3 due to how unicode is implemented
I'd like to see the bugs he raised against python 3 regarding this. There should be no difference in what you can and cannot do using python 2/3. I don't want to call BS on this, but... please provide some specific issues if you're claiming py3 is not usable.
Can you provide more details? The one thing that python3 did well is actually fixing the unicode/str mixup.
You posted some lines of code, but didn't tell exactly what's wrong with it.
> Python3 not operating on bytes by default is a mess
Why not just use the b'' prefix then and be explicit?
> can't move to Python3 due to how unicode is implemented
I'd like to see the bugs he raised against python 3 regarding this. There should be no difference in what you can and cannot do using python 2/3. I don't want to call BS on this, but... please provide some specific issues if you're claiming py3 is not usable.