On Sat, Apr 11, 2020 at 03:17:07PM -0700, Mike Miller wrote:
> Python as π£ β π
> Python β π
For anyone else who had trouble seeing those glyphs, the ASCII
equivalent is:
Python as v --> e
Python ~= e
with the v and e in italics and the ~= meaning "approximately equal".
--
St
The relevant parties are aware.
On Sat, Apr 11, 2020, at 17:17, Mike Miller wrote:
>
> Unless I've read something wrong, it looks like the final Python 2 release
> (2.7.18) should approximate the math constant e:
>
> >>> import math
> >>> math.e
> 2.718281828459045
>
> Aka:
>
>
> -Original Message-
> From: Mike Miller
> Sent: Saturday, April 11, 2020 6:17 PM
> To: python-dev@python.org
> Subject: [Python-Dev] Python2 as π£ β π
>
>
> Unless I've read something wrong, it looks like the final Python 2 release
> (2.7.18) should approximate the math constant e:
>
>
Unless I've read something wrong, it looks like the final Python 2 release
(2.7.18) should approximate the math constant e:
>>> import math
>>> math.e
2.718281828459045
Aka:
Python as π£ β π
Python β π
Would be fun to note that in the announcement/docs somehow.
-Mike
___
Copy on writes are a big problem in large Python application that rely on
multiple processes sharing the same memory.
I just sent out a patch introduces Immortal Instances which allows the user to
bypass reference counting on specific objects to avoid CoW on forked processes.
This has helped in
This seems like a noble pursuit. File a bug on bugs.python.org with the
results you posted here, and submit a PR via GitHub (
github.com/python/cpython/).
On Sat, Apr 11, 2020 at 9:09 AM Barry Scott wrote:
> modulefinder.py does not open source files in "rb" which
> prevents compile() from apply
modulefinder.py does not open source files in "rb" which
prevents compile() from applying the encoding rules.
This first showed up for me on Windows with Python 3.8.
I'd like to provide patches for 3.8 (if any more releases)
and 3.9.
What is the process I should follow?
I have signed the Contrib
Thanks. I'm working to get https://github.com/python/steering-council/issues/3
resolved by April 17th to add an informational header to all the deep links
within https://docs.python.org/2/* . I welcome help on the pull requests linked
from that issue (such as https://github.com/python/cpython/pu
On 11/04/2020 13:08, Ivan Pozdeev via Python-Dev wrote:
On 10.04.2020 20:20, Victor Stinner wrote:
Stable ABI
--
The idea is to build a C extension only once: the built binary will be
usable on multiple Python runtimes and different versions of the same
runtime (stable ABI).
The idea
On 10.04.2020 20:20, Victor Stinner wrote:
Hi,
Here is a first draft a PEP which summarize the research work I'm
doing on CPython C API since 2017 and the changes that me and others
already made since Python 3.7 towards an "opaque" C API. The PEP is
also a collaboration with developers of PyPy,
On 10/04/2020 18:20, Victor Stinner wrote:
Note: Cython and cffi should be preferred to write new C extensions.
This PEP is about existing C extensions which cannot be rewritten with
Cython.
If this is true, the documentation on python.org needs a serious
rewrite. I am in the throes of writin
On Sat, 11 Apr 2020 01:52:13 +0200
Victor Stinner wrote:
>
> By the way, CPython currently uses statically allocated types for
> builtin types like str or list. This may have to change to run
> efficiently multiple subinterepters in parallel: each subinterpeter
> should have its own heap-allocate
On Sat, 11 Apr 2020 02:11:41 +0200
Victor Stinner wrote:
> Le ven. 10 avr. 2020 Γ 22:00, Antoine Pitrou a Γ©crit :
> > > Debug runtime and remove debug checks in release mode
> > > .
> > >
> > > If the C extensions are no longer tied to CPython i
13 matches
Mail list logo
