On a broader note, how does the deployment pipeline for documentation work?
It seems to me that for branches that are in pre-release (3.10) or active
development (3.11), the documentation should be continuously deployed,
while deployment of changes to earlier documentation should follow minor
Maybe we could specialize the heck out of this and not bother with a
function object? In the end we want to execute the code, the function
object is just a convenient way to bundle defaults, free variables (cells)
and globals. But co_annotation has no arguments or defaults, and is only
called
On Thu, Aug 12, 2021 at 08:26:47AM +0200, Marco Sulla wrote:
> No ideas? Excuse me for the up.
Perhaps you can be more concrete in what you expect from this mailing
list.
Are you looking for upvotes on StackOverflow (or however it works
there)? Or for some core dev to acknowledge that your
Has anyone raised this on bugs.python.org? That's the best way to get
something like this looked at, not via a post on Stack Overflow. The
SO posting didn't include a bpo link.
Paul
On Thu, 12 Aug 2021 at 07:33, Marco Sulla wrote:
>
> No ideas? Excuse me for the up.
>
> On Fri, 6 Aug 2021 at
On Aug 12, 2021, at 12:58, Jack DeVries wrote:
> > If you look at the version picker on docs.python.org you will see that we
> > already have the docs for 3.10 and 3.11 available. I don't know if they are
> > updated per release right now or per commit.
>
> I understand that they are available
On Thu, Aug 12, 2021 at 6:04 AM Jack DeVries wrote:
> On a broader note, how does the deployment pipeline for documentation
> work? It seems to me that for branches that are in pre-release (3.10) or
> active development (3.11), the documentation should be continuously
> deployed, while
On 8/12/21 8:25 AM, Guido van Rossum wrote:
Maybe we could specialize the heck out of this and not bother with a
function object? In the end we want to execute the code, the function
object is just a convenient way to bundle defaults, free variables
(cells) and globals. But co_annotation has
> If you look at the version picker on docs.python.org you will see that we
already have the docs for 3.10 and 3.11 available. I don't know if they are
updated per release right now or per commit.
I understand that they are available options. To clarify my suggestion, I
think that 3.11 should be
The Steering Council is a bit behind on the community updates, but we just
published the May and June ones (also included below):
https://github.com/python/steering-council/blob/main/updates/2021-05-steering-council-update.md
I will try to find time to review the code.
On Thu, Aug 12, 2021 at 08:56 Larry Hastings wrote:
>
> On 8/12/21 8:25 AM, Guido van Rossum wrote:
>
> Maybe we could specialize the heck out of this and not bother with a
> function object? In the end we want to execute the code, the function
>
No ideas? Excuse me for the up.
On Fri, 6 Aug 2021 at 21:29, Marco Sulla wrote:
>
> I've done an answer on SO about why subclassing `dict` makes the
> subclass so much slower than `dict`. The answer is interesting:
>
>
11.08.21 21:35, Brett Cannon пише:
> So my question is whether we want to push to be more diligent about
> updating What's New by b1 so people can provide feedback during the
> betas beyond just reporting breaking changes?
I think that What's New should be updated as soon as possible,
immediately
Lazy loading code object solves only a half of the problem.
I am worrying about function objects for annotation too.
Function objects are heavier than code objects. And they are GC-tracked objects.
I want to know how we can reduce the function objects created for
annotation in PEP 649, before
13 matches
Mail list logo
