Is there anything like GIL?

[yanchenghust]

As we know, CPython implemention has a GIL.
How about gpython?

[ncw]

gpython does not contain a GIL.

However it does not, as yet allow any sort of multiprocessing.

It is my plan to make a threading library which under the hood creates go routines. At this point it will need some sort of locking...

[sbinet]

by threading library, you mean exposing a gpython module to the Python interpreter, right?

the skylark Python-like VM has actually the concept of a Thread state that is passed to each API call...

• https://godoc.org/github.com/google/skylark#Thread

WDYT about this?

[ncw]

by threading library, you mean exposing a gpython module to the Python interpreter, right?

Yes. My plan was to make a low level module exposing some go features like goroutines, channels, locks etc, and use that low level module to build up something which was API compatible with the threading module.

the skylark Python-like VM has actually the concept of a Thread state that is passed to each API call...

That sounds like a job for a context passed everywhere. We've already identified somewhere else that would be very useful! Go having no thread local storage makes it very difficult to translate some bits of python.

• https://godoc.org/github.com/google/skylark#Thread

WDYT about this?

I think we'd almost certainly need something very similar! I'd propose to attach it to a context though.

[sbinet]

I think we'd almost certainly need something very similar! I'd propose to attach it to a context though.

SGTM. (we should probably make sure extracting informations and/or restoring state from that context.Context isn't showing abysmal performances, though.)

[ncw]

SGTM. (we should probably make sure extracting informations and/or restoring state from that context.Context isn't showing abysmal performances, though.)

Hmm, yes! AFAICS context is implemented as linked list, so the lookup isn't very efficient.

[drew-512]

I suggest to close this issue with the push of v0.1.0 (multi-context support)

[drew-512]

@yanchenghust v0.1.0 introduces py.Context which is the best-case scenario for concurrent interpreter execution while also aligned with Go programming patterns. For example:

for _, item := range items {
    go func() {
        ctx := py.NewContext(opts)
        ...
        setupState(ctx, item)
        py.Run*(ctx, ...)
        ...
        ctx.Close()
    }()
}

[sbinet]

fixed w/ #158