You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add integer value functions.
* Add proper memory tracking to tests.
* Add tests for integer values.
* Fix unit test.
* Switch to Py_ssize_t
* Fix leak in backport of PyErr_SetRaisedException
* Add back cast.
* Switch to longs.
* Bump version to 1.1.0
* Switch to Py_CLEAR
* Refactor error return condition.
* Fix variable name in refactor.
* Explicitly use c_long in unit test.
* Fix use of c_ssize_t to c_long
* Fix reference leaks in error callbacks.
* Remove unneeded cleanup test.
* Don't hold strong reference to the gen wrapper.
* Nevermind.
* Fix double reference count.
* Remove memray files.
* Update changelog with previous fix.
* Apparently that broke everything.
* Remove changelog entry.
* Revert debug change.
* Some small reference fixes.
* Use preallocated callbacks for faster awaits.
* Fix reference leak with coroutine send().
* Update security policy.
* Add test for asyncio.gather()
* Update changelog.
* Add -W error to Memray tests.
* Remove -x flag from tests.
* Remove tests for gathering.
* Fix missing reference increase in backport of PyErr_SetRaisedException
Copy file name to clipboardExpand all lines: SECURITY.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,6 @@
4
4
5
5
Breaking API changes are made *only* between major versions. Deprecations may be made in between minor versions, but functions will not be removed until the next major version.
6
6
7
-
| Version | Supported |
8
-
| ------- | ------------------ |
9
-
| 1.0.x |:white_check_mark:|
10
-
11
7
## Reporting a Vulnerability
12
8
13
9
Depending on the severity of the vulnerability, you can make an issue on the [issue tracker](https://github.com/ZeroIntensity/pyawaitable/issues), or send an email explaining the vulnerability to <zintensitydev@gmail.com>
0 commit comments