Hello pypy.org webmasters,
while discussing with Armin Rigo the update of the documentation of
sandbox-2 on pypy.org, I realised,
that the README (in the root dir of the pypy.org repo) is still pointing
to the old yatiblog pages (source/README - which contains the old
yatiblog instructions).
On 29/3/20 11:43 pm, mark doerr wrote:
Hello pypy.org webmasters,
while discussing with Armin Rigo the update of the
documentation of sandbox-2 on pypy.org, I realised,
that the README (in the root dir of the pypy.org repo) is still
You're welcome, Matti, thanks for you fast reply. I will make a proposal
for an update. Just one question/comment, since you are at the very
beginning of your new repository: On our SiLA python repository (
https://gitlab.com/SiLA2/sila_python ) we are just using sphinx to
generate the gitLAB s
Those pages do look nice, and are very similar to doc.python.org
or doc.pypy.org (but with a nicer theme). However this repo
renders www.pypy.org, which is parallel to www.python.org, which
is the "non-developer front page" of pypy and python.
Your p
I see, Matti,
thanks for explaining the decision. These are valid arguments using
nikola (the blog post part I was not aware of).
Using the CI of heptapod might be really worth to have a closer look
into (that also might reduce errors, since everything relies only on one
service rather than
Hello,
On Mon, 30 Mar 2020 09:58:32 -0700
Brett Cannon wrote:
> On Sun, Mar 29, 2020 at 10:58 AM Paul Sokolovsky
> wrote:
>
> > [SNIP]
> >
> > 1. Succumb to applying the same mis-optimization for string type as
> > CPython3. (With the understanding that for speed-optimized projects,
> > implem
On Mon, Mar 30, 2020 at 10:24:02AM -0700, Andrew Barnert via Python-ideas wrote:
> On Mar 30, 2020, at 10:01, Brett Cannon wrote:
[talking about string concatenation]
> > I don't think characterizing this as a "mis-optimization" is fair.
[...]
> Yes. A big part of the reason there’s so much us
On Mon, Mar 30, 2020 at 12:37:48PM -0700, Andrew Barnert via Python-ideas wrote:
> On Mar 30, 2020, at 12:00, Paul Sokolovsky wrote:
> > Roughly speaking, to support efficient appending, one need to
> > be ready to over-allocate string storage, and maintain bookkeeping for
> > this. Another known
