4 ms·

What a ridiculous conclusion you came to based on a single line from that page. The very next line says: > We've made Cinder publicly available in order to fac

What a ridiculous conclusion you came to based on a single line from that page. The very next line says: > We've made Cinder publicly available in order to facilitate conversation about potentially upstreaming some of this work to CPython and to reduce duplication of effort among people working on CPython performance. > Our goal in making this code available is a unified faster CPython. Facebook is a Python Software Foundation sponsor[1], and they sponsor every PyCon. I don't know why you got the idea that they don't contribute back. https://www.python.org/psf/sponsorship/sponsors/ https://www.python.org/psf/sponsorship/sponsors/

bgfellows 5y ago
The PSF has not really sponsored CPython so far, and PyCons are for self promotion. Often in OSS foundations the entire sponsorship money goes to people who don't deserve it. Please do not attach any meaning to corporate sponsorship of foundations unless you can point to a specific project. 99% of CPython has been written by individuals without any compensation who don't get any credit. When a corporation gives money to non-productive bureaucrats everyone thinks they are helping open source. It is very sad.
- KptMarchewa 5y ago
  Agreed with your comment. There are public reports of PSF, 75% of expenses go to US PyCon. https://www.python.org/psf/annual-report/2020/ https://www.python.org/psf/annual-report/2020/
  - neolog 5y ago
    > In 2019, PyCon US generated 63% of the PSF’s revenue.
    - rpl101 5y ago
      Which makes it even more surprising where all that money goes. Hint: It is not CPython development.
    - KptMarchewa 5y ago
      63% of revenue and 75% of costs.
      - neolog 5y ago
        positive net revenue?
3v1n0 5y ago
Yeah but also... “If you want to upstream it, take it” it's not really something where ehi forked is working hard to send it back upstream patch by patch...
- _carljm 5y ago
  We've already upstreamed a lot of changes, including one that makes all coroutines faster in Python 3.10. The big-ticket items in Cinder would be big changes for CPython and need discussion about whether CPython even wants them. You don't just slap a C++ JIT into a bugs.python.org ticket. Opening Cinder is the first step in the conversation, and we're here for that work too. It's not just "if you want it, take it."
  - 3v1n0 5y ago
    Ok great to hear that this is the case! Reading the README was a bit unclear on this topic. I also know that engineers do their best, while their employers may not always care about proper behavior when it comes to contribute back to FLOSS

bgfellows 5y ago

The PSF has not really sponsored CPython so far, and PyCons are for self promotion. Often in OSS foundations the entire sponsorship money goes to people who don't deserve it. Please do not attach any meaning to corporate sponsorship of foundations unless you can point to a specific project. 99% of CPython has been written by individuals without any compensation who don't get any credit. When a corporation gives money to non-productive bureaucrats everyone thinks they are helping open source. It is very sad.

KptMarchewa 5y ago
Agreed with your comment. There are public reports of PSF, 75% of expenses go to US PyCon. https://www.python.org/psf/annual-report/2020/ https://www.python.org/psf/annual-report/2020/
- neolog 5y ago
  > In 2019, PyCon US generated 63% of the PSF’s revenue.
  - rpl101 5y ago
    Which makes it even more surprising where all that money goes. Hint: It is not CPython development.
  - KptMarchewa 5y ago
    63% of revenue and 75% of costs.
    - neolog 5y ago
      positive net revenue?

3v1n0 5y ago

Yeah but also... “If you want to upstream it, take it” it's not really something where ehi forked is working hard to send it back upstream patch by patch...

_carljm 5y ago
We've already upstreamed a lot of changes, including one that makes all coroutines faster in Python 3.10. The big-ticket items in Cinder would be big changes for CPython and need discussion about whether CPython even wants them. You don't just slap a C++ JIT into a bugs.python.org ticket. Opening Cinder is the first step in the conversation, and we're here for that work too. It's not just "if you want it, take it."
- 3v1n0 5y ago
  Ok great to hear that this is the case! Reading the README was a bit unclear on this topic. I also know that engineers do their best, while their employers may not always care about proper behavior when it comes to contribute back to FLOSS