diff --git a/numpydonate.html b/numpydonate.html index e714082895349ff86b1430522f2053a768482a24_bnVtcHlkb25hdGUuaHRtbA==..ee04263f40411a0f4d649cf0786a60a64b3006e9_bnVtcHlkb25hdGUuaHRtbA== 100644 --- a/numpydonate.html +++ b/numpydonate.html @@ -45,6 +45,17 @@ <div> <div id="main"> <h1 class="title">Call for donations - PyPy to support Numpy!</h1> +<p>UPDATE (February 2014):</p> +<blockquote> +<em>Thanks to our donors, we have raised 77% 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.</em></blockquote> <p>This is a proposal to provide a fully compatible working <a class="reference external" href="http://numpy.scipy.org/">NumPy</a> implementation for PyPy. This has long been a very commonly <a class="reference external" href="http://morepypy.blogspot.com/2011/06/report-back-from-our-survey.html">requested feature</a> for PyPy as well as a worthy goal given that PyPy performs extremely well on numeric diff --git a/py3donate.html b/py3donate.html index e714082895349ff86b1430522f2053a768482a24_cHkzZG9uYXRlLmh0bWw=..ee04263f40411a0f4d649cf0786a60a64b3006e9_cHkzZG9uYXRlLmh0bWw= 100644 --- a/py3donate.html +++ b/py3donate.html @@ -45,6 +45,17 @@ <div> <div id="main"> <h1 class="title">Call for donations - PyPy to support Python3!</h1> +<p>UPDATE (February 2014):</p> +<blockquote> +<em>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.</em></blockquote> <p>The release of Python 3 has been a major undertaking for the Python community, both technically and socially. So far the PyPy interpreter implements only version 2 of the Python language and is increasingly diff --git a/source/numpydonate.txt b/source/numpydonate.txt index e714082895349ff86b1430522f2053a768482a24_c291cmNlL251bXB5ZG9uYXRlLnR4dA==..ee04263f40411a0f4d649cf0786a60a64b3006e9_c291cmNlL251bXB5ZG9uYXRlLnR4dA== 100644 --- a/source/numpydonate.txt +++ b/source/numpydonate.txt @@ -3,6 +3,19 @@ title: Call for donations - PyPy to support Numpy! --- +UPDATE (February 2014): + + *Thanks to our donors, we have raised 77% 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.* + + This is a proposal to provide a fully compatible working `NumPy`_ implementation for PyPy. This has long been a very commonly `requested feature`_ for PyPy as well as a worthy goal given that PyPy performs extremely well on numeric diff --git a/source/py3donate.txt b/source/py3donate.txt index e714082895349ff86b1430522f2053a768482a24_c291cmNlL3B5M2RvbmF0ZS50eHQ=..ee04263f40411a0f4d649cf0786a60a64b3006e9_c291cmNlL3B5M2RvbmF0ZS50eHQ= 100644 --- a/source/py3donate.txt +++ b/source/py3donate.txt @@ -3,6 +3,19 @@ title: Call for donations - PyPy to support Python3! --- +UPDATE (February 2014): + + *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.* + + The release of Python 3 has been a major undertaking for the Python community, both technically and socially. So far the PyPy interpreter implements only version 2 of the Python language and is increasingly diff --git a/source/tmdonate.txt b/source/tmdonate.txt index e714082895349ff86b1430522f2053a768482a24_c291cmNlL3RtZG9uYXRlLnR4dA==..ee04263f40411a0f4d649cf0786a60a64b3006e9_c291cmNlL3RtZG9uYXRlLnR4dA== 100644 --- a/source/tmdonate.txt +++ b/source/tmdonate.txt @@ -7,6 +7,18 @@ Transactional Memory / Automatic Mutual Exclusion ================================================= +UPDATE (February 2014): + + *Thanks to our donors, we have raised 52% 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.* + Introduction ============ diff --git a/tmdonate.html b/tmdonate.html index e714082895349ff86b1430522f2053a768482a24_dG1kb25hdGUuaHRtbA==..ee04263f40411a0f4d649cf0786a60a64b3006e9_dG1kb25hdGUuaHRtbA== 100644 --- a/tmdonate.html +++ b/tmdonate.html @@ -45,6 +45,17 @@ <div> <div id="main"> <h1 class="title">Call for donations - Transactional Memory / Automatic Mutual Exclusion in PyPy</h1> +<p>UPDATE (February 2014):</p> +<blockquote> +<em>Thanks to our donors, we have raised 52% 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.</em></blockquote> <div class="section" id="introduction"> <h1>Introduction</h1> <p>In the presence of today's machines with multiple processors, Python