1.16.2
api-change:organizations: [botocore] Update organizations client to latest version
api-change:globalaccelerator: [botocore] Update globalaccelerator client to latest version
api-change:kendra: [botocore] Update kendra client to latest version
api-change:ec2: [botocore] Update ec2 client to latest version
api-change:cloudfront: [botocore] Update cloudfront client to latest version
api-change:glue: [botocore] Update glue client to latest version
1.16.1
api-change:elasticbeanstalk: [botocore] Update elasticbeanstalk client to latest version
api-change:appsync: [botocore] Update appsync client to latest version
api-change:batch: [botocore] Update batch client to latest version
1.16.0
api-change:backup: [botocore] Update backup client to latest version
api-change:docdb: [botocore] Update docdb client to latest version
api-change:cloudfront: [botocore] Update cloudfront client to latest version
api-change:servicecatalog: [botocore] Update servicecatalog client to latest version
feature:imds: [botocore] Updated InstanceMetadataFetcher to use custom ipv6 uri as endpoint if envvar or config set
api-change:ssm: [botocore] Update ssm client to latest version
1.15.18
api-change:medialive: [botocore] Update medialive client to latest version
api-change:organizations: [botocore] Update organizations client to latest version
1.15.17
api-change:transfer: [botocore] Update transfer client to latest version
api-change:xray: [botocore] Update xray client to latest version
api-change:dms: [botocore] Update dms client to latest version
api-change:macie2: [botocore] Update macie2 client to latest version
api-change:ssm: [botocore] Update ssm client to latest version
api-change:groundstation: [botocore] Update groundstation client to latest version
api-change:rekognition: [botocore] Update rekognition client to latest version
api-change:ce: [botocore] Update ce client to latest version
api-change:workspaces: [botocore] Update workspaces client to latest version
api-change:glue: [botocore] Update glue client to latest version
api-change:budgets: [botocore] Update budgets client to latest version
api-change:accessanalyzer: [botocore] Update accessanalyzer client to latest version
api-change:rds: [botocore] Update rds client to latest version
api-change:workmail: [botocore] Update workmail client to latest version
api-change:iot: [botocore] Update iot client to latest version
1.15.16
api-change:snowball: [botocore] Update snowball client to latest version
api-change:servicecatalog: [botocore] Update servicecatalog client to latest version
api-change:eks: [botocore] Update eks client to latest version
api-change:amplify: [botocore] Update amplify client to latest version
api-change:medialive: [botocore] Update medialive client to latest version
1.15.15
api-change:ec2: [botocore] Update ec2 client to latest version
api-change:events: [botocore] Update events client to latest version
api-change:sns: [botocore] Update sns client to latest version
api-change:ce: [botocore] Update ce client to latest version
api-change:sagemaker: [botocore] Update sagemaker client to latest version
api-change:rds: [botocore] Update rds client to latest version
api-change:rekognition: [botocore] Update rekognition client to latest version
1.15.14
api-change:mediapackage: [botocore] Update mediapackage client to latest version
api-change:ce: [botocore] Update ce client to latest version
api-change:compute-optimizer: [botocore] Update compute-optimizer client to latest version
api-change:elasticache: [botocore] Update elasticache client to latest version
1.15.13
api-change:dms: [botocore] Update dms client to latest version
api-change:kinesisanalyticsv2: [botocore] Update kinesisanalyticsv2 client to latest version
api-change:marketplace-catalog: [botocore] Update marketplace-catalog client to latest version
api-change:ec2: [botocore] Update ec2 client to latest version
1.15.12
api-change:dynamodbstreams: [botocore] Update dynamodbstreams client to latest version
api-change:sagemaker: [botocore] Update sagemaker client to latest version
api-change:mediaconvert: [botocore] Update mediaconvert client to latest version
api-change:dynamodb: [botocore] Update dynamodb client to latest version
api-change:glue: [botocore] Update glue client to latest version
1.15.11
api-change:batch: [botocore] Update batch client to latest version
api-change:personalize-events: [botocore] Update personalize-events client to latest version
api-change:rds: [botocore] Update rds client to latest version
api-change:elbv2: [botocore] Update elbv2 client to latest version
api-change:servicediscovery: [botocore] Update servicediscovery client to latest version
api-change:s3: [botocore] Update s3 client to latest version
1.15.10
api-change:glue: [botocore] Update glue client to latest version
api-change:kafka: [botocore] Update kafka client to latest version
api-change:appsync: [botocore] Update appsync client to latest version
api-change:emr: [botocore] Update emr client to latest version
api-change:wafv2: [botocore] Update wafv2 client to latest version
api-change:quicksight: [botocore] Update quicksight client to latest version
1.15.9
api-change:datasync: [botocore] Update datasync client to latest version
api-change:s3control: [botocore] Update s3control client to latest version
api-change:imagebuilder: [botocore] Update imagebuilder client to latest version
api-change:securityhub: [botocore] Update securityhub client to latest version
api-change:iot: [botocore] Update iot client to latest version
api-change:emr: [botocore] Update emr client to latest version
api-change:s3outposts: [botocore] Update s3outposts client to latest version
api-change:application-autoscaling: [botocore] Update application-autoscaling client to latest version
api-change:directconnect: [botocore] Update directconnect client to latest version
api-change:s3: [botocore] Update s3 client to latest version
api-change:mediaconnect: [botocore] Update mediaconnect client to latest version
api-change:pinpoint: [botocore] Update pinpoint client to latest version
1.19.2
api-change:organizations: Update organizations client to latest version
api-change:globalaccelerator: Update globalaccelerator client to latest version
api-change:kendra: Update kendra client to latest version
api-change:ec2: Update ec2 client to latest version
api-change:cloudfront: Update cloudfront client to latest version
api-change:glue: Update glue client to latest version
1.19.1
api-change:elasticbeanstalk: Update elasticbeanstalk client to latest version
api-change:appsync: Update appsync client to latest version
api-change:batch: Update batch client to latest version
1.19.0
api-change:backup: Update backup client to latest version
api-change:docdb: Update docdb client to latest version
api-change:cloudfront: Update cloudfront client to latest version
api-change:servicecatalog: Update servicecatalog client to latest version
feature:imds: Updated InstanceMetadataFetcher to use custom ipv6 uri as endpoint if envvar or config set
api-change:ssm: Update ssm client to latest version
1.18.18
api-change:medialive: Update medialive client to latest version
api-change:organizations: Update organizations client to latest version
1.18.17
api-change:transfer: Update transfer client to latest version
api-change:xray: Update xray client to latest version
api-change:dms: Update dms client to latest version
api-change:macie2: Update macie2 client to latest version
api-change:ssm: Update ssm client to latest version
api-change:groundstation: Update groundstation client to latest version
api-change:rekognition: Update rekognition client to latest version
api-change:ce: Update ce client to latest version
api-change:workspaces: Update workspaces client to latest version
api-change:glue: Update glue client to latest version
api-change:budgets: Update budgets client to latest version
api-change:accessanalyzer: Update accessanalyzer client to latest version
api-change:rds: Update rds client to latest version
api-change:workmail: Update workmail client to latest version
api-change:iot: Update iot client to latest version
1.18.16
api-change:snowball: Update snowball client to latest version
api-change:servicecatalog: Update servicecatalog client to latest version
api-change:eks: Update eks client to latest version
api-change:amplify: Update amplify client to latest version
api-change:medialive: Update medialive client to latest version
1.18.15
api-change:ec2: Update ec2 client to latest version
api-change:events: Update events client to latest version
api-change:sns: Update sns client to latest version
api-change:ce: Update ce client to latest version
api-change:sagemaker: Update sagemaker client to latest version
api-change:rds: Update rds client to latest version
api-change:rekognition: Update rekognition client to latest version
1.18.14
api-change:mediapackage: Update mediapackage client to latest version
api-change:ce: Update ce client to latest version
api-change:compute-optimizer: Update compute-optimizer client to latest version
api-change:elasticache: Update elasticache client to latest version
1.18.13
api-change:dms: Update dms client to latest version
api-change:kinesisanalyticsv2: Update kinesisanalyticsv2 client to latest version
api-change:marketplace-catalog: Update marketplace-catalog client to latest version
api-change:ec2: Update ec2 client to latest version
1.18.12
api-change:dynamodbstreams: Update dynamodbstreams client to latest version
api-change:sagemaker: Update sagemaker client to latest version
api-change:mediaconvert: Update mediaconvert client to latest version
api-change:dynamodb: Update dynamodb client to latest version
api-change:glue: Update glue client to latest version
1.18.11
api-change:batch: Update batch client to latest version
api-change:personalize-events: Update personalize-events client to latest version
api-change:rds: Update rds client to latest version
api-change:elbv2: Update elbv2 client to latest version
api-change:servicediscovery: Update servicediscovery client to latest version
api-change:s3: Update s3 client to latest version
1.18.10
api-change:glue: Update glue client to latest version
api-change:kafka: Update kafka client to latest version
api-change:appsync: Update appsync client to latest version
api-change:emr: Update emr client to latest version
api-change:wafv2: Update wafv2 client to latest version
api-change:quicksight: Update quicksight client to latest version
1.18.9
api-change:datasync: Update datasync client to latest version
api-change:s3control: Update s3control client to latest version
api-change:imagebuilder: Update imagebuilder client to latest version
api-change:securityhub: Update securityhub client to latest version
api-change:iot: Update iot client to latest version
api-change:emr: Update emr client to latest version
api-change:s3outposts: Update s3outposts client to latest version
api-change:application-autoscaling: Update application-autoscaling client to latest version
api-change:directconnect: Update directconnect client to latest version
api-change:s3: Update s3 client to latest version
api-change:mediaconnect: Update mediaconnect client to latest version
api-change:pinpoint: Update pinpoint client to latest version
Release v1.33.1
This release contains refinements, improvements, and bug fixes, with highlights listed below.
Core
Deprecate GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS.
Expose Cronet error message to the application layer.
Remove grpc_channel_ping from surface API.
Do not send BDP pings if there is no receive side activity.
C++
Makefile: only support building deps from submodule.
C#
Add trimming attribute to BindServiceMethodAttribute.
Fix incremental build of csproj projects depending on grpc.
Python
[Backport] Make Python 2 an optional dependency for Bazel build.
Allow asyncio API to be imported as grpc.aio.
[gRPC Easy] Fix import errors on Windows.
Make version check for importlib.abc in grpcio-tools more stringent.
6.3p2
This release introduces a new utility called vidoas (vi doas). This tool is a
shell script which creates a copy of the doas.conf file, allows the admin to
edit the file, and then checks its syntax for errors. If a problem is found,
vidoas reports which line the error was on and asks us to try editing the file
again. Once the new doas.conf file contains the proper syntax, it is installed
and overwrites the old doas.conf file.
This tool is designed to assist admins and avoid introducing errors to doas.conf
which might accidentally revoke admin access to the machine.
6.3p1
In this release, we work around a quirk of the GNU parameter parser which
required us to use double-dashes (--) after doas's parameters and before a
target command's parameters. In the past we used "doas -- pacman -Syu" and now
we can use simply "doas pacman -Syu".
This change affects only GNU/Linux systems, other platforms like FreeBSD,
NetBSD, etc already had this behaviour.
6.3
This release introduces a few minor changes:
-Added command line parameter (-S) which launches an interactive shell. This is
equivalent to "su -l" or "sudo -i".
-Updated documentation to include the new -S flag.
-Updated documentation to assist users in installing doas on some Linux
distributions, such as CentOS, that prevent PAM authentication from working by
default.
6.2p5
This release simply adds a new sample PAM configuration file for FreeBSD (and
compatible systems). The new sample configuration file is named
campat/pam.conf.freebsd.
Calling setusercontext(3) makes per-user temporary storage work (see
per_user_tmp in security(7) and rc.conf(5)).
May as well use our reallocarray(3) instead of the bundled compat code.
Changes in MySQL 5.7.32 (2020-10-19, General Availability)
Functionality Added or Changed
Bugs Fixed
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved.
Bugs Fixed
InnoDB: A query that updated the clustered index of an internal temporary table returned an incorrect result. The modified pages of the clustered index were not added to the flush list resulting in lost changes when the modified pages were evicted from the buffer pool.
References: This issue is a regression of:
InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on a large encrypted and compressed table failed with a Page decompress failed after reading from disk error. The decryption operation did not use the encryption block size used during encryption. Also, the encryption process did not consider compressed length, while the decryption process decrypts data by compressed length only.
InnoDB: A failure occurred during a concurrent update operation. The failure was due to an invalid previous record value.
InnoDB: The function used to process the SHOW ENGINE INNODB MUTEX statement was insufficiently isolated from other threads adding new mutexes concurrently.
InnoDB: The buffer control block structure (buf_block_t) was freed while reducing the size of the buffer pool, causing an assertion failure. The fix for this bug also backports important aspects of the fix for
InnoDB: In session started with START TRANSACTION WITH CONSISTENT SNAPSHOT, a range query returned a truncated result. The end range flag was not reset at the beginning of the index read resulting in an aborted read and missing rows.
References: This issue is a regression of:
InnoDB: A full-text phrase search raised an assertion failure.
Thanks to TXSQL (Tencent MySQL) for the contribution.
References: This issue is a regression of:
InnoDB: A long running statistics calculation operation on a large table blocked other operations requiring access to the table's statistics, causing those operations to fail. A new statistics calculation mutex was introduced, which permits concurrent access table statistics.
Thanks to Kamil Holubicki for the contribution.
InnoDB: Two connections attempted to use the same transaction handler object resulting in a stalled query.
Replication: When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the table must be emptied by writing a statement to the binary log to that effect. Previously, this was a DELETE statement, but it is now a TRUNCATE TABLE statement. A replica server also writes this statement to its own binary log when it shuts down and restarts. The statement is always logged in statement format, even if the binary logging format is set to ROW, and it is written even if read_only or super_read_only mode is set on the server.
Replication: When the system variable session_track_gtids was set to OWN_GTID on a multithreaded replica, the replica’s performance would degrade over time and begin to lag behind the master. The cause was the buildup of the GTIDs recorded by the replica’s worker threads at each transaction commit, which increased the time taken by the worker threads to insert new ones. Session state tracking is now disabled for worker threads on a multithreaded replica. Thanks to Facebook for the contribution.
Certain cases of successful LDAP authentication could cause the server to hang.
In bootstrapping mode, certain multiple-statement transactions could cause unexpected server behavior.
Sensitive LDAP authentication plugin system variables now display as asterisks when retrieved in SQL statements.
After the fix for
References: This issue is a regression of:
Some INSERT statements were not handled correctly.
Certain prepared statements could cause an unexpected server exit.
mysqlpump object validation included objects in excluded databases.
LDAP authentication plugins enforced CA verification incorrectly, which could result in use of an incorrect CA.
ORDER BY queries were not executed correctly when sort_buffer_size and max_sort_length were set to values which caused the internal limit on the maximum number of keys allowed per sort buffer to be set to 0.
A large number of nested arguments in full-text search query caused an error.
When explicit_defaults_for_timestamp was disabled and a NULL was inserted into a generated column declared as TIMESTAMP NOT NULL, the server would attempt to convert the inserted value to CURRENT_TIMESTAMP. Such an insertion is now rejected with ER_BAD_NULL_ERROR.
An assertion could be raised when the SQL layer passed incorrect information to InnoDB about the type of operation to be performed on a temporary table.
pysmb-1.2.5
- Fix bug in filename encoding which leads to failure for file retrieval and upload operations
- Improve resetFileAttributes() method in SMBConnection class to allow the
new attribute to be specified in the reset operation
3.1.0
Added
Declare support for Python 3.9
testing/docs: Include doctests in testing
Allow custom "now" in naturaldelta and naturaltime
Fixed
Represent with a zero if the delta is too small
Update pkgsrc patches and remove the ones that were merged upstream.
Doom Legacy Changelog
1.48.6 SVN1550 (2020-09-09)
FEATURES 1.48.6
* DoomLegacy can read zip archives (Linux Only, enabled by compile option
ZIPWAD). When an load file is a zip archive, all loadable files within the
archive are loaded. When searching for a known file, zip archives of the
same name (but with .zip) are also searched.
This uses library libzip. When built with compile option ZIPWAD_OPTIONAL,
DoomLegacy detects if the libzip library is present on the user machine.
This allows DoomLegacy to run without the feature, when the user does not
have libzip.
A libzip before version 1.2 does not have a seek function. A compile
option will provide our own zip_seek function, so libzip 1.0 can be used.
* Recorded Demos now include both the Version and Revision numbers, so
revision specific behaviors can be enabled. DoomLegacy 1.48.6 has modified
its native demo format, which is revision specific. Older demo formats are
still playable.
* Recognize and handle DeePsea Tall patches. Enabled with compile option
DEEPSEA_TALL_PATCH. Michael Bauerle submitted the orignial patch, derived
from crispy doom.
BUG FIXES 1.48.6
* DoomLegacy and PrBoom monster infighting does not have missile
invulnerability between monsters of the same species. Some other ports
(Boom, MBF, Eternity engine) do not have the infight test, so their
monsters are always invulnerable to missiles from their own species.
Added another item to the infight control to select the behavior.
Implements "Full Infight" setting with missile damage (Legacy, PrBoom).
Implements other infight settings without missile damage (Boom, MBF,
Eternity).
Fixes BUG 0664.
Added MBF infight logic, thats stops monsters from firing on friends.
* Legacy demo would fail to start due to blocking the textcmd that loads the
map.
The Legacy 1.48.4 demo was recorded with player 0 issuing the map textcmd.
Player 0 was not in the game yet, and this was detected as a textcmd from
a non-existant player, which got caught by new security code. For textcmd
issued before player 0 is in the game, the demo needs to use SERVER_PID.
Fixed demo read to redirect player 0 demo textcmd to SERVER_PID.
DoomLegacy 1.48 has a single long combined textbuf, containing the textcmd
from all players. Within the combined textbuf, there are individual
textcmd marked with the player id. Individual textcmd are still limited to
255 chars as in an ordinary textbuf. The DoomLegacy 1.48.6 demo format has
been changed to store the entire combined textbuf buffer into the player 0
slot.
This is simpler for recording and playback, has the same effect, and
allows SERVER_PID textcmd, which the previous demo format did not.
The commands to create a player (and other server actions) are now issued
by SERVER_PID, where in older demos they were issued by player 0, before
player 0 existed. DoomLegacy 1.48 has better protection against malicious
network traffic than previous versions, and checking textcmd validity is
part of the security protection. This fixes demo playback to work with the
security checking.
Changed the SERVER_PID to 250 now, for future expansion of players.
This fixes bug 0665.
* Fixed the moonwalk bug, where monsters would sometimes walk backward. This
was due to a bad translation of an everything-in-one-expression to more
maintainable code.
* Make an oof sound when hit a 2s line, just like when hit a 1s line.
Adopted from PrBoom, a Killough enhancement.
* Make optional, and disabled, some old development hacks.
Option DEVPARM_LOADING:
Loaded development wads from a special directory. This used switches
-wart, -devgame (even older -shdev, -regdev, -comdev).
Option WADFILE_RELOAD:
If a filename started with a tilde "~", it was taken as an indication to
reload the file on every lump access. This was to enable leaving doom
running while changing wad files.
Option LOADING_DISK_ICON:
Not implemented in any port anyway.
* The Full Graphics startup was fragile, requiring constant fixing. Video
startup now changes directly to the config modes, which is faster and
cleaner. Removed some antiquated code and interactions, adopting an
interface that puts the main code in control.
* Fixed the violet line, trees, and tall sprites of "Lost civilization" wad.
This required being able to save the same texture as both a transparent
patch texture, for drawing hanging vines, and as a picture format texture,
for drawing tiled walls. This fixes Bug 0663.
* The fast drawing of wall textures required them to be a power-of-2 in
width, so they could be tiled. To handle the case where it is not a
power-of-2 in width, it now uses a slower masked draw similar to that in
PrBoom, which also handles a negative offset. This fixes the large tree in
"Lost civilization".
* Fixed some old code to use POSIX fcntl, which allows it to compile on
SunOS. Patches submitted by Michael Bauerle. Fixes Bug 0666.
* Noteworthy changes in release 3.7.3 (2020-10-13) [stable]
** Bug fixes
Fix concurrent build issues.
The bison executable is no longer linked uselessly against libreadline.
Fix incorrect use of yytname in glr.cc.
1.3.20
Released: October 12, 2020
orm
[orm] [bug]
An ArgumentError with more detail is now raised if the target parameter for Query.join() is set to an unmapped object. Prior to this change a less detailed AttributeError was raised. Pull request courtesy Ramon Williams.
[orm] [bug]
Fixed issue where using a loader option against a string attribute name that is not actually a mapped attribute, such as a plain Python descriptor, would raise an uninformative AttributeError; a descriptive error is now raised.
engine
[engine] [bug]
Fixed issue where a non-string object sent to SQLAlchemyError or a subclass, as occurs with some third party dialects, would fail to stringify correctly. Pull request courtesy Andrzej Bartosiński.
[engine] [bug]
Repaired a function-level import that was not using SQLAlchemy’s standard late-import system within the sqlalchemy.exc module.
sql
[sql] [bug]
Fixed issue where the pickle.dumps() operation against Over construct would produce a recursion overflow.
[sql] [bug]
Fixed bug where an error was not raised in the case where a column() were added to more than one table() at a time. This raised correctly for the Column and Table objects. An ArgumentError is now raised when this occurs.
postgresql
[postgresql] [usecase]
The psycopg2 dialect now support PostgreSQL multiple host connections, by passing host/port combinations to the query string. Pull request courtesy Ramon Williams.
See also
Specfiying multiple fallback hosts
[postgresql] [bug]
Adjusted the Comparator.any() and Comparator.all() methods to implement a straight “NOT” operation for negation, rather than negating the comparison operator.
[postgresql] [bug]
Fixed issue where the ENUM type would not consult the schema translate map when emitting a CREATE TYPE or DROP TYPE during the test to see if the type exists or not. Additionally, repaired an issue where if the same enum were encountered multiple times in a single DDL sequence, the “check” query would run repeatedly rather than relying upon a cached value.
mysql
[mysql] [usecase]
Adjusted the MySQL dialect to correctly parenthesize functional index expressions as accepted by MySQL 8. Pull request courtesy Ramon Williams.
[mysql] [bug]
The “skip_locked” keyword used with with_for_update() will emit a warning when used on MariaDB backends, and will then be ignored. This is a deprecated behavior that will raise in SQLAlchemy 1.4, as an application that requests “skip locked” is looking for a non-blocking operation which is not available on those backends.
[mysql] [bug]
Fixed bug where an UPDATE statement against a JOIN using MySQL multi-table format would fail to include the table prefix for the target table if the statement had no WHERE clause, as only the WHERE clause were scanned to detect a “multi table update” at that particular point. The target is now also scanned if it’s a JOIN to get the leftmost table as the primary table and the additional entries as additional FROM entries.
[mysql] [change]
Add new MySQL reserved words: cube, lateral added in MySQL 8.0.1 and 8.0.14, respectively; this indicates that these terms will be quoted if used as table or column identifier names.
mssql
[mssql] [bug]
Fixed issue where a SQLAlchemy connection URI for Azure DW with authentication=ActiveDirectoryIntegrated (and no username+password) was not constructing the ODBC connection string in a way that was acceptable to the Azure DW instance.
misc
[bug] [pool]
Fixed issue where the following pool parameters were not being propagated to the new pool created when Engine.dispose() were called: pre_ping, use_lifo. Additionally the recycle and reset_on_return parameter is now propagated for the AssertionPool class.
[bug] [associationproxy] [ext]
An informative error is now raised when attempting to use an association proxy element as a plain column expression to be SELECTed from or used in a SQL function; this use case is not currently supported.
[bug] [tests]
Fixed incompatibilities in the test suite when running against Pytest 6.x.
20.4:
Canonicalize version before comparing specifiers.
Change type hint for canonicalize_name to return packaging.utils.NormalizedName. This enables the use of static typing tools (like mypy) to detect mixing of normalized and un-normalized names.
20.3:
Fix changelog for 20.2.
20.2:
Fix a bug that caused a 32-bit OS that runs on a 64-bit ARM CPU (e.g. ARM-v8, aarch64), to report the wrong bitness.
20.1:
Fix a bug caused by reuse of an exhausted iterator.
20.0:
Add type hints
Add proper trove classifiers for PyPy support
Scale back depending on ctypes for manylinux support detection
Use sys.implementation.name where appropriate for packaging.tags
Expand upon the API provded by packaging.tags: interpreter_name(), mac_platforms(), compatible_tags(), cpython_tags(), generic_tags()
Officially support Python 3.8
Add major, minor, and micro aliases to packaging.version.Version
Properly mark packaging has being fully typed by adding a py.typed file
- 19961114 change: dns_ip() now recognizes [1.2.3.4] and [f80::a]. tnx DS.
- scan_long() included for mess822x support.
- constmap() added from qmail.
- Changed ipv4/6-localhost and ipv4/6-loopback to
ip4/6-localhost and ip4/6-loopback.
v2.0.0
importlib_metadata no longer presents a __version__ attribute. Consumers wishing to resolve the version of the package should query it directly with importlib_metadata.version('importlib-metadata').
v3.0.0
Package no longer exposes importlib_resources.__version__. Users that wish to inspect the version of importlib_resources should instead invoke .version('importlib_resources') from importlib-metadata ( stdlib or backport) directly. This change eliminates the dependency on importlib_metadata.
Package now always includes its data.
Declare hidden imports for PyInstaller.
v2.0.1
Select pathlib and contextlib imports based on Python version and avoid pulling in deprecated [pathlib](https://pypi.org/project/pathlib).
v2.0.0
Loaders are no longer expected to implement the abc.TraversableResources interface, but are instead expected to return TraversableResources from their get_resource_reader method.
