python-greenlet
No description set
- Devel package for openSUSE:Factory
-
13
derived packages
- Links to openSUSE:Factory / python-greenlet
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:python/python-greenlet && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000150 150 Bytes | |
greenlet-3.0.0rc3.tar.gz | 0000174747 171 KB | |
python-greenlet-rpmlintrc | 0000000060 60 Bytes | |
python-greenlet.changes | 0000018087 17.7 KB | |
python-greenlet.spec | 0000002751 2.69 KB |
Revision 70 (latest revision is 89)
Dirk Mueller (dirkmueller)
committed
(revision 70)
- update to 3.0.0~rc3: * Fix an intermittent error during process termination on some platforms (GCC/Linux/libstdc++). * Fix some potential bugs (assertion failures and memory leaks) in previously-untested error handling code. In some cases, this means that the process will execute a controlled ``abort()`` after severe trouble when previously the process might have continued for some time with a corrupt state. It is unlikely those errors occurred in practice. * Fix some assertion errors and potential bugs with re-entrant switches. * Fix a potential crash when certain compilers compile greenlet with high levels of optimization. The symptom would be that switching to a greenlet for the first time immediately crashes. * Fix a potential crash when the callable object passed to the greenlet constructor (or set as the ``greenlet.run`` attribute) has a destructor attached to it that switches. Typically, triggering this issue would require an unlikely subclass of ``greenlet.greenlet``. * Python 3.11+: Fix rare switching errors that could occur when a garbage collection was triggered during the middle of a switch, and Python-level code in ``__del__`` or weakref callbacks switched to a different greenlet and ultimately switched back to the original greenlet. This often manifested as a ``SystemError``: "switch returned NULL without an exception set." * Python 3.12: Fix walking the frame stack of suspended greenlets. Previously accessing ``glet.gr_frame.f_back`` would crash due to `changes in CPython's undocumented internal frame handling * Make the platform-specific low-level C/assembly snippets stop using the ``register`` storage class. Newer versions of standards remove
Comments 1
Why did you accept this? The comments in changes do not match the changes in spec!