Merge pull request #60 from mattip/bitbucket-heptapod

mattip · web-flow · commit 1c5ee58729a2 · 2022-04-03T14:58:19.000+03:00
Change some blogpost links from bitbucket
diff --git a/posts/2017/10/cape-of-good-hope-for-pypy-hello-from-3656631725712879033.html b/posts/2017/10/cape-of-good-hope-for-pypy-hello-from-3656631725712879033.html
@@ -65,7 +65,7 @@
 slow logic;</li>
 <li>implement freelists to allocate the cpyext versions of <tt class="docutils literal">int</tt> and
 <tt class="docutils literal">tuple</tt> objects, as CPython does;</li>
-<li>the <a class="reference external" href="https://bitbucket.org/pypy/pypy/commits/branch/cpyext-avoid-roundtrip">cpyext-avoid-roundtrip</a> branch: crossing the RPython/C border is
+<li>the <a class="reference external" href="https://foss.heptapod.net/pypy/pypy/-/merge_requests/573">cpyext-avoid-roundtrip</a> branch: crossing the RPython/C border is
 slowish, but the real problem was (and still is for many cases) we often
 cross it many times for no good reason. So, depending on the actual API
 call, you might end up in the C land, which calls back into the RPython
@@ -110,6 +110,6 @@
 
 <br>
 <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody>
-<tr><td style="text-align: center;"><a href="https://bytebucket.org/pypy/extradoc/raw/extradoc/sprintinfo/cape-town-2017/2017-10-04-155524.jpg" style="margin-left: auto; margin-right: auto;"><img border="0" height="360" src="https://bytebucket.org/pypy/extradoc/raw/extradoc/sprintinfo/cape-town-2017/2017-10-04-155524.jpg" width="640"></a></td></tr>
+<tr><td style="text-align: center;"><a href="https://foss.heptapod.net/pypy/extradoc/-/blob/branch/extradoc/sprintinfo/cape-town-2017/2017-10-04-155524.jpg" style="margin-left: auto; margin-right: auto;"><img border="0" height="360" src="https://bytebucket.org/pypy/extradoc/raw/extradoc/sprintinfo/cape-town-2017/2017-10-04-155524.jpg" width="640"></a></td></tr>
 <tr><td class="tr-caption" style="text-align: center;">The panorama we looked at instead of staring at cpyext code</td></tr>
 </tbody></table></body></html>
diff --git a/posts/2017/10/cape-of-good-hope-for-pypy-hello-from-3656631725712879033.meta b/posts/2017/10/cape-of-good-hope-for-pypy-hello-from-3656631725712879033.meta
@@ -1,7 +1,7 @@
 .. title: (Cape of) Good Hope for PyPy
 .. slug: cape-of-good-hope-for-pypy-hello-from-3656631725712879033
 .. date: 2017-10-18 13:31:00
-.. tags: sprint,unicode,cpyext
+.. tags: sprint,unicode,cpyext,profile,speed
 .. description: 
 .. authors: Antonio Cuni
 .. id: 3656631725712879033
diff --git a/posts/2017/10/how-to-make-your-code-80-times-faster-1424098117108093942.html b/posts/2017/10/how-to-make-your-code-80-times-faster-1424098117108093942.html
@@ -72,7 +72,7 @@
 Generation   4: ... [population = 500]  [33.75 secs]
 </pre>
 Ouch! We are ~5.5x slower than CPython. This was kind of expected: numpy is
-based on cpyext, which is infamously slow.  (Actually, <a class="reference external" href="https://morepypy.blogspot.it/2017/10/cape-of-good-hope-for-pypy-hello-from.html">we are working on
+based on cpyext, which is infamously slow.  (Actually, <a class="reference external" href="https://pypy.org/posts/2017/10/cape-of-good-hope-for-pypy-hello-from-3656631725712879033.html">we are working on
 that</a> and on the <tt class="docutils literal"><span class="pre">cpyext-avoid-roundtrip</span></tt> branch we are already faster than
 CPython, but this will be the subject of another blog post.)<br>
 <br>
@@ -109,7 +109,7 @@
 operations.  The operations emitted for the line <tt class="docutils literal"><span class="pre">np.dot(...)</span> +
 self.constant</tt> are listed between lines 1217 and 1456. Here is the excerpt
 which calls <tt class="docutils literal"><span class="pre">np.dot(...)</span></tt>; most of the ops are cheap, but at line 1232 we
-see a call to the RPython function <a class="reference external" href="https://bitbucket.org/pypy/pypy/src/89d1f31fabc86778cfaa1034b1102887c063de66/pypy/module/micronumpy/ndarray.py?at=default&amp;fileviewer=file-view-default#ndarray.py-1168">descr_dot</a>; by looking at the
+see a call to the RPython function <a class="reference external" href="https://foss.heptapod.net/pypy/pypy/-/blob/release-pypy3.5-v5.10.0/pypy/module/micronumpy/ndarray.py#L1160">descr_dot</a>; by looking at the
 implementation we see that it creates a new <tt class="docutils literal">W_NDimArray</tt> to store the
 result, which means it has to do a <tt class="docutils literal">malloc()</tt>:<br>
 <div class="separator" style="clear: both; text-align: center;">
@@ -230,4 +230,4 @@ <h3>
 $ {python,pypy} -m ev.main
 </pre>
 </div>
-</div></body></html>
+</div></body></html>
diff --git a/posts/2017/10/how-to-make-your-code-80-times-faster-1424098117108093942.meta b/posts/2017/10/how-to-make-your-code-80-times-faster-1424098117108093942.meta
@@ -1,7 +1,7 @@
 .. title: How to make your code 80 times faster
 .. slug: how-to-make-your-code-80-times-faster-1424098117108093942
 .. date: 2017-10-30 10:15:00
-.. tags: 
+.. tags: jit, profiling, speed
 .. description: 
 .. authors: Antonio Cuni
 .. id: 1424098117108093942
diff --git a/posts/2018/09/the-first-15-years-of-pypy-3412615975376972020.html b/posts/2018/09/the-first-15-years-of-pypy-3412615975376972020.html
diff --git a/posts/2018/09/the-first-15-years-of-pypy-3412615975376972020.meta b/posts/2018/09/the-first-15-years-of-pypy-3412615975376972020.meta
@@ -1,7 +1,7 @@
 .. title: The First 15 Years of PyPy — a Personal Retrospective
 .. slug: the-first-15-years-of-pypy-3412615975376972020
 .. date: 2018-09-09 14:50:00
-.. tags: 
+.. tags: roadmap
 .. description: 
 .. authors: Carl Friedrich Bolz-Tereick
 .. id: 3412615975376972020
diff --git a/posts/2019/01/pypy-for-low-latency-systems-613165393301401965.html b/posts/2019/01/pypy-for-low-latency-systems-613165393301401965.html
@@ -83,7 +83,7 @@
 <br>
 Combining these two functions, it is possible to take control of the GC to
 make sure it runs only when it is acceptable to do so.  For an example of
-usage, you can look at the implementation of a <a class="reference external" href="https://bitbucket.org/antocuni/pypytools/src/0273afc3e8bedf0eb1ef630c3bc69e8d9dd661fe/pypytools/gc/custom.py?at=default&amp;fileviewer=file-view-default">custom GC</a> inside <a class="reference external" href="https://pypi.org/project/pypytools/">pypytools</a>.
+usage, you can look at the implementation of a <a class="reference external" href="https://github.com/antocuni/pypytools/blob/master/pypytools/gc/custom.py">custom GC</a> inside <a class="reference external" href="https://pypi.org/project/pypytools/">pypytools</a>.
 The peculiarity is that it also defines a "<tt class="docutils literal">with <span class="pre">nogc():"</span></tt> context manager
 which you can use to mark performance-critical sections where the GC is not
 allowed to run.<br>
@@ -109,4 +109,4 @@
 available in the nightly builds of PyPy, and will be included in the next
 release: take this as a New Year present :)<br>
 <br>
-Antonio Cuni and the PyPy team</body></html>
+Antonio Cuni and the PyPy team</body></html>
diff --git a/posts/2022/04/how-is-pypy-tested.rst b/posts/2022/04/how-is-pypy-tested.rst
@@ -61,7 +61,7 @@ PyPy Testing History
 
 A few historical notes on the PyPy project and its relationship to testing: The
 PyPy project `was started in 2004`_. At the time when the project was started,
-Extreme Programming and Agile Software Development where up and coming. On the
+Extreme Programming and Agile Software Development were up and coming. On the
 methodology side, PyPy was heavily influenced by these, and started using
 Test-Driven Development and pair programming right from the start.
 
