5 ms·

Pity it's not Python3.

rtkwe 8y ago
Yeah weird. I would expect Python2 to be dying off more by now. Wonder if we're headed to an environment where there's essentially 2 separate languages as Python 3 continues to change and grow?
- ealhad 8y ago
  https://pythonclock.org/ https://pythonclock.org/
- jchw 8y ago
  I think we're roughly already there. I think the pivotal moment where Python 2 could've died out rapidly passed and they kept officially supporting it for too long.
  - da_chicken 8y ago
    As far as I know, permanent EOL for Python 2 is still Jan 1, 2020 (https://pythonclock.org/ https://pythonclock.org/). Python 3 was first released December of 2008. That's an awfully long tail.
    - collinmanderson 8y ago
      Fascinating. I always thought Python 2.7 support would end July 3, 2020 (exactly 5+5 years from when 2.7 was released), but for some reason they recently decided to go with Jan 1st. > Specifically, 2.7 will receive bugfix support until January 1, 2020. All 2.7 development work will cease in 2020. > I've updated the PEP to say 2.7 is completely dead on Jan 1 2020. The final release may not literally be on January 1st, but we certainly don't want to support 2.7 through all of 2020. https://www.python.org/dev/peps/pep-0373/#maintenance-releases https://www.python.org/dev/peps/pep-0373/#maintenance-releas... https://mail.python.org/pipermail/python-dev/2018-March/152355.html https://mail.python.org/pipermail/python-dev/2018-March/1523...
- duhi88 8y ago
  Well this project has pretty much died off. No update in over a year, and nothing significant in 3-4.
- detaro 8y ago
  It's a pretty old side-project, based on an interpreter that itself took quite a while to support Python 3 well due to lack of funding, so it's not that weird it hasn't been updated.
- saganus 8y ago
  I still get surprises like starting to learn Google Cloud Functions and realizing that up until July of this year they only supported Python 2. I have no idea why would a project of this caliber would start by using Python 2 instead of Python 3. Edit: When I started reading about GCF, all docs said I could only use Python 2. Later I found that they seem to be on the way to change this. But still, I was very surprised that Python 2 was even an option to begin with.
jchw 8y ago
Assuming the work here was primarily the asm.js based emitter, maybe it can be ported to PyPy3 without needing to go from scratch.

Yeah weird. I would expect Python2 to be dying off more by now. Wonder if we're headed to an environment where there's essentially 2 separate languages as Python 3 continues to change and grow?

ealhad 8y ago
https://pythonclock.org/ https://pythonclock.org/
jchw 8y ago
I think we're roughly already there. I think the pivotal moment where Python 2 could've died out rapidly passed and they kept officially supporting it for too long.
- da_chicken 8y ago
  As far as I know, permanent EOL for Python 2 is still Jan 1, 2020 (https://pythonclock.org/ https://pythonclock.org/). Python 3 was first released December of 2008. That's an awfully long tail.
  - collinmanderson 8y ago
    Fascinating. I always thought Python 2.7 support would end July 3, 2020 (exactly 5+5 years from when 2.7 was released), but for some reason they recently decided to go with Jan 1st. > Specifically, 2.7 will receive bugfix support until January 1, 2020. All 2.7 development work will cease in 2020. > I've updated the PEP to say 2.7 is completely dead on Jan 1 2020. The final release may not literally be on January 1st, but we certainly don't want to support 2.7 through all of 2020. https://www.python.org/dev/peps/pep-0373/#maintenance-releases https://www.python.org/dev/peps/pep-0373/#maintenance-releas... https://mail.python.org/pipermail/python-dev/2018-March/152355.html https://mail.python.org/pipermail/python-dev/2018-March/1523...
duhi88 8y ago
Well this project has pretty much died off. No update in over a year, and nothing significant in 3-4.
detaro 8y ago
It's a pretty old side-project, based on an interpreter that itself took quite a while to support Python 3 well due to lack of funding, so it's not that weird it hasn't been updated.
saganus 8y ago
I still get surprises like starting to learn Google Cloud Functions and realizing that up until July of this year they only supported Python 2. I have no idea why would a project of this caliber would start by using Python 2 instead of Python 3. Edit: When I started reading about GCF, all docs said I could only use Python 2. Later I found that they seem to be on the way to change this. But still, I was very surprised that Python 2 was even an option to begin with.

jchw 8y ago

Assuming the work here was primarily the asm.js based emitter, maybe it can be ported to PyPy3 without needing to go from scratch.