For Donations, List How Much is Left (or Spent)?
Hey! So out of someone complaining about PyPy's lack of an up to date port of Python 3, it struck me that for someone just now looking into PyPy it looks like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 to 3.4. However the reality (via fijall) is that most of it, roughly 50k has already been spent going from nothing to 3.2. It might be a good idea to have the numbers reflect how much of the fundraised money has already been spent so that people get a more accurate reflection on just how much money there is left to take the task at hand from where it is now to where folks want it to be. My assumption is that people are going to feel a lot more like their money is going to be useful if it's not just adding onto the tail of what looks to be a fairly major pot of money and thus are more likely to actually donate. This of course doesn't just apply to Python 3 porting, the same thing is true for all of the fundraisers that PyPy is running. Without more information I have no way to evaluate if PyPy is sitting with cash reserves for that task and it's waiting for someone to work on it, or if it's mostly gone and it needs more funding to get any more effort applied to it. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
On June 1, 2015 at 4:00:09 PM, Donald Stufft (donald@stufft.io) wrote:
Also, if you read the actual proposal for Python 3, the last update to it says: Thanks to our donors, we have raised 45% of the total so far. Work on this topic has been happening, and continues to happen, within the budget – even if not within the timeline described below. We have simply not found enough time to work on it as much as we wanted, and thus did not consume the money as quickly as predicted. The ratio “progress / $ used” so far corresponds roughly to what we expected. The document below is the original call for proposal, and we still accept donations for this topic. Which would read to me like it confirms the above, that there is a surplus of money just sitting around waiting for someone to actually get around to working on the port and spend that money. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Hi Donald, hi everybody, On 1 June 2015 at 22:00, Donald Stufft <donald@stufft.io> wrote:
Thanks for bringing this up. I added to pypy.org the display of the amount left in our account for each project. Like the amount received, this number is updated from a source that depends on a manual step somewhere. This manual step is typically done only a few times per month. Don't be surprised if you donate and it does not show up immediately! Current situation: numpy: $52184 received, $15999 left py3k: $59578 received, $5045 left stm (2nd call): $29112 received, $22016 left We also have two Summer of Code projects, one related to numpy (performance via vectorization, not general compatibility) and one on py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is the version most used, trying to push forward). STM is progressing too, but I am alone on consuming the funds and recently I've been "side-tracked" by CFFI 1.0 (coming back to STM now). A bientôt, Armin.
Hi, I don't know it should help, however European Commission has simplified the process to help SMEs for the innovation: http://ec.europa.eu/research/participants/portal/desktop/en/funding/sme_part... The constraint is to have a legal company in the European Union, it should be also a consortium if several companies around PyPy are interested in. All details: http://ec.europa.eu/research/participants/portal/desktop/en/support/faq.html... I've received some feedbacks via my network about this funding, for now, it's an helpful operation. Moreover, European Commission is officially Open Source friendly: http://ec.europa.eu/dgs/informatics/oss_tech/index_en.htm Regards. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ 2015-06-05 9:35 GMT+02:00 Armin Rigo <arigo@tunes.org>:
2015-06-24 23:20 GMT+02:00 Phyo Arkar <phyo.arkarlwin@gmail.com>:
What do you guys think about skipping directly to pythin 3.5 and release it in-time when it releases?
Yes, it would be great to release 3.5 at the same time as CPython, but skipping releases won't make it faster. There are so many features to implement, many new modules. At least intermediate releases (3.3 and 3.4) make stable consistent milestones. Currently I'm kind of blocked on finishing the "more-rposix" branch (needed for the recent expansion of the posix module: os.supports_dir_fd...) It has still some failures: win32 does not translate, for example. Since it's mostly changes in rpython/ I wanted to make it land in the "default" branch first, but I'll probably move along and merge it into the py3.3 branch.
-- Amaury Forgeot d'Arc
Hi Amaury, On 25 June 2015 at 01:10, Amaury Forgeot d'Arc <amauryfa@gmail.com> wrote:
If it's only adding new functions, then I think it's fine to merge it to default even if some of these functions cause translation errors on Windows. The default pypy won't call them anyway. A bientôt, Armin.
2015-06-25 9:11 GMT+02:00 Armin Rigo <arigo@tunes.org>:
No, this branch is actually a full rewrite of the ll_os.py file, all the code has been moved to rposix.py. The code is much simpler (no lazy registering callback function), and we have a consistent way to add new wrapper to C functions, even if they don't map to any 2.7 feature. -- Amaury Forgeot d'Arc
On June 1, 2015 at 4:00:09 PM, Donald Stufft (donald@stufft.io) wrote:
Also, if you read the actual proposal for Python 3, the last update to it says: Thanks to our donors, we have raised 45% of the total so far. Work on this topic has been happening, and continues to happen, within the budget – even if not within the timeline described below. We have simply not found enough time to work on it as much as we wanted, and thus did not consume the money as quickly as predicted. The ratio “progress / $ used” so far corresponds roughly to what we expected. The document below is the original call for proposal, and we still accept donations for this topic. Which would read to me like it confirms the above, that there is a surplus of money just sitting around waiting for someone to actually get around to working on the port and spend that money. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Hi Donald, hi everybody, On 1 June 2015 at 22:00, Donald Stufft <donald@stufft.io> wrote:
Thanks for bringing this up. I added to pypy.org the display of the amount left in our account for each project. Like the amount received, this number is updated from a source that depends on a manual step somewhere. This manual step is typically done only a few times per month. Don't be surprised if you donate and it does not show up immediately! Current situation: numpy: $52184 received, $15999 left py3k: $59578 received, $5045 left stm (2nd call): $29112 received, $22016 left We also have two Summer of Code projects, one related to numpy (performance via vectorization, not general compatibility) and one on py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is the version most used, trying to push forward). STM is progressing too, but I am alone on consuming the funds and recently I've been "side-tracked" by CFFI 1.0 (coming back to STM now). A bientôt, Armin.
Hi, I don't know it should help, however European Commission has simplified the process to help SMEs for the innovation: http://ec.europa.eu/research/participants/portal/desktop/en/funding/sme_part... The constraint is to have a legal company in the European Union, it should be also a consortium if several companies around PyPy are interested in. All details: http://ec.europa.eu/research/participants/portal/desktop/en/support/faq.html... I've received some feedbacks via my network about this funding, for now, it's an helpful operation. Moreover, European Commission is officially Open Source friendly: http://ec.europa.eu/dgs/informatics/oss_tech/index_en.htm Regards. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ 2015-06-05 9:35 GMT+02:00 Armin Rigo <arigo@tunes.org>:
2015-06-24 23:20 GMT+02:00 Phyo Arkar <phyo.arkarlwin@gmail.com>:
What do you guys think about skipping directly to pythin 3.5 and release it in-time when it releases?
Yes, it would be great to release 3.5 at the same time as CPython, but skipping releases won't make it faster. There are so many features to implement, many new modules. At least intermediate releases (3.3 and 3.4) make stable consistent milestones. Currently I'm kind of blocked on finishing the "more-rposix" branch (needed for the recent expansion of the posix module: os.supports_dir_fd...) It has still some failures: win32 does not translate, for example. Since it's mostly changes in rpython/ I wanted to make it land in the "default" branch first, but I'll probably move along and merge it into the py3.3 branch.
-- Amaury Forgeot d'Arc
Hi Amaury, On 25 June 2015 at 01:10, Amaury Forgeot d'Arc <amauryfa@gmail.com> wrote:
If it's only adding new functions, then I think it's fine to merge it to default even if some of these functions cause translation errors on Windows. The default pypy won't call them anyway. A bientôt, Armin.
2015-06-25 9:11 GMT+02:00 Armin Rigo <arigo@tunes.org>:
No, this branch is actually a full rewrite of the ll_os.py file, all the code has been moved to rposix.py. The code is much simpler (no lazy registering callback function), and we have a consistent way to add new wrapper to C functions, even if they don't map to any 2.7 feature. -- Amaury Forgeot d'Arc
participants (6)
-
Amaury Forgeot d'Arc -
Armin Rigo -
Donald Stufft -
Ludovic Gasc -
Maciej Fijalkowski -
Phyo Arkar