threading2: like the standard threading module, but awesomer.
This module is designed as a drop-in replacement and extension for the default “threading” module. It has two main objectives:
implement primitives using native platform functionality where possible
expose more sophisticated functionality where it can be done uniformly
The following extensions are currently implemented:
ability to set (advisory) thread priority
ability to set (advisory) CPU affinity at thread and process level
thread groups for simultaneous management of multiple threads
SHLock class for shared/exclusive (also known as read/write) locks
The following API niceties are also included:
all blocking methods take a “timeout” argument and return a success code
all exposed objects are actual classes and can be safely subclassed
This has currently only been tested on WinXP and Ubuntu Karmic; similar platforms should work OK, and other platforms should fall back to using sensible default behaviour, but I’m not making any guarantees at this stage.
Additional planned extensions include:
make stack_size a kwarg when creating a thread
native events, semaphores and timed waits on win32
native conditions and timed waits on pthreads platforms
native SHLock implementations (SRW on Win Vista+, pthread_rwlock)
Metadata
Release files for threading2 0.3.1
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 |
|---|---|---|---|---|
| threading2-0.3.1.tar.gz | 20.0 kB | Without provenance | Details for threading2-0.3.1.tar.gz |
Release files / threading2-0.3.1.tar.gz
| Download URL | threading2-0.3.1.tar.gz |
|---|---|
| Size | 20.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94b11388dd64b31b6ba8079f2d8d99abb2c18df21b2f2b5cb6464650445b19cc
|
|
BLAKE2b-256 checksum How to use checksums |
b53a283e51fa979d372139dc724d34ece957fbfc709b1ae7006b82ceb459fd4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for threading2 0.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.