Up to [cvs.NetBSD.org] / pkgsrc / devel / py-future
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-future: update to 1.0.0.
pkgsrc comment: this does not support Python 3.13.
The previous version didn't even support Python 3.12.
This package is still pulled in by ~15 packages, and if this
was a real problem, we probably would have noticed, so do not
mark this as not-for-3.13 for now.
Changes:
The new version number of 1.0.0 indicates that the python-future
project, like Python 2, is now done.
The most important change in this release is adding support for
Python 3.12 (ba1cc50 and a6222d2 and bcced95).
This release also includes these fixes:
Small updates to the docs
Add SECURITY.md describing security policy (0598d1b)
Fix pasteurize: NameError: name ‘unicode’ is not defined (de68c10)
Move CI to GitHub Actions (8cd11e8)
Add setuptools to requirements for building docs (0c347ff)
Fix typos in docs (350e87a)
Make the fix_unpacking fixer more robust (de68c10)
Small improvements to shell scripts according to shellcheck (6153844)
py-future: provide correct PLIST
py-future: updated to 0.18.2 What's new in version 0.18.2: ============================= This is a minor bug-fix release containing a number of fixes: - Fix min/max functions with generators, and 'None' default - Use BaseException in raise_() - Fix builtins.round() for Decimals - Fix raise_from() to prevent failures with immutable classes - Make FixInput idempotent - Fix type in newround - Support mimetype guessing in urllib2 for Py3.8+ Python 3.8 is not yet officially supported. What's new in version 0.18.1: ============================= This is a minor bug-fix release containing a fix for raise_() when passed an exception that's not an Exception (e.g. BaseException subclasses) What's new in version 0.18.0: ============================= This is a major bug-fix and feature release, including: - Fix collections.abc import for py38+ - Remove import for isnewbytes() function, reducing CPU cost significantly - Fix bug with importing past.translation when importing past which breaks zipped python installations - Fix an issue with copyreg import under Py3 that results in unexposed stdlib functionality - Export and document types in future.utils - Update behavior of newstr.__eq__() to match str.__eq__() as per reference docs - Fix raising and the raising fixer to handle cases where the syntax is ambigious - Allow "default" parameter in min() and max() - Implement __hash__() in newstr - Future proof some version checks to handle the fact that Py4 won't be a major breaking release - Fix urllib.request imports for Python 3.8 compatibility - Fix future import ordering - Fixed bug in fix_division_safe fixture - Do not globally destroy re.ASCII in PY3 - Fix a bug in email.Message.set_boundary() - Implement format_map() in str - Implement readinto() for socket.fp As well as a number of corrections to a variety of documentation, and updates to test infrastructure.
Add version suffix to binaries to allow multiple alternatives at once.
Update devel/py-future to 0.16.0. This release removes the configparser package as an alias for ConfigParser on Py2 to improve compatibility with Lukasz Langa's backported configparser package. Previously python-future and the configparser backport clashed, causing various compatibility issues. This releases also fixes these bugs: - Fix newbytes constructor bug. - Fix semantics of bool() with newobject. - Fix standard_library.install_aliases() on PyPy. - Fix assertRaises for pow and compile` on Python 3.5. - Fix return argument of future.utils.ensure_new_type if conversion to new type does not exist. - Add missing cmp_to_key for Py2.6. - Allow the old_div fixer to be disabled. - Improve compatibility with Google App Engine. - Add some missing imports to the tkinter and tkinter.filedialog package namespaces. - Fix raise_from on PY3 when the exception cannot be recreated from its repr.
Import wip/py-future as devel/py-future. future is the missing compatibility layer between Python 2 and Python 3. It allows you to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead.