4 ms·
TIL I suppose Python doesn't even have backwards compatibility within the same major release as we saw with the addition of the async keyword in Python3.5. Man
by abetlen 7y ago
TIL
I suppose Python doesn't even have backwards compatibility within the same major release as we saw with the addition of the async keyword in Python3.5. Many older Python 3 packages broke because they expected that to be a legal identifier for a variable name.
- hprotagonist 7y agotensorflow didn't work on 3.7 for a solid 8 months because some people at google very unwisely decided that `async` and `await` were great choices for variable names, despite PEP492 landing in 2015.
- fock 7y agothat's because tensorflow is advertisement for Google and while it's technically open-source, it doesn't stand for any kind of community-project, it's all there to show off (and ingrain in its users) the way Google wants things to Go (just look at the byzantine Bazel-build-processes - tensorflow taking hours to build and pytorch about 10minutes...).
- hprotagonist 7y agomy torch builds also take hours. facebook is just as capable of writing hot garbage, sadly.
- fock 7y agoYeah, still it's an order of magnitudes faster...
- VWWHFSfQ 7y agoPython has never tried to maintain backwards compatibility within a major release