5 ms·

> It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks agains

> It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks against vanilla Python 3.10. So not entirely just python 3.1.

zitterbewegung 3y ago
I have ported code from Cinder to CPython . The fork has some optimizations that can be easily put in CPython and Facebook is open to port features. I’m not sure if Facebook wants to continually have a fork but CPython is open to have those features merged in if they make sense.
- amethyst 3y ago
  The Cinder team's longterm goal is to upstream as much as we can, and make the rest available as pip-installable extensions that anyone could theoretically install and use on CPython. The fewer internal changes and patches we need to maintain, the faster we can adopt upstream Python releases and all of the associated performance and tooling wins.
  - VagabundoP 3y ago
    I've been following it with updates from Talk Python To Me and Python Bytes. Great work, much appreciated.
  - zitterbewegung 3y ago
    Okay cool thanks for the clarification
  - VectorLock 3y ago
    That seems like pretty much the perfect way to go about things. Kudos on that work!
roflyear 3y ago
Python is a spec not an implementation, for what it is worth.
chungy 3y ago
Mind that Python 3.10 is nine major versions ahead of 3.1
- deleted 3y ago
  [deleted]
- paulddraper 3y ago
  *minor
- Tommstein 3y ago
  :s/major/minor
  - chungy 3y ago
    No, I meant major. Each of the 3.x releases brings in new features, deprecations, and even sometimes removed features. They are all major releases. Python doesn't go by semver rules. Semver isn't a definition for all software project versioning systems everywhere.
    - Tommstein 3y ago
      You are factually wrong. "To clarify terminology, Python uses a major.minor.micro nomenclature for production-ready releases. So for Python 3.1.2 final, that is a major version of 3, a minor version of 1, and a micro version of 2. * new major versions are exceptional; they only come when strongly incompatible changes are deemed necessary, and are planned very long in advance; * new minor versions are feature releases; they get released annually, from the current in-development branch;" — https://devguide.python.org/developer-workflow/development-cycle/#devcycle https://devguide.python.org/developer-workflow/development-c...
- shaftoe444 3y ago
  Good point 3.10 != 3.1

zitterbewegung 3y ago

I have ported code from Cinder to CPython . The fork has some optimizations that can be easily put in CPython and Facebook is open to port features. I’m not sure if Facebook wants to continually have a fork but CPython is open to have those features merged in if they make sense.

amethyst 3y ago
The Cinder team's longterm goal is to upstream as much as we can, and make the rest available as pip-installable extensions that anyone could theoretically install and use on CPython. The fewer internal changes and patches we need to maintain, the faster we can adopt upstream Python releases and all of the associated performance and tooling wins.
- VagabundoP 3y ago
  I've been following it with updates from Talk Python To Me and Python Bytes. Great work, much appreciated.
- zitterbewegung 3y ago
  Okay cool thanks for the clarification
- VectorLock 3y ago
  That seems like pretty much the perfect way to go about things. Kudos on that work!

roflyear 3y ago

Python is a spec not an implementation, for what it is worth.

chungy 3y ago

Mind that Python 3.10 is nine major versions ahead of 3.1

deleted 3y ago
[deleted]
paulddraper 3y ago
*minor
Tommstein 3y ago
:s/major/minor
- chungy 3y ago
  No, I meant major. Each of the 3.x releases brings in new features, deprecations, and even sometimes removed features. They are all major releases. Python doesn't go by semver rules. Semver isn't a definition for all software project versioning systems everywhere.
  - Tommstein 3y ago
    You are factually wrong. "To clarify terminology, Python uses a major.minor.micro nomenclature for production-ready releases. So for Python 3.1.2 final, that is a major version of 3, a minor version of 1, and a micro version of 2. * new major versions are exceptional; they only come when strongly incompatible changes are deemed necessary, and are planned very long in advance; * new minor versions are feature releases; they get released annually, from the current in-development branch;" — https://devguide.python.org/developer-workflow/development-cycle/#devcycle https://devguide.python.org/developer-workflow/development-c...
shaftoe444 3y ago
Good point 3.10 != 3.1