18.8.1
- add API to support cancellation; this means passing a 1-argument
callable to create_future and txaio.cancel to actually
cancel a future
- support Python 3.7 (CI / testing added)
11.1.0
- Add iglob method.
- Rename tempdir to TempDir and declare
it as part of __all__. Retain tempdir for compatibility
for now.
- TempDir.__enter__ no longer returns the TempDir
instance, but instead returns a Path instance, suitable for
entering to change the current working directory.
3.7.0:
Backwards-incompatible changes
* Pool database close_all() method renamed to close_idle() to better
reflect the actual behavior.
* Databases will now raise InterfaceError when connect() or close() are
called on an uninitialized, deferred database object.
New features
* Add methods to the migrations extension to support adding and dropping table
constraints.
* Add Model.bulk_create() method for bulk-inserting unsaved model instances.
* Add close_stale() method to the connection pool to support closing stale
connections.
* The FlaskDB class in playhouse.flask_utils now accepts a model_class
parameter, which can be used to specify a custom base-class for models.
Bugfixes
* Parentheses were not added to subqueries used in function calls with more
than one argument.
* Fixed bug when attempting to serialize many-to-many fields which were created
initially with a DeferredThroughModel.
* Fixed bug when using the Postgres ArrayField with an array of BlobField.
* Allow Proxy databases to be used as a context-manager.
* Fixed bug where the APSW driver was referring to the SQLite version from the
standard library sqlite3 driver, rather than from apsw.
* Reflection library attempts to wrap server-side column defaults in quotation
marks if the column data-type is text/varchar.
* Missing import in migrations library, which would cause errors when
attempting to add indexes whose name exceeded 64 chars.
* When using the Postgres connection pool, ensure any open/pending transactions
are rolled-back when the connection is recycled.
* Even *more* changes to the setup.py script. In this case I've added a
helper function which will reliably determine if the SQLite3 extensions can
be built. This follows the approach taken by the Python YAML package.
pytest 3.8.0:
Deprecations and Removals
- Config.warn has been deprecated, it should be replaced by calls to the standard warnings.warn.
Node.warn now supports two signatures:
* node.warn(PytestWarning("some message")): is now the recommended way to call this function. The warning
instance must be a PytestWarning or subclass instance.
* node.warn("CI", "some message"): this code/message form is now deprecated and should be converted to
the warning instance form above.
RemovedInPytest4Warning and PytestExperimentalApiWarning are now part of the public API and should be accessed
using pytest.RemovedInPytest4Warning and pytest.PytestExperimentalApiWarning.
- @pytest.mark.filterwarnings second parameter is no longer regex-escaped,
making it possible to actually use regular expressions to check the warning message.
**Note**: regex-escaping the match string was an implementation oversight that might break test suites which depend
on the old behavior.
Features
- Internal pytest warnings are now issued using the standard warnings module, making it possible to use
the standard warnings filters to manage those warnings. This introduces PytestWarning,
PytestDeprecationWarning and RemovedInPytest4Warning warning types as part of the public API.
- DeprecationWarning and PendingDeprecationWarning are now shown by default if no other warning filter is
configured.
- Add option to disable plugin auto-loading.
- Added the count option to console_output_style to enable displaying the progress as a count instead of a percentage.
- Added support for 'xfailed' and 'xpassed' outcomes to the pytester.RunResult.assert_outcomes signature.
- Terminal writer now takes into account unicode character width when writing out progress.
- Pytest now returns with correct exit code (EXIT_USAGEERROR, 4) when called with unknown arguments.
- Improve performance of assertion rewriting.
- Added a blurb in usage.rst for the usage of -r flag which is used to show an extra test summary info.
- Corrected type of the exceptions collection passed to xfail: raises argument accepts a tuple instead of list.
Trivial/Internal Changes
- Removed "run all (no recorded failures)" message printed with --failed-first and --last-failed when there are no failed tests.
* Version 1.34 (2018-03-31)
** libidn: Fix integer overflow in combine_hangul()
Found by fuzzing.
** libidn: Fix integer overflow in punycode decoder
Found by fuzzing, fix for the fix reported by Christian Weisgerber
** libidn: Fix performance issue in idna_to_unicode_internal()
Found by fuzzing.
** libidn: Fix performance issue in stringprep functions.
Found by fuzzing.
** libidn: Fix NULL pointer dereference in g_utf8_normalize()
Found by fuzzing.
** libidn: Fix NULL pointer dereference in stringprep_ucs4_nfkc_normalize()
Found by fuzzing.
** libidn: Increase performance of stringprep functions
Found by fuzzing.
** testing: Add OSS-fuzz integration and regression testing
** build: Update gnulib files
** build: Modernize GTK-Doc build
** build: Fix parallel builds
** build: Add configure flag --disable-doc
** build: Add configure flag --enable-ubsan (enable UB Sanitizer)
** build: Add configure flag --enable-asan (enable Address Sanitizer)
** build: Fix compiler warnings
** build: Fix build for gcc-7
** i18n: Added Swedish translation.
Thanks to Josef Andersson.
** API and ABI is backwards compatible with the previous version.
SECURITY:
- Random Byte Reading in Barrier: Prior to this release, Vault was not
properly checking the error code when reading random bytes for the IV for
AES operations in its cryptographic barrier. Specifically, this means that
such an IV could potentially be zero multiple times, causing nonce re-use
and weakening the security of the key. On most platforms this should never
happen because reading from kernel random sources is non-blocking and always
successful, but there may be platform-specific behavior that has not been
accounted for. (Vault has tests to check exactly this, and the tests have
never seen nonce re-use.)
FEATURES:
- AliCloud Agent Support: Vault Agent can now authenticate against the
AliCloud auth method.
- UI: Enable AliCloud auth method and Azure secrets engine via the UI.
IMPROVEMENTS:
- core: Logging level for most logs (not including secrets/auth plugins) can
now be changed on-the-fly via `SIGHUP`, reading the desired value from
Vault's config file
BUG FIXES:
- core: Ensure we use a background context when stepping down
- core: Properly check error return from random byte reading
- core: Re-add `sys/` top-route injection for now
- core: Properly store the replication checkpoint file if it's larger than the
storage engine's per-item limit
- identity: Update MemDB with identity group alias while loading groups
- secrets/database: Fix nil pointer when revoking some leases
- secrets/pki: Fix sign-verbatim losing extra Subject attributes
- secrets/pki: Remove certificates from store when tidying revoked
certificates and simplify API
- ui: JSON editor will not coerce input to an object, and will now show an
error about Vault expecting an object
- ui: authentication form will now default to any methods that have been tuned
to show up for unauthenticated users
Instead of hardcoding the check of 64bit platforms just reuse LP64PLATFORMS and
ABI (shamelessy stolen from lang/python27/Makefile).
This fixes the build of swi-prolog-lite on aarch64 and probably
other 64bit platforms too previously not listed.
2.6.0:
Dropped support for Python < 3.4, Pytest < 3.5 and Coverage < 4.4.
Fixed some documentation formatting. Contributed by Jean Jordaan and Julian.
Added an example with addopts in documentation.
Fixed TypeError: 'NoneType' object is not iterable in certain xdist configurations.
Added a no_cover marker and fixture.
Fixed broken no_cover check when running doctests.
Fixed various issues with path normalization in reports (when combining coverage data from parallel mode).
Report generation failures don’t raise exceptions anymore. A warning will be logged instead.
Fixed multiprocessing issue on Windows (empty env vars are not passed).
3.4.4:
Fix installation from sources when compiling toolkit is not available
3.4.3:
Add app.pre_frozen state to properly handle startup signals in sub-applications.
6.9.0:
[Core] Switched from culprit to transaction for automatic transaction reporting.
[CI] Removed py3.3 from build
[Django] resolved an issue where the log integration would override the user.
v6.5.2
- Fix import of :py:mod:cheroot.ssl.pyopenssl by refactoring and separating
:py:mod:cheroot.makefile's stream wrappers.
- Add initial tests for SSL layer with use of :py:mod:trustme
trustme is a tiny Python package that does one thing: it gives you a fake
certificate authority (CA) that you can use to generate fake TLS certs to use
in your tests. Well, technically they're real certs, they're just signed by
your CA, which nobody trusts. But you can trust it. Trust me.
There are no meaningful changes in this release compared to 0.1.6rc2, it
is primarily a tag update. However, adding gsed to USE_TOOLS fixes an
issue where the output of ldd was not parsed correctly by either illumos
sed or nbsed, resulting in dlopen failures for libusb-0.1.so.
Fixesjoyent/pkgsrc#117.
## 0.27.0 - 2018-09-05
### Added
- The Apache plugin now accepts the parameter --apache-ctl which can
be used to configure the path to the Apache control script.
### Changed
- When using `acme.client.ClientV2` (or
`acme.client.BackwardsCompatibleClientV2` with an ACME server that
supports a newer version of the ACME protocol), an
`acme.errors.ConflictError` will be raised if you try to create
an ACME account with a key that has already been used. Previously,
a JSON parsing error was raised in this scenario when using the
library with Let's Encrypt's ACMEv2 endpoint.
### Fixed
- When Apache is not installed, Certbot's Apache plugin no longer
prints messages about being unable to find apachectl to the
terminal when the plugin is not selected.
- If you're using the Apache plugin with the --apache-vhost-root flag
set to a directory containing a disabled virtual host for the
domain you're requesting a certificate for, the virtual host will
now be temporarily enabled if necessary to pass the HTTP challenge.
- The documentation for the Certbot package can now be built using
Sphinx 1.6+.
- You can now call `query_registration` without having to first call
`new_account` on `acme.client.ClientV2` objects.
- The requirement of `setuptools>=1.0` has been removed from
`certbot-dns-ovh`.
- Names in certbot-dns-sakuracloud's tests have been updated to refer
to Sakura Cloud rather than NS1 whose plugin certbot-dns-sakuracloud
was based on.
## 0.26.1 - 2018-07-17
### Fixed
- Fix a bug that was triggered when users who had previously manually
set `--server` to get ACMEv2 certs tried to renew ACMEv1 certs.
Switch to a bundled release for the assets, and make libretro-database
and glsls-headers current. This will make it easier to update versions
between releses where the database compatibility differs (e.g. for fbalpha)
Release 1.1.0:
* Added functionality to align chart category axis labels. See the
label_align property of the :func:set_x_axis() method.
* Added worksheet :func:hide_row_col_headers() method to turn off worksheet
row and column headings.
* Added the :func:set_tab_ratio() method to set the ratio between the
worksheet tabs and the horizontal slider.
* Fixed issue with icon conditional formats when the values were zero.
Release 1.7.9:
Features added
* Make generated texinfo files reproducible by sorting the anchors
Bugs fixed
* crashed on incremental build if document uses include directive
