On Sun, May 9, 2021 at 9:13 AM Antoine Pitrou wrote:
> On Sun, 09 May 2021 02:16:02 -
> "Jim J. Jewett" wrote:
> > Antoine Pitrou wrote:
> > > On Sat, 8 May 2021 02:58:40 +
> > > Neil Schemenauer nas-pyt...@arctrix.com wrote:
> >
> > > > It would be cool if we could mmap the pyc files
> I wasn’t able to find examples - is this what is up and running on
> docs.python.org, or is that a future plan?
I believe currently only the pre-release (3.10) documentation
https://docs.python.org/3.10/
and in-development (3.11) documentation https://docs.python.org/3.11/
is using the theme.
Thanks, Carol (and Olga)! This sounds great!
I’m sure you can all google :), but here’s the link:
https://github.com/python/python-docs-theme
I wasn’t able to find examples - is this what is up and running on
docs.python.org, or is that a future plan?
thanks much,
—titus
p.s. Not sure what
On Sat, 8 May 2021 21:59:49 +0100
Pablo Galindo Salgado wrote:
> > That could work, but in my personal opinion, I would prefer not to do
> that as it complicates things and I think is overkill.
>
> Let me expand on this:
>
> I recognize the problem that -OO can be quite unusable if some of
On Sun, 09 May 2021 02:16:02 -
"Jim J. Jewett" wrote:
> Antoine Pitrou wrote:
> > On Sat, 8 May 2021 02:58:40 +
> > Neil Schemenauer nas-pyt...@arctrix.com wrote:
>
> > > It would be cool if we could mmap the pyc files and have the VM run
> > > code without an unmarshal step.
> > >
On 5/9/21 3:00 AM, M.-A. Lemburg wrote:
> BTW: For better readability, I'd also not output the lines
> for every stack level in the traceback, but just the last one,
> since it's usually clear where the call to the next stack
> level happens in the upper ones.
Usually, sure -- but in the
Hi,
We have prepared a PEP with our proposal for fine-grained error locations
in tracebacks. You can find the PEP here:
https://www.python.org/dev/peps/pep-0657/
The discussion is happening in the discourse server:
On 5/9/21 3:00 AM, M.-A. Lemburg wrote:
BTW: For better readability, I'd also not output the lines
for every stack level in the traceback, but just the last one,
since it's usually clear where the call to the next stack
level happens in the upper ones.
Playing devil's advocate: in the
On 08.05.2021 23:55, Gregory P. Smith wrote:
> Who non-hypothetically cares about a 22% pyc file size increase? I don't
> think
> we should be concerned. I'm in favor of always writing them and the 20% size
> increase that results in. If pyc size is an issue that should be its own
> separate
