summaryrefslogtreecommitdiff
path: root/CHANGES.rst
Commit message (Collapse)AuthorAgeFilesLines
* Hide dev release from change log.HEADmasterMichael Howitz2023-04-201-6/+0
|
* Back to development: 6.2Michael Howitz2023-04-201-0/+6
|
* Preparing release 6.2a1.dev06.2a1.dev0Michael Howitz2023-04-201-2/+2
|
* Garden change log.Michael Howitz2023-04-201-2/+3
|
* Drop using `setup_requires`. (#98)Michael Howitz2023-04-201-1/+3
| | | | | * Drop using ``setup_requires`` due to constant problems on GHA. * Add preliminary support for Python 3.12a7
* Add preliminary support for Python 3.12 as of 3.12a5. (#96)Michael Howitz2023-03-061-0/+2
|
* Use PEP 3114 __next__ methodsColin Watson2023-02-281-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | I got very confused recently when I had a security-proxied iterator using this sort of pattern: class Foo: def __iter__(self): return self def __next__(self): ... The value returned from `__iter__` is wrapped in a security proxy, and I found that unless I used `PURE_PYTHON=1` I got a `ForbiddenAttribute` exception trying to get the Python-2-style `next` method. This probably ought to have been noticed and fixed before we dropped support for Python 2, in which case a transition period of supporting both method names would have made sense. Now that we only support Python 3, I expect that any proxied objects that actually work as iterators will have a `__next__` method (and perhaps a vestigial `next` alias for compatibility), so I think we can just jump straight to only supporting `__next__` for both the C case and the pure-Python case. The C case is not actually being tested properly at the moment due to an oversight around the exact handling of the `PURE_PYTHON` environment variable, but fixing that will require coordinated changes to both `zope.security` and `zope.proxy`. I'll deal with that separately.
* - vb [ci skip]Jens Vagelpohl2023-01-181-0/+4
|
* - prepare release 6.16.1Jens Vagelpohl2023-01-181-1/+1
|
* - Remove more proxying code for names that no longer exist in Python 3Jens Vagelpohl2023-01-171-0/+7
|
* - prepare release 6.06.0Jens Vagelpohl2023-01-161-1/+1
|
* - Remove proxying code for names that no longer exist in Python 3Jens Vagelpohl2023-01-151-0/+3
|
* Config with c code template 831a34f5 (#91)Michael Howitz2022-12-231-2/+2
| | | * Drop support for Python 2.7, 3.5, 3.6.
* Back to development: 5.9Michael Howitz2022-11-301-0/+6
|
* Preparing release 5.85.8Michael Howitz2022-11-301-1/+1
|
* Update to zope.untrustedpython >= 5. (#76)Michael Howitz2022-11-301-0/+3
| | | The extra ``untrustedpython`` now for Python 3, too, installs ``zope.untrustedpython``.
* - vb [ci skip]Jens Vagelpohl2022-11-171-0/+4
|
* - prepare release 5.75.7Jens Vagelpohl2022-11-171-1/+3
|
* - vb [ci skip]Jens Vagelpohl2022-11-161-0/+4
|
* - prepare release 5.6 and package cleanups5.6Jens Vagelpohl2022-11-161-1/+1
|
* - Add support for building arm64 wheels on macOS.Jens Vagelpohl2022-11-131-0/+2
|
* - vb [ci skip]Jens Vagelpohl2022-11-081-0/+4
|
* - prepare release 5.5Jens Vagelpohl2022-11-061-2/+2
|
* Back to development: 5.5Michael Howitz2022-09-151-0/+6
|
* Preparing release 5.45.4Michael Howitz2022-09-151-1/+1
|
* Add a changelog noteMarius Gedminas2022-09-121-1/+2
|
* Back to development: 5.4Michael Howitz2022-04-271-0/+6
|
* Preparing release 5.35.3Michael Howitz2022-04-271-1/+1
|
* Add support for Python 3.11Michael Howitz2022-04-221-0/+2
|
* re #83: Remove `unittest.makeSuite` as it is deprecated in Python 3.11+.Steffen Allner2022-04-131-0/+4
|
* Fix default checker for method-wrapper on Python 3Colin Watson2022-03-101-1/+4
| | | | | | | | | The default checker for `method-wrapper` objects such as `().__repr__` and `{}.__repr__` was previously set by setting the default checker `type(().__getslice__)`, which only worked on Python 2. Use a different exemplar for this type which works on both Python 2 and 3. Fixes #75.
* Back to development: 5.3Michael Howitz2022-03-101-0/+6
|
* Preparing release 5.25.2Michael Howitz2022-03-101-1/+1
|
* Fix tests on Python 3.10 + lint.config-with-c-codeMichael Howitz2021-11-231-1/+1
|
* Lint the code.Michael Howitz2021-08-301-3/+3
| | | | Add support for Python 3.9.
* Back to development: 5.1.2Jason Madden2020-03-231-0/+6
|
* Preparing release 5.1.15.1.1Jason Madden2020-03-231-1/+1
|
* Ensure all objects have consistent interface resolution orders.Jason Madden2020-03-231-2/+4
| | | | Fixes #71
* Back to development: 5.2.0Michael Howitz2020-02-141-0/+6
|
* Preparing release 5.1.05.1.0Michael Howitz2020-02-141-1/+1
|
* Allow to use a common Sphinx version for Python 2 and 3. (#70)Michael Howitz2020-02-141-0/+2
| | | | | | * Allow to use a common Sphinx version for Python 2 and 3. * Work around pypa/virtualenv#1555
* Let interfaces be iterated on Python 3Jason Madden2020-02-061-5/+7
| | | | Fixes https://github.com/zopefoundation/zope.interface/issues/141
* Back to development: 5.1Marius Gedminas2019-11-111-0/+6
|
* Preparing release 5.05.0Marius Gedminas2019-11-111-1/+1
|
* Update changelogMarius Gedminas2019-11-111-0/+2
|
* Add Python 3.8 to appveyor.ymlappveyor-py38Marius Gedminas2019-11-101-1/+1
|
* Properly declare dependency on zope.schema >= 4.2.0Colin Watson2019-10-251-0/+3
| | | | This was introduced in zope.security 4.2.1.
* Update to current Python versions. (#61)Michael Howitz2019-04-061-3/+5
| | | | Additionally we have to pin an older `Sphinx` version to keep supporting Python 2.
* Back to development: 4.3.2Adam Groszer2019-01-031-0/+6
|
* Preparing release 4.3.14.3.1Adam Groszer2019-01-031-1/+1
|
View Lorry Controller Status