goesque
goesque patches Python function objects with a go() method backed by
gevent.spawn, so regular functions can be launched in a Go-like style.
Quick example
import goesque
goesque.patch_all()
def side_effect():
print("Side effect!")
side_effect.go()
# out: Side effect!
How it works
goesque.patch_all() does two things:
- Calls
gevent.monkey.patch_all()so standard library I/O becomes cooperative. - Patches
types.FunctionTypeso every Python function gains ago()method.
The patching is process-wide for the current interpreter. After patching, any
new or existing Python function object can call .go(...).
How go() is implemented
The go() method is installed at runtime and is equivalent to:
def go(self, *args, **kwargs):
import gevent
greenlet = gevent.spawn(self, *args, **kwargs)
gevent.sleep(0) # yield once so spawned work can start promptly
return greenlet
Notes:
go()returns a geventGreenlet.- Use
join()orget()when you need to wait for completion. - This is cooperative concurrency (greenlets), not native thread-based parallelism.
1 maintainer
Metadata
1 maintainer
Release files for goesque 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| goesque-0.1.0.tar.gz | 2.7 kB | With provenance | Details for goesque-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| goesque-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for goesque-0.1.0-py3-none-any.whl |
Total release size: 5.3 kB
Release files / goesque-0.1.0.tar.gz
| Download URL | goesque-0.1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6364443b199cc3beabe9953170a355b5d6ff68cd8fcac2df97b6ff6a6d18a5e6
|
|
BLAKE2b-256 checksum How to use checksums |
5c6191b6e268209ed9d9558e14a797f897a469ccad12902e45a2522e6b284817
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / goesque-0.1.0-py3-none-any.whl
| Download URL | goesque-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b94954cc8e2c6379063c5a645740fc731002ecd78812f953f064da3e728c0d85
|
|
BLAKE2b-256 checksum How to use checksums |
2ac2d4f65476ac3afe9a16e97dff6b51d5cb434a6613a8be35a479329d73677c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logSecurity for goesque 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for goesque-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
