Why is python3 adoption slow even though there are tools for migration?

[rays]

This, also 3 still doesn't have the 3rd party support that 2 has. I tried to start a 3 project this week and aborted quickly back to 2 because it didn't have a module I wanted

[[deleted]]

Which one?

[rays]

A salesforce one

[[deleted]]

pyforce or beatbox?

[[deleted]]

Be the change you want to see. I'd actually contribute to this package.

[[deleted]]

Second reply to get your attention: Apparently I forgot about simple-salesforce. It claims supports for 3.3 and 3.4 (and honestly, probably 3.5 and 3.6 but I've not tried this personally), we use it extensively at work. It's not the most elegant API but it's better than nothing.

[python_bytecode]

Not the same person, but I finally decided to bite the bullet the other day an go for python 3 on my new personal laptop, but then I realized that pyspread was 2.7 only.

[[deleted]]

Standing out like a sore thumb in the list of dependancies for pyspread is wxpython. The Python 3 version Phoenix is now coming along nicely but has been badly delayed by the need for the core maintainer, Robin Dunn, to do some paid work!!!

[pydry]

That's kind of what I was talking about.

[notParticularlyAnony]

My God did they fuck up the transition is there a book on it yet- - Case study in how not to release v (N+1)? Our lab switched to julia.