| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
ChangeLog:
- macOS fix
|
|
Add upstream patch to fix build with latest meson.
1.70.0 - 2021-09-17
-------------------
* Update the GIR data for GLib, GObject, and GIO
1.69.0 - 2021-08-24
-------------------
* Fix build when gobject-introspection is a subproject :mr:`266`
* Add more float types :issue:`384`, :mr:`269`
* Make test suite work with cross-related options :issue:`227`
* Fix several leaks found by Coverity :mr:`272`
* Fix enum member c:identifier :mr:`264`
* Add g-ir-doc-tool man page :mr:`284`
* Export warnlib sources as variables :mr:`287`
* Update the GLib annotations :mr:`288`
* Add "final" class attribute :mr:`257`, :mr:`291`
* Add option to make .gir files installation paths configurable :mr:`63`
* Handle constructors with mismatched GTypes :issue:`399`, :mr:`292`
* Add property accessors annotations :issue:`13`, :mr:`279`
|
|
|
|
pytest-celery a shim pytest plugin to enable celery.contrib.pytest.
|
|
|
|
This pytest plugin was generated with Cookiecutter along with
@hackebrot's cookiecutter-pytest-plugin template.
* Adds support for TestCase.subTest.
* New subtests fixture, providing similar functionality for pure
pytest tests.
|
|
pytest 7.0.1 (2022-02-11)
Bug Fixes
#9608: Fix invalid importing of importlib.readers in Python
3.9.
#9610: Restore UnitTestFunction.obj to return unbound rather
than bound method. Fixes a crash during a failed teardown in
unittest TestCases with non-default __init__. Regressed in
pytest 7.0.0.
#9636: The pythonpath plugin was renamed to python_path. This
avoids a conflict with the pytest-pythonpath plugin.
#9642: Fix running tests by id with :: in the parametrize
portion.
#9643: Delay issuing a PytestWarning about diamond inheritance
involving Item and Collector so it can be filtered using standard
warning filters.
pytest 7.0.0 (2022-02-03)
(Please see the full set of changes for this release also in the
7.0.0rc1 notes below) Deprecations
#9488: If custom subclasses of nodes like pytest.Item override
the __init__ method, they should take **kwargs. See Constructors
of custom pytest.Node subclasses should take **kwargs for
details.
Note that a deprection warning is only emitted when there is
a conflict in the arguments pytest expected to pass. This
deprecation was already part of pytest 7.0.0rc1 but wasn’t
documented.
Bug Fixes
#9355: Fixed error message prints function decorators when
using assert in Python 3.8 and above.
#9396: Ensure pytest.Config.inifile is available during the
pytest_cmdline_main hook (regression during 7.0.0rc1).
Improved Documentation
#9404: Added extra documentation on alternatives to common
misuses of pytest.warns(None) ahead of its deprecation.
#9505: Clarify where the configuration files are located. To
avoid confusions documentation mentions that configuration file
is located in the root of the repository.
pytest 7.0.0rc1 (2021-12-06)
Breaking Changes
#7259: The Node.reportinfo() function first return value type
has been expanded from py.path.local | str to os.PathLike[str]
| str.
Most plugins which refer to reportinfo() only define it as part
of a custom pytest.Item implementation. Since py.path.local is
a os.PathLike[str], these plugins are unaffacted.
Plugins and users which call reportinfo(), use the first return
value and interact with it as a py.path.local, would need to
adjust by calling py.path.local(fspath). Although preferably,
avoid the legacy py.path.local and use pathlib.Path, or use
item.location or item.path, instead.
Note: pytest was not able to provide a deprecation period for
this change.
#8246: --version now writes version information to stdout rather
than stderr.
#8733: Drop a workaround for pyreadline that made it work with
--pdb.
The workaround was introduced in #1281 in 2015, however since
then pyreadline seems to have gone unmaintained, is generating
warnings, and will stop working on Python 3.10.
#9061: Using pytest.approx() in a boolean context now raises
an error hinting at the proper usage.
It is apparently common for users to mistakenly use pytest.approx
like this:
assert pytest.approx(actual, expected)
While the correct usage is:
assert actual == pytest.approx(expected)
The new error message helps catch those mistakes.
#9277: The pytest.Instance collector type has been removed.
Importing pytest.Instance or _pytest.python.Instance returns
a dummy type and emits a deprecation warning. See The
pytest.Instance collector for details.
#9308: PytestRemovedIn7Warning deprecation warnings are now
errors by default.
Following our plan to remove deprecated features with as little
disruption as possible, all warnings of type PytestRemovedIn7Warning
now generate errors instead of warning messages by default.
The affected features will be effectively removed in pytest
7.1, so please consult the Deprecations and Removals section
in the docs for directions on how to update existing code.
In the pytest 7.0.X series, it is possible to change the errors
back into warnings as a stopgap measure by adding this to your
pytest.ini file:
[pytest] filterwarnings =
ignore::pytest.PytestRemovedIn7Warning
But this will stop working when pytest 7.1 is released.
If you have concerns about the removal of a specific feature,
please add a comment to issue #9308.
Deprecations
#7259: py.path.local arguments for hooks have been deprecated.
See the deprecation note for full details.
py.path.local arguments to Node constructors have been deprecated.
See the deprecation note for full details.
Note
The name of the Node arguments and attributes (the new attribute
being path) is the opposite of the situation for hooks (the
old argument being path).
This is an unfortunate artifact due to historical reasons,
which should be resolved in future versions as we slowly get
rid of the py dependency (see issue #9283 for a longer discussion).
#7469: Directly constructing the following classes is now
deprecated:
_pytest.mark.structures.Mark
_pytest.mark.structures.MarkDecorator
_pytest.mark.structures.MarkGenerator
_pytest.python.Metafunc
_pytest.runner.CallInfo
_pytest._code.ExceptionInfo
_pytest.config.argparsing.Parser
_pytest.config.argparsing.OptionGroup
_pytest.pytester.HookRecorder
These constructors have always been considered private, but
now issue a deprecation warning, which may become a hard error
in pytest 8.
#8242: Raising unittest.SkipTest to skip collection of tests
during the pytest collection phase is deprecated. Use pytest.skip()
instead.
Note: This deprecation only relates to using unittest.SkipTest
during test collection. You are probably not doing that. Ordinary
usage of unittest.SkipTest / unittest.TestCase.skipTest() /
unittest.skip() in unittest test cases is fully supported.
#8315: Several behaviors of Parser.addoption are now scheduled
for removal in pytest 8 (deprecated since pytest 2.4.0):
parser.addoption(..., help=".. %default ..") - use %(default)s
instead.
parser.addoption(..., type="int/string/float/complex") -
use type=int etc. instead.
#8447: Defining a custom pytest node type which is both an
pytest.Item and a pytest.Collector (e.g. pytest.File) now issues
a warning. It was never sanely supported and triggers hard to
debug errors.
See the deprecation note for full details.
#8592: pytest_cmdline_preparse has been officially deprecated.
It will be removed in a future release. Use
pytest_load_initial_conftests instead.
See the deprecation note for full details.
#8645: pytest.warns(None) is now deprecated because many people
used it to mean “this code does not emit warnings”, but it
actually had the effect of checking that the code emits at
least one warning of any type - like pytest.warns() or
pytest.warns(Warning).
#8948: pytest.skip(msg=...), pytest.fail(msg=...) and
pytest.exit(msg=...) signatures now accept a reason argument
instead of msg. Using msg still works, but is deprecated and
will be removed in a future release.
This was changed for consistency with pytest.mark.skip and
pytest.mark.xfail which both accept reason as an argument.
#8174: The following changes have been made to types reachable
through pytest.ExceptionInfo.traceback:
The path property of _pytest.code.Code returns Path instead
of py.path.local.
The path property of _pytest.code.TracebackEntry returns
Path instead of py.path.local.
There was no deprecation period for this change (sorry!).
Features
#5196: Tests are now ordered by definition order in more cases.
In a class hierarchy, tests from base classes are now consistently
ordered before tests defined on their subclasses (reverse MRO
order).
#7132: Added two environment variables PYTEST_THEME and
PYTEST_THEME_MODE to let the users customize the pygments theme
used.
#7259: Added cache.mkdir(), which is similar to the existing
cache.makedir(), but returns a pathlib.Path instead of a legacy
py.path.local.
Added a paths type to parser.addini(), as in parser.addini("mypaths",
"my paths", type="paths"), which is similar to the existing
pathlist, but returns a list of pathlib.Path instead of legacy
py.path.local.
#7469: The types of objects used in pytest’s API are now exported
so they may be used in type annotations.
The newly-exported types are:
pytest.Config for Config.
pytest.Mark for marks.
pytest.MarkDecorator for mark decorators.
pytest.MarkGenerator for the pytest.mark singleton.
pytest.Metafunc for the metafunc argument to the
pytest_generate_tests hook.
pytest.CallInfo for the CallInfo type passed to various
hooks.
pytest.PytestPluginManager for PytestPluginManager.
pytest.ExceptionInfo for the ExceptionInfo type returned
from pytest.raises() and passed to various hooks.
pytest.Parser for the Parser type passed to the pytest_addoption
hook.
pytest.OptionGroup for the OptionGroup type returned from
the parser.addgroup method.
pytest.HookRecorder for the HookRecorder type returned from
Pytester.
pytest.RecordedHookCall for the RecordedHookCall type
returned from HookRecorder.
pytest.RunResult for the RunResult type returned from
Pytester.
pytest.LineMatcher for the LineMatcher type used in RunResult
and others.
pytest.TestReport for the TestReport type used in various
hooks.
pytest.CollectReport for the CollectReport type used in
various hooks.
Constructing most of them directly is not supported; they are
only meant for use in type annotations. Doing so will emit a
deprecation warning, and may become a hard-error in pytest 8.0.
Subclassing them is also not supported. This is not currently
enforced at runtime, but is detected by type-checkers such as
mypy.
#7856: –import-mode=importlib now works with features that
depend on modules being on sys.modules, such as pickle and
dataclasses.
#8144: The following hooks now receive an additional pathlib.Path
argument, equivalent to an existing py.path.local argument:
pytest_ignore_collect - The collection_path parameter
(equivalent to existing path parameter).
pytest_collect_file - The file_path parameter (equivalent
to existing path parameter).
pytest_pycollect_makemodule - The module_path parameter
(equivalent to existing path parameter).
pytest_report_header - The start_path parameter (equivalent
to existing startdir parameter).
pytest_report_collectionfinish - The start_path parameter
(equivalent to existing startdir parameter).
Note
The name of the Node arguments and attributes (the new attribute
being path) is the opposite of the situation for hooks (the
old argument being path).
This is an unfortunate artifact due to historical reasons,
which should be resolved in future versions as we slowly get
rid of the py dependency (see issue #9283 for a longer discussion).
#8251: Implement Node.path as a pathlib.Path. Both the old
fspath and this new attribute gets set no matter whether path
or fspath (deprecated) is passed to the constructor. It is a
replacement for the fspath attribute (which represents the same
path as py.path.local). While fspath is not deprecated yet due
to the ongoing migration of methods like reportinfo(), we expect
to deprecate it in a future release.
Note
The name of the Node arguments and attributes (the new attribute
being path) is the opposite of the situation for hooks (the
old argument being path).
This is an unfortunate artifact due to historical reasons,
which should be resolved in future versions as we slowly get
rid of the py dependency (see issue #9283 for a longer discussion).
#8421: pytest.approx() now works on Decimal within mappings/dicts
and sequences/lists.
#8606: pytest invocations with --fixtures-per-test and --fixtures
have been enriched with:
Fixture location path printed with the fixture name.
First section of the fixture’s docstring printed under the
fixture name.
Whole of fixture’s docstring printed under the fixture name
using --verbose option.
#8761: New pytest.version_tuple attribute, which makes it
simpler for users to do something depending on the pytest
version (such as declaring hooks which are introduced in later
versions).
#8789: Switch TOML parser from toml to tomli for TOML v1.0.0
support in pyproject.toml.
#8920: Added pytest.Stash, a facility for plugins to store
their data on Config and Nodes in a type-safe and conflict-free
manner. See Storing data on items across hook functions for
details.
#8953: RunResult method assert_outcomes now accepts a warnings
argument to assert the total number of warnings captured.
#8954: --debug flag now accepts a str file to route debug logs
into, remains defaulted to pytestdebug.log.
#9023: Full diffs are now always shown for equality assertions
of iterables when CI or BUILD_NUMBER is found in the environment,
even when -v isn’t used.
#9113: RunResult method assert_outcomes now accepts a deselected
argument to assert the total number of deselected tests.
#9114: Added pythonpath setting that adds listed paths to
sys.path for the duration of the test session. If you currently
use the pytest-pythonpath or pytest-srcpaths plugins, you should
be able to replace them with built-in pythonpath setting.
Improvements
#7480: A deprecation scheduled to be removed in a major version
X (e.g. pytest 7, 8, 9, …) now uses warning category
PytestRemovedInXWarning, a subclass of PytestDeprecationWarning,
instead of PytestDeprecationWarning directly.
See Backwards Compatibility Policy for more details.
#7864: Improved error messages when parsing warning filters.
Previously pytest would show an internal traceback, which
besides being ugly sometimes would hide the cause of the problem
(for example an ImportError while importing a specific warning
type).
#8335: Improved pytest.approx() assertion messages for sequences
of numbers.
The assertion messages now dumps a table with the index and
the error of each diff. Example:
> assert [1, 2, 3, 4] == pytest.approx([1, 3, 3, 5]) E
assert comparison failed for 2 values: E Index |
Obtained | Expected E 1 | 2 | 3 +- 3.0e-06
E 3 | 4 | 5 +- 5.0e-06
#8403: By default, pytest will truncate long strings in assert
errors so they don’t clutter the output too much, currently at
240 characters by default.
However, in some cases the longer output helps, or is even
crucial, to diagnose a failure. Using -v will now increase the
truncation threshold to 2400 characters, and -vv or higher will
disable truncation entirely.
#8509: Fixed issue where unittest.TestCase.setUpClass() is not
called when a test has / in its name since pytest 6.2.0.
This refers to the path part in pytest node IDs, e.g.
TestClass::test_it in the node ID
tests/test_file.py::TestClass::test_it.
Now, instead of assuming that the test name does not contain
/, it is assumed that test path does not contain ::. We plan
to hopefully make both of these work in the future.
#8803: It is now possible to add colors to custom log levels
on cli log.
By using add_color_level from a pytest_configure hook, colors
can be added:
logging_plugin = config.pluginmanager.get_plugin('logging-plugin')
logging_plugin.log_cli_handler.formatter.add_color_level(logging.INFO,
'cyan')
logging_plugin.log_cli_handler.formatter.add_color_level(logging.SPAM,
'blue')
See Customizing Colors for more information.
#8822: When showing fixture paths in --fixtures or --fixtures-by-test,
fixtures coming from pytest itself now display an elided path,
rather than the full path to the file in the site-packages
directory.
#8898: Complex numbers are now treated like floats and integers
when generating parameterization IDs.
#9062: --stepwise-skip now implicitly enables --stepwise and
can be used on its own.
#9205: pytest.Cache.set() now preserves key order when saving
dicts.
|
|
pkgsrc changes:
drop perl dependecy, it is only used when buildling docs
install license, needed when distributing the .h file
use gmake
changes:
new license, boost-license
fix installation on case-insensitive file systems
|
|
Mercurial 6.0.2
* Fix hg incoming and hg outgoing with remote subrepos on Windows
* Fix Rust build on MacOS
* Fix a (15 year old?) bug where some data loss could happen in
a very tight race window
* Remove support for running hg unamend on merge changesets at
it was never actually implemented
* Fix stream-clone requirements filtering which caused some
stream-clones to be unusable from an older version of Mercurial
* Rename dirstate-v2 configuration name from exp-rc-dirstate-v2
to use-dirstate-v2. This was overlooked in 6.0, the old name
will be kept as an alias for compatibility.
* Fix a bug where the branchmap could point to uncommitted data
|
|
2.10.8 (stable)
Build:
* Meson build: Perl is not required by new versions of mm-common
* NMake Makefiles: Support building with VS2022
Documentation:
* Upgrade the manual from DocBook 4.1 to DocBook 5.0
|
|
mm-common 1.0.4 (2022-02-11)
* Add util/doc_postprocess.py and util/doc_install.py.
Generating documentation in modules that use mm-common
does not require Perl in Meson builds.
Meson build and skeletonmm:
* Specify 'check' option in run_command().
The default value will change in future Meson releases.
|
|
Overview of changes in 1.48.11
==============================
* Be more careful with rounding
* Reinstate behavior of pango_attr_list_splice for gnumeric
|
|
Overview of changes in GLib 2.70.4
==================================
* Bugs fixed:
- Backport !2461 “Fix memory leak in gio/gdbusauthmechanismsha1.c” to glib-2-70
* Translation updates:
- Czech
- French
- Indonesian
- Japanese
- Polish
- Portuguese (Brazil)
- Russian
- Slovenian
- Spanish
- Swedish
- Ukrainian
Overview of changes in GLib 2.70.3
==================================
* Several important fixes to FD handling in gspawn
* Several important fixes to GDBus message and GVariant parsing of invalid data
* Fix potential data loss due to missing fsync when saving files on btrfs
* Bugs fixed:
- gspawn.c may clobber target fds
- gspawn.c fails to close child_err_report_fd if it is duped to avoid conflation with one of the target_fds
- Arrays of zero-element tuples with non-zero length lead to infinite loops in g_dbus_message_new_from_blob
- Check for GVariant recursion depth before recursing
- gspawn doesn't set CLOEXEC if close_range fails unexpectedly
- Backport !1968 “gspawn: Fix file descriptor conflation issues” to glib-2-70
- Backport !2412 “paramspec: fix unref annotation” to glib-2-70
- Backport !2425 “gfileutils: Remove outdated BTRFS fsync optimization from set_contents” to glib-2-70
- Backport !2435 “gspawn: Report errors with closing file descriptors between fork/exec” to glib-2-70
- Backport !2454 gdbusmessage and gvariant fixes to glib-2-70
* Translation updates:
- Czech
- Indonesian
- Italian
- Lithuanian
- Polish
- Portuguese
- Romanian
- Serbian
- Slovenian
- Spanish
- Swedish
- Turkish
- Ukrainian
|
|
Meson 0.61
backend_startup_project
Windows.compile_resources CustomTarget
Add a man page backend to refman
extract_objects() supports generated sources
Python 3.6 support will be dropped in the next release
Warning if check kwarg of run_command is missing
meson rewrite can modify extra_files
meson rewrite target <target> info outputs target's extra_files
Visual Studio 2022 backend
Support for CMake <3.14 is now deprecated for CMake subprojects
Added support for sccache
install_symlink function
|
|
"No valid Emacs version installed found"
Use a python language server with lsp-mode instead.
|
|
The list of changes since 2.0.2 is too long to paste here:
https://hackage.haskell.org/package/darcs-2.16.4/changelog
|
|
|
|
Class of filtrable containers, i.e. containers we can map over while
selectively dropping elements.
|
|
|
|
This module provides set and multiset operations on ordered lists.
|
|
|
|
GHC 7.4 gave us the ability to talk about ConstraintKinds. They stopped
crashing the compiler in GHC 7.6.
This package provides a vocabulary for working with them.
|
|
|
|
This library defines a propositional equality data type, shims
Data.Type.Equality as well as possible for older GHCs (< 7.8).
|
|
Upstream changes:
0.000144 2021-12-03 13:17:19-08:00 America/Los_Angeles
- Add void context warning for dies and lives
0.000143 2021-12-01 11:20:03-08:00 America/Los_Angeles
- Add stringification option for custom compare checks
0.000142 2021-11-15 14:06:34-08:00 America/Los_Angeles
- Fix deprecation diagnostics
- Fix older perls by removing //=
|
|
Introduction Reporter: by default, if you haven't set up any DiffTools,
a friendly message pointing you to documentation about reports will be
printed to your console.
|
|
Obsoleted by dune.
|
|
22.2.0 (2022-02-08)
===================
Features
--------
- Python 3.10 and PyPy 3.8 are now supported.
Bugfixes
--------
- Address a regression introduced in Treq 22.1.0 that prevented transmission of cookies with requests to ports other than 80, including HTTPS (443).
Deprecations and Removals
-------------------------
- Support for Python 3.6, which has reached end of support, is deprecated. This is the last release with support for Python 3.6.
|
|
### v1.1.0 2021-10-11 Paris (France)
- Add Keccak256 module (ethereum padding) (@maxtori, @dinosaure, #118)
- Update README.md to include the documentation (@mimoo, @dinosaure, 65a5c12)
- Remove deprecated function from `fmt` library (@dinosaure, #121)
- **NOTE**: This version lost the support of OCaml 4.03 and OCaml 4.04.
### v1.0.1 2020-02-08 Paris (France)
- Fix `esy` support (@dinosaure, #115)
- Fix big-endian support (@dinosaure, #113)
### v1.0.0 2020-11-02 Paris (France)
- **breaking changes** Upgrade the library with MirageOS 3.9 (new layout of artifacts)
Add tests about compilation of unikernels (execution and link)
(#105, @dinosaure, @hannesm)
- Fix `esy` installation (#104, @dinosaure)
- **breaking changes** Better GADT (#103, @dinosaure)
As far as I can tell, nobody really use this part of `digestif`.
The idea is to provide a GADT which contains the type of the hash.
From third-part libraries point-of-view, it's better to _pattern-match_ with
such information instead to use a polymorphic variant (as before).
- **breaking changes** key used for HMAC is a constant `string` (#101, @dinosaure, @hannesm)
The key should not follow the same type as the digest value (`string`, `bytes`, `bigstring`).
This update restricts the user to user only constant key (as a `string`).
### v0.9.0 2020-07-10 Paris (France)
- Add sha3 implementation (#98), @lyrm, @dinosaure, @hannesm and @cfcs
### v0.8.1 2020-06-15 Paris (France)
- Move to `dune.2.6.0` (#97)
- Apply `ocamlformat.0.14.2` (#97)
- Fix tests according `alcotest.1.0.0` (#95)
### v0.8.0 2019-20-09 Saint Louis (Sénégal)
- Fake version to prioritize dune's variants instead of
old linking trick
- Use `stdlib-shims` to keep compatibility with < ocaml.4.07.0
### v0.7.3 2019-07-09 Paris (France)
- Fix bug about specialization of BLAKE2{B,S} (#85, #86)
reported by @samoht, fixed by @dinosaure, reviewed by @hannes and @cfcs
|
|
Does not build, last upstream version from 2018, not used in pkgsrc.
|
|
|
|
### v0.3.2 2021-02-08 Arles (France)
- `freenstanding` support does not need `opam` (@sternenseemann, @dinosaure, #53)
- Fix big-endian support (@dinosaure, #56)
- Use `which` when `command -v` is not available (@dinosaure, @sternenseemann, @mseri, #56)
- Fix `esy` support and on its environment the MirageOS 3 support (@dinosaure, @mseri, #56)
- Upgrade to `ocamlformat.0.19.0` (@dinosaure, #57)
### v0.3.1 2021-23-02 Paris (France)
- Upgrade `checkseum` to `optint.0.0.5` (@dinosaure, #51)
### v0.3.0 2020-11-03 Paris (France)
- Upgrade C artifacts with MirageOS 3.9 (#50, @dinosaure, @hannesm)
- Fix `esy` installation (#49, @dinosaure, @jordwalke, reported by @Faliszek)
### v0.2.1 2020-06-15 Paris (France)
- Move to dune.2.6.0 (#47)
### v0.2.0 2020-06-03 Paris (France)
- fix cross-compilation with `dune -x windows` (#45, @dinosaure, @pirbo)
- add CRC-24 (#43, @dinosaure, @cfcs)
- factorize C stubs (as digestif)
- avoid clash of names when we use `checkseum.c`
Any functions are prefixed by `checkseum_`
- fix META file (#39 & #41, @hannesm, @dinosaure)
A test was added to see if runes (static C libraries) are available for
MirageOS targets (freestanding & xen)
- provide a binary `checkseum` to _digest_ standard input or file
`checkseum.checkseum` is available to compute check-sum of standard input
or file. The tool is used only for debugging.
- clean distribution (#38, @dinosaure)
`checkseum` depends only on `bigarray-compat`, `base-bytes` & `optint`
- `limits.h` is available on any targets (#37, @dinosaure, @pirbo)
### v0.1.1 2019-09-12 Paris (France)
- Compatibility with mirage+dune (#29, @dinosaure)
- Use `bigarray-compat` (#29, @TheLortex)
- Add constraints with < mirage-runtime.4.0.0
`checkseum` (as some others packages) must be used with MirageOS 4
where `checkseum.0.9.0` is a compatibility package with Mirage)S 3
- Replace `STDC` macro check by `STDDEF_H_` to be able to compile (#34, @dinosaure)
checkseum with +32bit compiler variant (#34, @dinosaure)
- Use a much more simpler implementation of CRC32C to be compatible with large set of targets (#34, @dinosaure)
- Avoid fancy operators in OCaml implementation of CRC32 and CRC32C (#34, @dinosaure)
- Require `optint.0.0.3` at least (#34, @dinosaure)
|
|
### v0.1.0 2021-03-30 Paris (France)
- Annotate integer types with `[@@immediate64]` (@CraigFe, #13)
- Move unwrapped module `Int63` to `Optint.Int63` (@CraigFe, #13)
### v0.0.5 2021-02-22 Paris (France)
- Update the README.md (@CraigFe, #9)
- Add a representation of 63-bit integers (@CraigFe, #9)
- Allow to compile fuzzers on 32-bit architectures (@dinosaure, #9)
- Add encode / decode functions for integers (@CraigFe, #9)
- Fix `optint` about sign and cast on all architectures (@dinosaure, #9)
- **breaking changes**, rename and handle properly sign-bit:
`{of,to}_int` become `{of,to}_unsigned_int`
`{of,to}_int32` become `{of,to}_unsigned_int32`
Previous functions handle sign-bit correctly
|
|
Use your fixtures in @pytest.mark.parametrize.
|
|
|
|
## 1.12.0 (2022-Jan-10)
- deprecate: module `pl.text` the contents have moved to `pl.stringx` (removal later)
[#407](https://github.com/lunarmodules/Penlight/pull/407)
- deprecate: module `pl.xml`, please switch to a more specialized library (removal later)
[#409](https://github.com/lunarmodules/Penlight/pull/409)
- feat: `utils.npairs` added. An iterator with a range that honours the `n` field
[#387](https://github.com/lunarmodules/Penlight/pull/387)
- fix: `xml.maptags` would hang if it encountered text-nodes
[#396](https://github.com/lunarmodules/Penlight/pull/396)
- fix: `text.dedent` didn't handle declining indents nor empty lines
[#402](https://github.com/lunarmodules/Penlight/pull/402)
- fix: `dir.getfiles`, `dir.getdirectories`, and `dir.getallfiles` now have the
directory optional, as was already documented
[#405](https://github.com/lunarmodules/Penlight/pull/405)
- feat: `array2d.default_range` now also takes a spreadsheet range, which means
also other functions now take a range. [#404](https://github.com/lunarmodules/Penlight/pull/404)
- fix: `lapp` enums allow [patterns magic characters](https://www.lua.org/pil/20.2.html)
[#393](https://github.com/lunarmodules/Penlight/pull/393)
- fix: `text.wrap` and `text.fill` numerous fixes for handling whitespace,
accented characters, honouring width, etc.
[#400](https://github.com/lunarmodules/Penlight/pull/400)
- feat: `text.wrap` and `text.fill` have a new parameter to forcefully break words
longer than the width given.
[#400](https://github.com/lunarmodules/Penlight/pull/400)
- fix: `stringx.expandtabs` could error out on Lua 5.3+
[#406](https://github.com/lunarmodules/Penlight/pull/406)
- fix: `pl` the module would not properly forward the `newindex` metamethod
on the global table.
[#395](https://github.com/lunarmodules/Penlight/pull/395)
- feat: `utils.enum` added to create enums and prevent magic strings
[#408](https://github.com/lunarmodules/Penlight/pull/408)
- change: `xml.new` added some sanity checks on input
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- added: `xml.xml_escape` and `xml.xml_unescape` functions (previously private)
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- feat: `xml.tostring` now also takes numeric indents (previously only strings)
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.walk` now detects recursion (errors out)
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.clone` now detects recursion (errors out)
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.compare` now detects recursion (errors out)
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.compare` text compares now work
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.compare` attribute order compares now only compare if both inputs provide an order
[#397](https://github.com/lunarmodules/Penlight/pull/397)
- fix: `xml.compare` child comparisons failing now report proper error
[#397](https://github.com/lunarmodules/Penlight/pull/397)
|
|
actively required.
|
|
|
|
|
|
|
|
7.0.2 (2022-02-08)
* No changes.
7.0.2.1 (2022-02-11)
* No changes.
7.0.2.2 (2022-02-11)
* No changes.
|
|
7.0.2 (2022-02-08)
* Revert the ability to pass service_name param to DirectUploadsController
which was introduced in 7.0.0.
That change caused a lot of problems to upgrade Rails applications so we
decided to remove it while in work in a more backwards compatible
implementation.
Gannon McGibbon
* Allow applications to opt out of precompiling Active Storage JavaScript
assets.
jlestavel
7.0.2.1 (2022-02-11)
* No changes.
7.0.2.2 (2022-02-11)
* No changes.
|
|
7.0.2 (2022-02-08)
* No changes.
7.0.2.1 (2022-02-11)
* No changes.
7.0.2.2 (2022-02-11)
* No changes.
|
|
7.0.2 (2022-02-08)
* Use different cache namespace for proxy calls
Models can currently have different attribute bodies for the same method
names, leading to conflicts. Adding a new namespace :active_model_proxy
fixes the issue.
Chris Salzberg
7.0.2.1 (2022-02-11)
* No changes.
7.0.2.2 (2022-02-11)
* No changes.
|
|
7.0.2 (2022-02-08)
* Fix ActiveSupport::EncryptedConfiguration to be compatible with Psych 4
Stephen Sugden
* Improve File.atomic_write error handling.
Daniel Pepper
7.0.2.1 (2022-02-11)
* No changes.
7.0.2.2 (2022-02-11)
* Fix Reloader method signature to work with the new Executor signature
|
|
This update contains security fix for CVE-2022-23633 in ruby-actionpack61.
Active Support 6.1.4.6 (2022-02-11)
* Fix Reloader method signature to work with the new Executor signature.
Action Pack 6.1.4.5 (2022-02-11)
* Under certain circumstances, the middleware isn't informed that the
response body has been fully closed which result in request state
not being fully reset before the next request.
[CVE-2022-23633]
Other packages have no change.
|
|
This update contains security fix for CVE-2022-23633 in ruby-actionpack60.
Active Support 6.0.4.6 (2022-02-11)
* Fix Reloader method signature to work with the new Executor signature.
Action Pack 6.0.4.6
6.0.4.5 (2022-02-11)
* Under certain circumstances, the middleware isn't informed that the
response body has been fully closed which result in request state
not being fully reset before the next request.
[CVE-2022-23633]
Other packages have no change.
|
|
This update contains security fix for CVE-2022-23633 in
Active Support 5.2.6.2 (2022-02-11)
* Fix Reloader method signature to work with the new Executor signature.
Action Pack 5.2.6.2 (2022-02-11)
* Under certain circumstances, the middleware isn't informed that the
response body has been fully closed which result in request state
not being fully reset before the next request.
[CVE-2022-23633]
|
|
2.2.1 (2022-02-11)
Fixed
* fixed Syntax version of absence groups ((?~...))
- the lexer accepted them for any Ruby version
- now they are only recognized for Ruby >= 2.4.1 in which they were
introduced
* reduced gem size by excluding specs from package
* removed deprecated test_files gemspec setting
* no longer depend on yaml/psych (except for Ruby <= 2.4)
* no longer depend on set
- set was removed from the stdlib and made a standalone gem as of Ruby 3
- this made it a hidden/undeclared dependency of regexp_parser
|
