summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Hide dev release from change log.HEADmasterMichael Howitz2023-04-201-6/+0
|
* Back to development: 6.2Michael Howitz2023-04-202-1/+7
|
* Preparing release 6.2a1.dev06.2a1.dev0Michael Howitz2023-04-202-3/+3
|
* Garden change log.Michael Howitz2023-04-201-2/+3
|
* Drop using `setup_requires`. (#98)Michael Howitz2023-04-207-40/+71
| | | | | * 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-067-9/+50
|
* Merge pull request #95 from cjwatson/pep-3114Colin Watson2023-03-025-10/+12
|\ | | | | Use PEP 3114 __next__ methods
| * Use PEP 3114 __next__ methodsColin Watson2023-02-285-10/+12
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-182-1/+5
|
* - prepare release 6.16.1Jens Vagelpohl2023-01-182-2/+2
|
* Merge pull request #94 from zopefoundation/dataflake/cleanup_py2_names_2Jens Vagelpohl2023-01-185-34/+16
|\ | | | | Remove more proxying code for names that no longer exist in Python 3
| * - Remove more proxying code for names that no longer exist in Python 3Jens Vagelpohl2023-01-175-34/+16
|/
* - prepare release 6.06.0Jens Vagelpohl2023-01-162-2/+2
|
* Merge pull request #93 from zopefoundation/dataflake/cleanup_py2_namesJens Vagelpohl2023-01-168-180/+14
|\ | | | | Remove proxying code for names that no longer exist in Python 3
| * - Remove proxying code for names that no longer exist in Python 3Jens Vagelpohl2023-01-156-178/+12
| |
| * - update to latest meta/configJens Vagelpohl2023-01-152-2/+2
|/
* - update to latest meta/configJens Vagelpohl2023-01-032-8/+8
|
* Config with c code template 831a34f5 (#91)Michael Howitz2022-12-2339-966/+400
| | | * Drop support for Python 2.7, 3.5, 3.6.
* Back to development: 5.9Michael Howitz2022-11-302-1/+7
|
* Preparing release 5.85.8Michael Howitz2022-11-302-2/+2
|
* Remove unused variable.Michael Howitz2022-11-301-1/+0
|
* Update to zope.untrustedpython >= 5. (#76)Michael Howitz2022-11-302-3/+5
| | | The extra ``untrustedpython`` now for Python 3, too, installs ``zope.untrustedpython``.
* - vb [ci skip]Jens Vagelpohl2022-11-172-1/+5
|
* - prepare release 5.75.7Jens Vagelpohl2022-11-172-2/+4
|
* - don't build/upload macOS universal2 wheels [ci skip]Jens Vagelpohl2022-11-171-31/+0
|
* - vb [ci skip]Jens Vagelpohl2022-11-162-1/+5
|
* - prepare release 5.6 and package cleanups5.6Jens Vagelpohl2022-11-166-17/+58
|
* - fix test failure by always pre-installing cffiJens Vagelpohl2022-11-131-0/+1
|
* - Add support for building arm64 wheels on macOS.Jens Vagelpohl2022-11-134-42/+89
|
* - vb [ci skip]Jens Vagelpohl2022-11-082-1/+5
|
* - update with meta/config to fix macOS build issues5.5Jens Vagelpohl2022-11-081-6/+6
|
* - lower deployment target again to match the existing zope.proxy eggJens Vagelpohl2022-11-071-2/+2
|
* - higher deployment targetJens Vagelpohl2022-11-071-1/+2
|
* - utilize flags for macOS similar to those used by cibuildwheelJens Vagelpohl2022-11-071-4/+5
|
* - declare Python 3.11 supportJens Vagelpohl2022-11-061-0/+1
|
* - prepare release 5.5Jens Vagelpohl2022-11-067-51/+18
|
* Back to development: 5.5Michael Howitz2022-09-152-1/+7
|
* Preparing release 5.45.4Michael Howitz2022-09-152-2/+2
|
* Merge pull request #89 from zopefoundation/config-with-c-codeMarius Gedminas2022-09-136-17/+90
|\ | | | | Update to the latest c-code template
| * Add a changelog noteMarius Gedminas2022-09-121-1/+2
| |
| * Configuring for c-codeMarius Gedminas2022-09-125-16/+88
|/ | | | | | Add a regression test for CFLAGS not having -Ofast, which is known to break things. See https://github.com/zopefoundation/meta/pull/155 for reference.
* Fix GHA Python 3.10 build on MacOS + PyPy-2.7 (#87)Michael Howitz2022-07-084-10/+36
| | | Built with https://github.com/zopefoundation/meta/pull/150.
* Update to Python 3.11b1 + fix doc creation.Michael Howitz2022-05-253-6/+8
| | | | Until `repoze.sphinx.autointerface` supports Sphinx 5 (which is used here because we support future python versions and activate installing pre-released package version, which is needed for some other packages to get a RestrictedPython which runs on Python 3.11) we have to use an older version.
* Back to development: 5.4Michael Howitz2022-04-272-1/+7
|
* Preparing release 5.35.3Michael Howitz2022-04-272-2/+2
|
* Apply isort rulesMichael Howitz2022-04-2234-136/+272
|
* Add support for Python 3.11Michael Howitz2022-04-227-9/+32
|
* Merge pull request #84 from zopefoundation/re-83-make-suites-newSteffen Allner2022-04-144-8/+12
|\ | | | | re #83: Remove `unittest.makeSuite` as it is deprecated in Python 3.11+.
| * re #83: Remove `unittest.makeSuite` as it is deprecated in Python 3.11+.Steffen Allner2022-04-134-8/+12
|/
* Fix badge.Michael Howitz2022-03-171-2/+2
|
View Lorry Controller Status