|
|
|
|
|
by cauterized
3636 days ago
|
|
I've yet to work in a company that began developing its primary Python codebase after 3 matured. Nor any company that had the engineering bandwidth to prioritize upgrading a working Python 2 codebase to 3 over work that directly impacted customers or business. If I start a new codebase for a toy or throwaway project that doesn't have to be importable into one of those codebases, I'll start it in Python 3. If I remember to use it when creating the virtualenv. After all, with the primary project in Python 2, 2 is still my system default. |
|