2 ms·
We should make this Python 4.0 and move on. Some high paid google engineers working the "official" 3.x will be pissed, but that's life. I am sad to see the schi
by hartator 10y ago
We should make this Python 4.0 and move on. Some high paid google engineers working the "official" 3.x will be pissed, but that's life. I am sad to see the schism in Python community.
- rch 10y agoA non-trivial number of people seem to want this, but why does it need to be called Python? Keep the syntax and C extension compatibility, but ditch the name. One could even work out a means of selectively bringing in ideas from elsewhere: - Concurrency from Erlang (http://queue.acm.org/detail.cfm?id=1454463 http://queue.acm.org/detail.cfm?id=1454463) - String handling from Go (https://blog.golang.org/strings https://blog.golang.org/strings) - Lightweight data classes (https://kotlinlang.org/docs/reference/data-classes.html https://kotlinlang.org/docs/reference/data-classes.html) - Syntactic macros from Nim (https://hookrace.net/blog/introduction-to-metaprogramming-in-nim/ https://hookrace.net/blog/introduction-to-metaprogramming-in...) - more from Lua, Julia, Scala, and Haskell (within reason) There are already plenty of examples of Python modules that implement significant modifications (e.g. Cython, Rpy2, Dask), so I don't think it would really feel all that different from typical Python programming.