Version 3.1.0
- Dropped support for Python 3.4, added Python 3.8
- Add `__slots__` optimization in Node class, should give performance improvement
- Fixed:
- Restore universal wheels
- Bytes/str type incompatibility in setup.py
- New version of distutils rejects version suffixes of `.postNN`, use `aNN` instead
1.0.1
Add Python 3.9 and linux/arm64 wheels.
Fixed Unpacker.tell() after read_bytes()
Fixed unpacking datetime before epoch on Windows
Fixed fallback Packer didn't check DateTime.tzinfo
pytest 6.2.0 (2020-12-12)
=========================
Breaking Changes
----------------
- pytest now supports python3.6+ only.
Deprecations
------------
- Directly constructing/calling the following classes/functions is now deprecated:
- ``_pytest.cacheprovider.Cache``
- ``_pytest.cacheprovider.Cache.for_config()``
- ``_pytest.cacheprovider.Cache.clear_cache()``
- ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
- ``_pytest.capture.CaptureFixture``
- ``_pytest.fixtures.FixtureRequest``
- ``_pytest.fixtures.SubRequest``
- ``_pytest.logging.LogCaptureFixture``
- ``_pytest.pytester.Pytester``
- ``_pytest.pytester.Testdir``
- ``_pytest.recwarn.WarningsRecorder``
- ``_pytest.recwarn.WarningsChecker``
- ``_pytest.tmpdir.TempPathFactory``
- ``_pytest.tmpdir.TempdirFactory``
These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.
- The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.
We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).
- The ``@pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.
``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.
Features
--------
- pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python>=3.8.
See :ref:`unraisable` for more information.
- New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.
This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.
Internally, the old :class:`Testdir <_pytest.pytester.Testdir>` is now a thin wrapper around :class:`Pytester <_pytest.pytester.Pytester>`, preserving the old interface.
- A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
This dictionary will be used to augment the "global" variables available to evaluate skipif/xfail/xpass markers.
Pseudo example
``conftest.py``:
.. code-block:: python
def pytest_markeval_namespace():
return {"color": "red"}
``test_func.py``:
.. code-block:: python
@pytest.mark.skipif("color == 'blue'", reason="Color is not red")
def test_func():
assert False
- It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
from the private `_pytest.monkeypatch.MonkeyPatch` namespace.
Additionally, :meth:`MonkeyPatch.context <pytest.MonkeyPatch.context>` is now a classmethod,
and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
is not ``undo()``-ed automatically.
Improvements
------------
- Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.
- Verbose mode now shows the reason that a test was skipped in the test's terminal line after the "SKIPPED", "XFAIL" or "XPASS".
- The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
The newly-exported types are:
- ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
- ``pytest.Cache`` for the :fixture:`cache` fixture.
- ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
- ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
- ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
- ``pytest.Pytester`` for the :fixture:`pytester` fixture.
- ``pytest.Testdir`` for the :fixture:`testdir` fixture.
- ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
- ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
- ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
- ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.
Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.
Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.
- When a comparison between :func:`namedtuple <collections.namedtuple>` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.
- :meth:`Node.warn <_pytest.nodes.Node.warn>` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning <pytest.PytestWarning>`.
- Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.
- Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
raising :class:`TypeError`.
This was the undocumented behavior before 3.7, but is now officially a supported feature.
- New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.
- Added ``'node_modules'`` to default value for :confval:`norecursedirs`.
- :meth:`doClassCleanups <unittest.TestCase.doClassCleanups>` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.
Bug Fixes
---------
- Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.
- Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.
- Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.
- Fixed a crash or hang in :meth:`pytester.spawn <_pytest.pytester.Pytester.spawn>` when the :mod:`readline` module is involved.
- Fixed handling of recursive symlinks when collecting tests.
- Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.
- Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.
Improved Documentation
----------------------
- Add more information and use cases about skipping doctests.
- Classes which should not be inherited from are now marked ``final class`` in the API reference.
- ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``"string"``.
- In pull request section, ask to commit after editing changelog and authors file.
Trivial/Internal Changes
------------------------
- The ``attrs`` dependency requirement is now >=19.2.0 instead of >=17.4.0.
- `.pyc` files created by pytest's assertion rewriting now conform to the newer PEP-552 format on Python>=3.7.
(These files are internal and only interpreted by pytest itself.)
0.36.2
- Updated vendored ``packaging`` library to v20.8
- Fixed wheel sdist missing ``LICENSE.txt``
- Don't use default ``macos/arm64`` deployment target in calculating the
platform tag for fat binaries
# testthat 3.0.0
## 3rd edition
testhat 3.0.0 brings with it a 3rd edition that makes a number of breaking
changes in order to clean up the interface and help you use our latest
recommendations. To opt-in to the 3rd edition for your package, set
`Config/testthat/edition: 3` in your `DESCRIPTION` or use `local_edition(3)` in
individual tests. You can retrieve the active edition with `edition_get()`.
Learn more in `vignette("third-edition")`.
* `context()` is deprecated.
* `expect_identical()` and `expect_equal()` use `waldo::compare()` to
compare actual and expected results. This mostly yields much more
informative output when the actual and expected values are different,
but while writing it uncovered some bugs in the existing comparison
code.
* `expect_error()`, `expect_warning()`, `expect_message()`, and
`expect_condition()` now all use the same underlying logic: they
capture the first condition that matches `class`/`regexp` and
allow anything else to bubble up (#998/#1052). They also warn if
there are unexpected arguments that are never used.
* The `all` argument to `expect_message()` and `expect_warning()` is now
deprecated. It was never a particularly good idea or well documented,
and is now superseded by the new condition capturing behaviour.
* `expect_equivalent()`, `expect_reference()`, `expect_is()` and
`expect_that()` are deprecated.
* Messages are no longer automatically silenced. Either use
`suppressMessages()` to hide unimportant messages, or
`expect_messsage()` to catch important messages (#1095).
* `setup()` and `teardown()` are deprecated in favour of test fixtures.
See `vignette("test-fixtures")` for more details.
* `expect_known_output()`, `expect_known_value()`, `expect_known_hash()`,
and `expect_equal_to_reference()` are all deprecated in favour of
`expect_snapshot_output()` and `expect_snapshot_value()`.
* `test_that()` now sets a number of options and env vars to make output as
reproducible as possible (#1044). Many of these options were previously
set in various places (in `devtools::test()`, `test_dir()`, `test_file()`,
or `verify_output()`) but they have now been centralised. You can use in
your own code, or when debugging tests interactively with
`local_test_context()`.
* `with_mock()` and `local_mock()` are deprecated; please use the mockr
or mockery packages instead (#1099).
## Snapshot testing
New family of snapshot expectations (`expect_snapshot()`, `expect_snapshot_output()`, `expect_snapshot_error()`, and `expect_snapshot_value()`) provide "snapshot" tests, where the expected results are stored in separate files in `test/testthat/_snaps`. They're useful whenever it's painful to store expected results directly in the test files.
`expect_snapshot_file()` along with `snapshot_review()` help snapshot
more complex data, with initial support for text files, images, and data frames (#1050).
See `vignette("snapshotting")` for more details.
## Reporters
* `CheckReporter` (used inside R CMD check) now prints out all problems
(i.e. errors, failures, warnings and skips; and not just the first 10),
lists skips types, and records problems in machine readable format in
`tests/testthat-problems.rds` (#1075).
* New `CompactProgressReporter` tweaks the output of `ProgressReporter` for
use with a single file, as in `devtools::test_file()`. You can pick a
different default by setting `testthat.default_compact_reporter` to
the name of a reporter.
* `ProgressReporter` (the default reporter) now keeps the stack traces of
an errors that happen before the before test, making problems substantially
easier to track down (#1004). It checks if you've exceeded the maximum number
of failures (from option `testthat.progress.max_fails`) after each
expectation, rather than at the end of each file (#967). It also gains
new random praise options that use emoji, and lists skipped tests by type
(#1028).
* `StopReporter` adds random praise emoji when a single test passes (#1094).
It has more refined display of failures, now using the same style
as `CompactProgressReporter` and `ProgressReporter`.
* `SummaryReporter` now records file start, not just context start. This
makes it more compatible with modern style which does not use `context()`
(#1089).
* All reporters now use exactly the same format when reporting the location
of an expectation.
* Warnings now include a backtrace, making it easier to figure
out where they came from.
* Catch C++ tests now provide detailed results for each test.
To upgrade existing code, re-run `testthat::use_catch()` (#1008).
## Fixures
* New `vignette("test-fixtures")` describes test fixtures; i.e. how to
temporarily and cleanly change global state in order to test parts of
your code that otherwise would be hard to run (#1042). `setup()` and
`teardown()` are superseded in favour of test fixtures.
* New `teardown_env()` for use with `withr::defer()`. This allows you to
run code after all other tests have been run.
## Skips
* New `vignette("skipping")` gives more general information on skipping
tests, include some basics on testing skipping helpers (#1060).
* `ProgressReporter()` and `CheckReporter()` list the number of skipped tests
by reason at the end of the reporter. This makes it easier to check that
you're not skipping the wrong tests, particularly on CI services (#1028).
## Test running
* `test_that()` no longer triggers an error when run outside of tests;
instead it produces a more informative summary of all failures, errors,
warnings, and skips that occurred inside the test.
* `test_that()` now errors if `desc` is not a string (#1161).
* `test_file()` now runs helper, setup, and teardown code, and has the
same arguments as `test_dir()` (#968). Long deprecated `encoding` argument
has been removed.
* `test_dir()` now defaults `stop_on_failure` to `TRUE` for consistency with
other `test_` functions. The `wrap` argument has been deprecated; it's not
clear that it should ever have been exposed.
* New `test_local()` tests a local source package directory. It's equivalent
to `devtools::test()` but doesn't require devtools and all its dependencies
to be installed (#1030).
## Minor improvements and bug fixes
* testthat no longer supports tests stored in `inst/tests`. This has been
deprecated since testthat 0.11.0 (released in 2015). `test_package()`
(previously used for running tests in R CMD check) will fail silently
if no tests are found to avoid breaking old packages on CRAN (#1149).
* `capture_output()` and `verify_output()` use a new `testthat_print()`
generic. This allows you to control the printed representation of your
object specifically for tests (i.e. if your usual print method shows
data that varies in a way that you don't care about for tests) (#1056).
* `context_start_file()` is now exported for external reporters (#983, #1082).
It now only strips first instance of prefix/suffix (#1041, @stufield).
* `expect_error()` no longer encourages you to use `class`. This advice
one type of fragility at the expense of creating a different type (#1013).
* `expect_known_failure()` has been removed. As far as I can tell it was
only ever used by testthat, and is rather fragile.
* `expect_true()`, `expect_false()`, and `expect_null()` now use waldo to
produce more informative failures.
* `verify_output()` no longer always fails if output contains a carriage
return character ("\r") (#1048). It uses the `pdf()` device instead of
`png()` soit work on systems without X11 (#1011). And it uses
`waldo::compare()` to give more informative failures.
Added devel/R-waldo version 0.2.3
Added devel/R-diffobj version 0.3.2
Added devel/R-brio version 1.1.0
Added www/R-diffviewer version 0.1.0
Updated sysutils/R-ps to 1.5.0
Functions to handle basic input output, these functions always read
and write UTF-8 (8-bit Unicode Transformation Format) files and
provide more explicit control over line endings.
Compare complex R objects and reveal the key differences. Designed
particularly for use in testing packages where being able to quickly
isolate key differences makes understanding test failures much easier.
# rprojroot 2.0.2 (2020-11-15)
## Features
- In `find_root_file()`, if the first path component is already an
absolute path, the path is returned unchanged without referring to
the root. This allows using both root-relative and absolute paths in
`here::here()`. Mixing root-relative and absolute paths in the same
call returns an error (#59).
- `find_root_file()` propagates `NA` values in path components. Using
tidyverse recycling rules for path components of length different
from one (#66).
- `has_file()` and `has_file_pattern()` gain `fixed` argument (#75).
- New `is_drake_project` criterion (#34).
- Add `subdir` argument to `make_fix_file()` (#33, @BarkleyBG).
- Update documentation for version control criteria (#35, @uribo).
## Breaking changes
- `Has_file()` and `has_dir()` now throw an error if the `filepath`
argument is an absolute path (#74).
- `has_basename()` replaces `has_dirname()` to avoid confusion (#63).
- `as_root_criterion()` and `is_root_criterion()` replace `as.` and
`is.`, respectively. The latter are soft-deprecated.
- `thisfile()` and related functions are soft-deprecated, now
available in the whereami package (#43).
## Bug fixes
- The `is_dirname()` criterion no longer considers sibling directories (#44).
## Internal
- Use testthat 3e (#70).
- The backports package is no longer imported (#68).
- Re-license as MIT (#50).
- Move checks to GitHub Actions (#52).
- Availability of suggested packages knitr and rmarkdown, and pandoc,
is now checked before running the corresponding tests.
# magrittr 2.0.1
* Fixed issue caused by objects with certain names being present in
the calling environment (#233).
* Fixed regression in `freduce()` with long lists (kcf-jackson/sketch#5).
# magrittr 2.0.0
## Fast and lean implementation of the pipe
The pipe has been rewritten in C with the following goals in mind:
- Minimal performance cost.
- Minimal impact on backtraces.
- No impact on reference counts.
As part of this rewrite we have changed the behaviour of the pipe to
make it closer to the implementation that will likely be included in a
future version of R. The pipe now evaluates piped expressions lazily (#120).
The main consequence of this change is that warnings and errors can
now be handled by trailing pipe calls:
```r
stop("foo") %>% try()
warning("bar") %>% suppressWarnings()
```
## Breaking changes
The pipe rewrite should generally not affect your code. We have
checked magrittr on 2800 CRAN packages and found only a dozen of
failures. The development version of magrittr has been advertised on
social media for a 3 months trial period, and no major issues were
reported. However, there are some corner cases that might require
updating your code. Below is a report of the backward
incompatibilities we found in real code to help you transition, should
you find an issue in your code.
### Behaviour of `return()` in a pipeline
In previous versions of magrittr, the behaviour of `return()` within
pipe expressions was undefined. Should it return from the current pipe
expression, from the whole pipeline, or from the enclosing function?
The behaviour that makes the most sense is to return from the
enclosing function. However, we can't make this work easily with the
new implementation, and so calling `return()` is now an error.
```r
my_function <- function(x) {
x %>% {
if (.) return("true")
"false"
}
}
my_function(TRUE)
#> Error: no function to return from, jumping to top level
```
In magrittr 1.5, `return()` used to return from the current pipe
expression. You can rewrite this to the equivalent:
```r
my_function <- function(x) {
x %>% {
if (.) {
"true"
} else {
"false"
}
}
}
my_function(TRUE)
#> [1] "true"
```
For backward-compatibility we have special-cased trailing `return()`
calls as this is a common occurrence in packages:
```r
1 %>% identity() %>% return()
```
Note however that this only returns from the pipeline, not the
enclosing function (which is the historical behaviour):
```r
my_function <- function() {
"value" %>% identity() %>% return()
"wrong value"
}
my_function()
#> [1] "wrong value"
```
It is generally best to avoid using `return()` in a pipeline, even if
trailing.
### Failures caused by laziness
With the new lazy model for the evaluation of pipe expressions,
earlier parts of a pipeline are not yet evaluated when the last pipe
expression is called. They only get evaluated when the last function
actually uses the piped arguments:
```r
ignore <- function(x) "return value"
stop("never called") %>% ignore()
#> [1] "return value"
```
This should generally not cause problems. However we found some
functions with special behaviour, written under the assumption that
earlier parts of the pipeline were already evaluated and had already
produced side effects. This is generally incorrect behaviour because
that means that these functions do not work properly when called
with the nested form, e.g. `f(g(1))` instead of `1 %>% g() %>% f()`.
The solution to fix this is to call `force()` on the inputs to force
evaluation, and only then check for side effects:
```r
my_function <- function(data) {
force(data)
peek_side_effect()
}
```
Another issue caused by laziness is that if any function in a pipeline
returns invisibly, than the whole pipeline returns invisibly as well.
```r
1 %>% identity() %>% invisible()
1 %>% invisible() %>% identity()
1 %>% identity() %>% invisible() %>% identity()
```
This is consistent with the equivalent nested code. This behaviour can
be worked around in two ways. You can force visibility by wrapping the
pipeline in parentheses:
```r
my_function <- function(x) {
(x %>% invisible() %>% identity())
}
```
Or by assigning the result to a variable and return it:
```r
my_function <- function(x) {
out <- x %>% invisible() %>% identity()
out
}
```
### Incorrect call stack introspection
The magrittr expressions are no longer evaluated in frames that can be
inspected by `sys.frames()` or `sys.parent()`. Using these functions
for implementing actual functionality (as opposed as debugging tools)
is likely to produce bugs. Instead, you should generally use
`parent.frame()` which works even when R code is called from
non-inspectable frames. This happens with e.g. `do.call()` and the new
C implementation of magrittr.
### Incorrect assumptions about magrittr internals
Some packages were depending on how magrittr was internally
structured. Robust code should only use the documented and exported
API of other packages.
## Bug fixes
* Can now use the placeholder `.` with the splicing operator `!!!`
from rlang (#191).
* Piped arguments are now persistent. They can be evaluated after the
pipeline has returned, which fixes subtle issues with function
factories (#159, #195).
## clipr 0.7.1
- Call xsel with the `--output` flag, which prevents RStudio from
hanging when calling clipr functions on a system running certain
Linux window managers. Thank you to @cgillespie and @kevinushey for
identifying the bug and the solution, and to @hannahcgunderman for
help in testing.
# callr 3.5.1
* `callr::r_session` now handles large messages from the subprocess
well (#168).
# callr 3.5.0
* callr can now pass the environment of the function to the subprocess,
optionally. This makes it easier to call an internal function of a
package in a subprocess. See the `package` argument of `r()`, `r_bg()`,
`r_session$run()`, etc. (#147).
golangci-lint is a fast runner for Go linters. It runs linters in parallel,
uses caching, supports yaml config, has integrations with all major IDE and has
dozens of linters included.
This was added in 2014 in r1.57 along with patches to add OpenBSD/amd64
5.4 support, which have long been removed.
In OpenBSD 6.2, the default compiler on amd64 was switched from GCC to
Clang, which does not support this option and emits unknown warning
option '-Wno-bounded' warnings.
5.4.0 is generally focused on code quality improvements and tornado asyncio compatibility.
- Add github actions, bail on asyncio patch for tornado 6.1.
- Start testing on Python 3.9.
- Fix stack levels for ipykernel's deprecation warnings and stop using some deprecated APIs.
- Add env parameter to kernel installation
- Fix stop_on_error_timeout blocking other messages in queue.
- Remove most of the python 2 compat code.
- Remove u-prefix from strings
Changes include:
* Add let* and and* in Lwt.Syntax and Lwt_result.Syntax.
* Also add let+ and and+.
* Add Lwt_result.both.
* Always use libev if detected.
New in 2020.11
6model:
+ [af9ebffb,ffc8a269,75177470,38a2f815,2e8b5657] Fix interning of parametrics
+ [3c5deb2f] Implement serialize/deserialize of CStr REPR
+ [a37cd763,cbb92b03,dfbdcc9d] Eliminate pointer mismatch warnings on big endian systems
+ [2a98b8f3] MVM_nativeref_{read,write}_lex_i should handle uint8, uint16, uint32
+ [608b90eb] No need to MVMROOT `root` twice in `get_attribute`
Core:
+ [88722e8e] Fix zeroing of reallocated memory in MVM_recalloc
+ [1eda12a0] Use `foo(void)` instead of just `foo()` for functions that take no arguments
Platform:
+ [18e6f94e] Import pthread on Windows to get a type
Strings:
+ [cefec1fb] Regenerate Unicode database files for v13.0, v13.1
+ [2cac07c9] Regenerate unicode_db to fix minor comment difference
+ [4ced726f] Use MVM_{malloc,realloc,calloc,free} consistency
+ [55964708] `swap_bytes` in utf16.c needs to also swap bytes on big endian platforms
Tooling/Build:
+ [f212c081] Update generation scripts for Unicode 13.0, 13.1
+ [004e4bc7] The probe for `pthread_setname_np` needs prototypes from <string.h>
+ [6a2284e6,aa83051a] Report the lines that caused coverage
+ [7167b3d1,56fca429] Remove unused, unneeded and misspelled block filter
libyang is a YANG data modelling language parser and toolkit written (and
providing API) in C. The library is used e.g. in
* Parsing (and validating) schemas in YANG format.
* Parsing (and validating) schemas in YIN format.
* Parsing, validating and printing instance data in XML format.
* Parsing, validating and printing instance data in JSON format
3.1.0 (2020-10-02)
------------------
*New:*
- Allow all types of declarations in :class:`factory.Faker` calls - enables references to other faker-defined attributes.
3.0.1 (2020-08-13)
------------------
*Bugfix:*
- :issue:`769`: Fix ``import factory; factory.django.DjangoModelFactory`` and similar calls.
3.0.0 (2020-08-12)
------------------
Breaking changes
""""""""""""""""
The following aliases were removed:
+------------------------------------------------+---------------------------------------------------+
| Broken alias | New import |
+================================================+===================================================+
| ``from factory import DjangoModelFactory`` | ``from factory.django import DjangoModelFactory`` |
+------------------------------------------------+---------------------------------------------------+
| ``from factory import MogoFactory`` | ``from factory.mogo import MogoFactory`` |
+------------------------------------------------+---------------------------------------------------+
| ``from factory.fuzzy import get_random_state`` | ``from factory.random import get_random_state`` |
+------------------------------------------------+---------------------------------------------------+
| ``from factory.fuzzy import set_random_state`` | ``from factory.random import set_random_state`` |
+------------------------------------------------+---------------------------------------------------+
| ``from factory.fuzzy import reseed_random`` | ``from factory.random import reseed_random`` |
+------------------------------------------------+---------------------------------------------------+
*Removed:*
- Drop support for Python 2 and 3.4. These versions `are not maintained anymore <https://devguide.python.org/devcycle/#end-of-life-branches>`__.
- Drop support for Django 2.0 and 2.1. These versions `are not maintained anymore <https://www.djangoproject.com/download/#supported-versions>`__.
- Remove deprecated ``force_flush`` from ``SQLAlchemyModelFactory`` options. Use
``sqlalchemy_session_persistence = "flush"`` instead.
- Drop deprecated ``attributes()`` from :class:`~factory.Factory` subclasses; use
``factory.make_factory(dict, FactoryClass._meta.pre_declarations)`` instead.
- Drop deprecated ``declarations()`` from :class:`~factory.Factory` subclasses; use ``FactoryClass._meta.pre_declarations`` instead.
- Drop ``factory.compat`` module.
*New:*
- Add support for Python 3.8
- Add support for Django 2.2 and 3.0
- Report misconfiguration when a :py:class:`~factory.Factory` is used as the :py:attr:`~factory.Factory.model` for another :py:class:`~factory.Factory`.
- Allow configuring the color palette of :py:class:`~factory.django.ImageField`.
- :py:meth:`get_random_state()` now represents the state of Faker and ``factory_boy`` fuzzy attributes.
- Add SQLAlchemy ``get_or_create`` support
*Improvements:*
- :issue:`561`: Display a developer-friendly error message when providing a model instead of a factory in a :class:`~factory.declarations.SubFactory` class.
*Bugfix:*
- Fix issue with SubFactory not preserving signal muting behaviour of the used factory, thanks `Patrick Stein <https://github.com/PFStein>`_.
- Fix issue with overriding params in a Trait, thanks `Grégoire Rocher <https://github.com/cecedille1>`_.
- :issue:`598`: Limit ``get_or_create`` behavior to fields specified in ``django_get_or_create``.
- :issue:`606`: Re-raise :class:`~django.db.IntegrityError` when ``django_get_or_create`` with multiple fields fails to lookup model using user provided keyword arguments.
- :issue:`630`: TypeError masked by __repr__ AttributeError when initializing ``Maybe`` with inconsistent phases.
5.0.1
* ``th_TH`` ``strftime``: normalize output for unsupported directive on ``musl``-based Linux.
5.0.0
* Drop support for Python 3.5.
* Add support fro Python 3.9.
4.18.0
* Add ``date_time`` and ``bank`` providers for ``th_TH``.
4.17.1
* Correct spelling errors in city names for ``de_DE``.
4.17.0
* Add name pairs to get matched representation in ``ja_JP`` person provider.
4.16.0
* Add SSN, company name, address, and license plate providers for ``th_TH``.
4.15.0
* Add postcode format, country names, person prefix weights, and update phone number format for ``th_TH``.
4.14.2
* Fix generation of names ending with spaces.
4.14.1
* Add relative frequencies for japanese last names.
4.14.0
* Add Swiss bank provider locales.
4.13.0
* Split first names into male and female on ``pt_PT`` provider.
4.12.0
* Geo provider added for ``tr_TR`` locale.
4.11.0
* Add ``sk_SK`` Job provider.
4.10.0
* Add ``date_time`` provider for ``pt_PT``.
4.9.0
* Add ``.unique()`` for unique values.
4.8.0
* Add automotive provider for ``tr_TR``.
4.7.0
* Add province list and add 2 new district to ``ne_NP``.
4.6.0
* Add Currency provider for ``sv_SE``.
4.5.0
* Add ``pt_PT`` credit card provider.
4.4.0
* Added Company Provider for ``tr_TR`` locale.
4.3.0
* Add job providers for ``tr_TR``.
4.2.0
* Implement color provider for ``sk_SK`` locale.
4.1.8
* Fix ``hu_HU`` color provider inheritance.
4.1.7
* Bigger zipcode ranges for VA, TX and MD in ``en_US``.
4.1.6
* Add new style ``pt_PT`` automotive plates.
4.1.5
* Remove duplicate jobs from the ``pt_PT`` provider.
4.1.4
* Use "Belarus" instead of "Vitryssland" for ``sv_SE``.
* Added bank provider for ``tr_TR`` locale.
* Improve VAT generation for IT provider.
* Use non-zero number for first digit of Swedish postal codes.
Changes from the previous version are too many to mention (see the
CHANGELOG.md file in the distribution for full details). From a practical
point of view the package bootstrap procedure has changed now so that
dune-configurator had to be split off as a separate package; there are
also compatibility changes so the package works with newer versions of
OCaml.
5.42.2
This patch teaches hypothesis.extra.django.from_field() to infer more efficient strategies by inspecting (not just filtering by) field validators for numeric and string fields.
5.42.1
This patch refactors hypothesis.settings to use type-annotated keyword arguments instead of **kwargs, which makes tab-completion much more useful - as well as type-checkers like mypy.
5.42.0
This patch teaches the magic() ghostwriter to recognise “en/de” function roundtrips other than the common encode/decode pattern, such as encrypt/decrypt or, encipher/decipher.
5.41.5
This patch adds a performance optimisation to avoid saving redundant seeds when using the .fuzz_one_input hook.
Those comments were written before converters/unoconv and textproc/
py-Levenshtein were imported. Point to what's in pkgsrc, rather than to
upstream URLs (in the case of py-Levenshtein, an older, unmaintained
version). (I'm not going to change anything to do with Tryton right
now, given the recent related build breakage.)
-Removed version checks for some LXQt dependencies.
-Added a Fontconfig CMake find module.
-Suppressed warning about find_package_handle_standard_args package name mismatch.
Abseil LTS 20200923, Patch 2
What's New:
absl::StatusOr<T> has been released. See our blog
post for more information.
Abseil Flags reflection interfaces have been released.
Abseil Flags memory usage has been significantly optimized.
Abseil now supports a "hardened" build mode. This build mode enables
runtime checks that guard against programming errors that may lead
to security vulnerabilities.
Notable Fixes:
Sanitizer dynamic annotations like AnnotateRWLockCreate that are
also defined by the compiler sanitizer implementation are no longer
also defined by Abseil.
Sanitizer macros are now prefixed with ABSL_ to avoid naming collisions.
Sanitizer usage is now automatically detected and no longer requires
macros like ADDRESS_SANITIZER to be defined on the command line.
Breaking Changes:
Abseil no longer contains a dynamic_annotations library. Users
using a supported build system (Bazel or CMake) are unaffected by
this, but users manually specifying link libraries may get an error
about a missing linker input.
reftools is a collection of refactoring tools for Go.
fixplurals: remove redundant parameter and result types from function signatures
fillstruct: fills a struct literal with default values
fillswitch: fills a (type) switch statement with case statements
Looks OK to kamil@
Changes in 2.35:
* Changed readelf's display of symbol names when wide mode is not enabled.
If the name is too long it will be truncated and the last five characters
replaced with "[...]". The old behaviour of displaying 5 more characters but
not indicating that truncation has happened can be restored by the use of the
-T or --silent-truncation options.
* X86 NaCl target support is removed.
* The readelf tool now has a -L or --lint or --enable-checks option which turns
on warning messages about possible problems with the file(s) being examined.
These checks include things like zero-sized sections, which are allowed by
the ELF standard but which nevertheless might be of concern if the user
was expecting them to actually contain something.
asmfmt will format your assembler code in a similar way that gofmt formats your
Go code. The main goals where:
- It should provide predictable formatting.
- Be as un-intrusive as possible.
- Tab setting should not affect alignment.
1.6.1
- Adjust test classifiers to match supported Python versions.
1.6.0
- Add support for Python 3.8.
- Drop support for Python 3.4.
- Update tests to match setuptools' change, no longer reporting metadata
version for installed packages w/o explicit metadata.
0.36.1
- Fixed ``AssertionError`` when ``MACOSX_DEPLOYMENT_TARGET`` was set to ``11``
- Fixed regression introduced in 0.36.0 on Python 2.7 when a custom generator
name was passed as unicode (Scikit-build)
(``TypeError: 'unicode' does not have the buffer interface``)
0.36.0
- Added official Python 3.9 support
- Updated vendored ``packaging`` library to v20.7
- Switched to always using LF as line separator when generating ``WHEEL`` files
(on Windows, CRLF was being used instead)
- The ABI tag is taken from the sysconfig SOABI value. On PyPy the SOABI value
is ``pypy37-pp73`` which is not compliant with PEP 3149, as it should have
both the API tag and the platform tag. This change future-proofs any change
in PyPy's SOABI tag to make sure only the ABI tag is used by wheel.
0.5.5
This is a patch release to fix two bugs in gopls/v0.5.4.
Fixes
Excessive reloading of packages outside of GOPATH or a module
File corruption with CRLF line endings and //-style comments
golang/go#42646 was supposed to have been fixed in gopls/v0.5.4,
but it was not. golang/go#42923 was reported and fixed.
0.5.4
Features
Opening a project that contains a module in a subdirectory
Previously, gopls required that you open your editor exactly at or
below the module root (the directory containing the go.mod). Now,
you can open a directory that contains exactly one module in a
subdirectory, and gopls will work as expected. For details on
multi-module workspaces, see below.
Removal of the granular go.mod upgrade codelenses
Previously, we offered a code lens to suggest upgrades for each
require in a go.mod file. In anticipation of changes that limit
the amount that gopls accesses the network, we have decided to
remove and reevaluate this feature. Users had mentioned that the
code lenses cluttered their go.mod files, especially if they didn't
actually want to upgrade. golang/go#38339 tracks the work to revamp
this feature. An "Upgrade all dependencies" code lens should still
appear at the top of your go.mod file.
Improved error message reports
Previously, critical error messages were reported as message pop-up
that would re-trigger as you type. Many users would find this
annoying. We have changed the approach to show error messages as
progress reports, which should be less intrusive and appear more
like status bars.
Improved memory usage for workspaces with multiple folders
We are now using a coarser cache key for package type information.
If you use the gopls daemon, this may reduce your total memory
usage.
Experimental
Multi-module workspace support
The proposal described in golang/go#32394 is still in development
and off by default. See our progress by tracking the multi-module
workspace milestone and project.
Enable multi-module workspace support by adding the following to
your settings:
"gopls": { "experimentalWorkspaceModule": true, }
With this setting, you will be able to open a directory that contains
multiple modules or a directory that contains nested modules.
Give this a try if you're interested in this new feature, but please
note that it is still very experimental. Please file issues if you
encounter bugs.
Fixes
File corruption with CRLF line endings and /**/-style comments
Previously, when you organized the imports in a file with CRLF line
endings and multi-line comments, the formatter might output incorrect
content for the file, rendering it invalid Go code. This issue has
popped up a number of times, but we believe it has finally been
fixed for good. If you are using Windows with CRLF line ending,
please report any regressions. For full details, see golang/go#42646.
Version 10.36 04-December-2020
------------------------------
Again, mainly bug fixes and tidies. The only enhancements are the addition of
GNU grep's -m (aka --max-count) option to pcre2grep, and also unifying the
handling of substitution strings for both -O and callouts in pcre2grep, with
the addition of $x{...} and $o{...} to allow for characters whose code points
are greater than 255 in Unicode mode.
NOTE: there is an outstanding issue with JIT support for MacOS on arm64
hardware. For details, please see Bugzilla issue #2618.
This implements a case preserving but case insensitive hash table.
This means that
$cphash{KEY} $cphash{key}
$cphash{Key} $cphash{keY}
all refer to the same entry. Also, the hash remembers which form of
the key was last used to store the entry. The `keys' and `each'
functions will return the key that was used to set the value.
Upstream release Notes:
2.0.8
- Fixed packages with aliases not matching conflicts which match the alias
- Fixed invalid reports of uncommitted changes when using non-default remotes
in vendor dir
- Fixed curl error handling edge cases
- Fixed cached git repositories becoming stale by having a git gc applied to
them periodically
- Fixed issue initializing plugins when using dev packages
- Fixed update --lock / mirrors failing to update in some edge cases
- Fixed partial update with --with-dependencies failing in some edge cases
with some nonsensical error
2.0.7
- Fixed detection of TTY mode, made input non-interactive automatically if
STDIN is not a TTY
- Fixed root aliases not being present in lock file if not required by
anything else
- Fixed remove command requiring a lock file to be present
- Fixed Composer\InstalledVersions to always contain up to date data during
installation
- Fixed status command breaking on slow networks
- Fixed order of POST_PACKAGE_* events to occur together once all
installations of a package batch are done
Python library for Intel HEX files manipulations
The Intel HEX file format is widely used in microprocessors and
microcontrollers area (embedded systems etc) as the de facto standard
for representation of code to be programmed into microelectronic
devices.
This work implements an intelhex Python library to read, write, create
from scratch and manipulate data from Intel HEX file format.
The distribution package also includes several convenience Python
scripts, including "classic" hex2bin and bin2hex converters and more,
those based on the library itself. Check the docs to know more.
Python and PyPI packaging tool. Core library and bootstrapping goo
imported as devel/py-flit_core at the same time. From the README:
Flit is a simple way to put Python packages and modules on PyPI.
It tries to require less thought about packaging and help you avoid
common mistakes.
20.3.1 (2020-12-03)
===================
Deprecations and Removals
-------------------------
- The --build-dir option has been restored as a no-op, to soften the transition
for tools that still used it.
20.3 (2020-11-30)
=================
Deprecations and Removals
-------------------------
- Remove --unstable-feature flag as it has been deprecated.
Features
--------
- Add support for :pep:`600`: Future 'manylinux' Platform Tags for Portable Linux Built Distributions.
- The new resolver now resolves packages in a deterministic order.
- Add support for MacOS Big Sur compatibility tags.
Bug Fixes
---------
- New Resolver: Rework backtracking and state management, to avoid getting stuck in an infinite loop.
- New resolver: Check version equality with ``packaging.version`` to avoid edge
cases if a wheel used different version normalization logic in its filename
and metadata.
- New resolver: Show each requirement in the conflict error message only once to reduce cluttering.
- Fix a regression that made ``pip wheel`` generate zip files of editable
requirements in the wheel directory.
- Fix ResourceWarning in VCS subprocesses
- Redact auth from URL in help message.
- New Resolver: editable installations are done, regardless of whether
the already-installed distribution is editable.
Vendored Libraries
------------------
- Upgrade certifi to 2020.11.8
- Upgrade colorama to 0.4.4
- Upgrade packaging to 20.7
- Upgrade pep517 to 0.9.1
- Upgrade requests to 2.25.0
- Upgrade resolvelib to 0.5.3
- Upgrade toml to 0.10.2
- Upgrade urllib3 to 1.26.2
Improved Documentation
----------------------
- Add a section to the User Guide to cover backtracking during dependency resolution.
- Reorder and revise installation instructions to make them easier to follow.
Apologies for breaking this package so hard with the previous update.
- add missing buildlinks to go-mod, go-crypto and goldmark
- remove bin/server (which is the "getgo" App Engine app, not useful locally)
- update PLIST
Ironically, this is not packaged as a Go module, because it is a dependency
of go-tools.
This repository holds packages for writing tools
that work directly with Go module mechanics.
That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that
need to do things like load packages in module mode.
That use case, where modules are incidental rather than the focus,
should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by
invoking the go command, which remains the single point of
truth for package loading algorithms.
1.4.1:
Due to numerous problems removed nose dependency completely in favor of pytest.
Fixed compatibility with Python 2.7
1.4.0:
Added support for index-only test names
1.3.1:
Switched from Travis to Github Actions for builds and release upload.
1.3.0:
Added the ability to specify the YAML loader in the file_data decorator
Dropped Python 3.4 support
1.2.2:
Merge pull request 76 from Harmon758/url-updates
Merge pull request 74 from carlwgeorge/stdlib-mock
- BREAKING: `MOB_WIP_BRANCH_QUALIFIER_SEPARATOR` now defaults to '-'.
- BREAKING: `MOB_NEXT_STAY` now defaults to 'true'.
- Proposed cli commands like `mob start --include-uncommitted-changes`
are now shown on a separate line to allow double clicking to copy in
the terminal.
Pkgsrc changes:
* set version# only once
Upstream changes:
v0.0.4 2020-03-09 Paris (France)
* Fix 32bit backend where we miss to fully apply an invalid_arg
* Fix 64bit backend where Native.unsigned_compare and
Nativeint.unsigned_div exists (OCaml 4.08.0)
v0.0.3 2010-09-12 Paris (France)
* Avoid partial application of function (#2, @dinosaure)
* Add [@immediate] tag (#4, @dinosaure)
* Fix select.ml in 32bit (#5, @IndiscriminateCoding)
* Fix typo (#6, @hannesm)
* Add fuzzer (#8, @dinosaure)
* Fix lsr and asr in 64bit (#8, @cfcs, @dinosaure)
* Optimization on of_int function (64bit) (#8, @cfcs, @dinosaure)
* Optimization on abs function (64bit) (#8, @cfcs, @dinosaure)
* Fix 32bit architecture, keep bit-sign in the same place (#8,
@dinosaure, review @cfcs)
OK'ed by jaapb@
SQLite Release 3.34.0
Added the sqlite3_txn_state() interface for reporting on the current transaction state of the database connection.
Enhance recursive common table expressions to support two or more recursive terms as is done by SQL Server, since this helps make queries against graphs easier to write and faster to execute.
Improved error messages on CHECK constraint failures.
CLI enhancements:
The .read dot-command now accepts a pipeline in addition to a filename.
Added options --data-only and --nosys to the .dump dot-command.
Added the --nosys option to the .schema dot-command.
Table name quoting works correctly for the .import dot-command.
The generate_series(START,END,STEP) table-valued function extension is now built into the CLI.
The .databases dot-command now show the status of each database file as determined by sqlite3_db_readonly() and sqlite3_txn_state().
Added the --tabs command-line option that sets .mode tabs.
The --init option reports an error if the file named as its argument cannot be opened. The --init option also now honors the --bail option.
Query planner improvements:
Improved estimates for the cost of running a DISTINCT operator.
When doing an UPDATE or DELETE using a multi-column index where only a few of the earlier columns of the index are useful for the index lookup, postpone doing the main table seek until after all WHERE clause constraints have been evaluated, in case those constraints can be covered by unused later terms of the index, thus avoiding unnecessary main table seeks.
The new OP_SeekScan opcode is used to improve performance of multi-column index look-ups when later columns are constrained by an IN operator.
The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if one or more attached database files are read-only.
Enhanced FTS5 to support trigram indexes.
Improved performance of WAL mode locking primitives in cases where there are hundreds of connections all accessing the same database file at once.
Enhanced the carray() table-valued function to include a single-argument form that is bound using the auxiliary sqlite3_carray_bind() interface.
The substr() SQL function can now also be called "substring()" for compatibility with SQL Server.
The syntax diagrams are now implemented as Pikchr scripts and rendered as SVG for improved legibility and ease of maintenance.
5.41.4 - 2020-11-28
This patch fixes issue #2657, where passing unicode patterns compiled
with re.IGNORECASE to from_regex() could trigger an internal error
when casefolding a character creates a longer string (e.g.
"\u0130".lower() -> "i\u0370").
There have been two small changes in this release: The browse tool
is now enabled when building with CMake (so it's part of the official
binaries again) and it should now work in all circumstances to run
the restat tool by the generator on Windows. See
https://github.com/ninja-build/ninja/issues/1724#issuecomment-677730694
for why the fix in 1.10.1 wasn't enough.
This is so that we can add that directory to the default
link search path of rust without also automatically picking up
other installed libraries.
This is for the benefit of our powerpc ports, where recent rust
has been changed to insist on using -latomic due to the lack of
native 64-bit atomic operations.
A bunch of packages had an extra "p" specification character passed to
the pax -p option. One is enough. Committed to reduce the human parsing
costs, should someone else need to examine this. (In my case because it
seems recent Linux distros have changed such that some -p arguments can
now cause an error to occur, where previously they were accepted.)
This patch adds a final fallback clause to our plugin logic to fail
with a warning rather than error on Python < 3.8 when neither the
importlib_metadata (preferred) or setuptools (fallback) packages are
available.
Add the following new features: arc4random, bswap, dprintf, efun,
errc, fparseln, fts, posix_getopt, raise_default_signals,
reallocarray, strsep and vis.
See mk-configure.7 for details.
Fixes:
* mkc_check_decl: fix "prototype" mode. Extraction of function name
was incorrect. Add one more regression test for this case in
tests/os_NetBSD.
* Avoid multiple repetition of MKC_COMMON_DEFINES in CPPFLAGS
* Fix target "depend" that failed if SRCS contains full path to
source code.
Move -Wreturn-type from CFLAGS.warns.{clang,gcc}.2 to
CFLAGS.warns.{clang,gcc}.1 and make it an error for C++
CC_TYPE and CXX_TYPE are correctly set if MKC_CHECK_CUSTOM is set.
Use .error bmake command for checking MKC_REQD. Also, move
appropriate check to mkc_imp.preinit.mk, so it is checked in the
very beginning. Documentation and error message are slightly
updated.
Rename variable DISTCLEANFILES to CLEANDIRFILES, DISTCLEANFILES is
considered deprecated.
Rename variable DISTCLEANDIRS to CLEANDIRDIRS, DISTCLEANDIRS is
considered deprecated.
Add support for latest Intel C/C++ compiler. We have to always add
-we10006 option to it in order it fail when invalid option is used.
Adapt some features for using functions implementation from
libnbcompat and libbsd libraries.
Use .depend_${.CURDIR:T} instead .depend to support MAKEOBJDIR.
New tests and examples.
Version 2.9.0
Upcoming version support changes
* This version, Babel 2.9, is the last version of Babel to support Python 2.7, Python 3.4, and Python 3.5.
Improvements
* CLDR: Use CLDR 37
* Dates: Handle ZoneInfo objects in get_timezone_location, get_timezone_name
* Numbers: Add group_separator feature in number formatting
Bugfixes
* Dates: Correct default Format().timedelta format to 'long' to mute deprecation warnings
* Import: Simplify iteration code in "import_cldr.py"
* Import: Stop using deprecated ElementTree methods "getchildren()" and "getiterator()"
* Messages: Fix unicode printing error on Python 2 without TTY.
* Messages: Introduce invariant that _invalid_pofile() takes unicode line.
* Tests: fix tests when using Python 3.9
* Tests: Remove deprecated 'sudo: false' from Travis configuration
* Tests: Support Py.test 6.x
* Utilities: LazyProxy: Handle AttributeError in specified func
* Utilities: Replace usage of parser.suite with ast.parse
Documentation
* Update parse_number comments
* Add __iter__ to Catalog documentation
2020-09-10 Thomas E. Dickey <dickey@invisible-island.net>
* LICENSE: RCS_BASE
* reader.c, output.c: cppcheck -- reduce scope
* defs.h: update to 2.0
* test/btyacc/[...]
update to version 2.0
* reader.c:
improve loop which skips backward through a (possibly nested) sequence of
square-brackets.
* reader.c: simplify a check to quiet a bogus cppcheck-warning
* yacc.1: bump date
* reader.c: add a note about a bogus cppcheck warning
* configure: regen
* configure.in:
always check for gcc attributes, to work around defect in clang's imitation
of this feature
* reader.c: cppcheck -- scope reduction
cppcheck -- eliminate bogus returns after no-return functions
* verbose.c, output.c, mkpar.c, main.c, warshall.c, lr0.c, lalr.c, graph.c, closure.c:
cppcheck -- scope reduction
* package/debian/compat: quiet compatibility-warning
* yacc.1: use "ASCII" for dashes which are part of proper names
* configure: regen
* configure.in: switch to --enable-warnings, for consistency
* aclocal.m4:
resync with my-autoconf, for compiler-warning fixes with macOS
* VERSION, package/byacc.spec, package/debian/changelog, package/mingw-byacc.spec, package/pkgsrc/Makefile:
bump
2020-06-28 Thomas E. Dickey <dickey@invisible-island.net>
* config.sub: 2020/06/28
2020-06-14 Thomas E. Dickey <dickey@invisible-island.net>
* config.guess: 2020/04/26
Changelog from AN-2020-11-04:
- Makefile system: include/schily/nlsdefs.h no longer by default defines
the macro __() because this is in conflict with definitions that are
present in the system include files from newer HP-UX versions.
Thanks to Rudi Blom for reporting.
- smake: The new POSIX ::= assign macro feature has been implemented.
Today, this is an alias for :=, but we may make := compatible to the
SunPro Make feature := (conditional macro assignment) compatible:
target := MACRO = value
or
target := MACRO += value
- smake: The new POSIX ?= conditional macro assignment operator has
been added.
Note that like with +=, there is a need to have a space character
before ?= in order to be recognised. This is because smake and
SunPro Make support to have the characters '+' and '?' as part of
a macro name.
Note that some other make implementations that do not support
'+' and '?' as part of a macro name may be happy with something like
"MACRO+= value" or "MACRO?= value" but this is definitely not
portable.
Changelog from AN-2020-11-25:
- Makefile System: Added support for MacOS on arm64
Thanks to a hint from Ryan Schmidt from macports
Note that due to outstanding replies to recent changes in configure,
it could up to now not be verified that all configure tests now work in
a way that results in correct overall results. See below for an in
depth report on the changes.
- Makefile System: autoconf (config.guess & config.sub) now supports
the new arm64 Apple systems.
Thanks to Ryan Schmidt from macports for provinding the needed uname(1)
output.
- Makefile System: Added a new shell script "autoconf/uname" that helps
to create shell scrips that allow to emulate an alien host system in
order to test the correct behavior of configure.guess and configure.sub
on the main development platform.
This helps to adapt configure.guess and configure.sub to new platforms
in the future.
- Makefile System: The new clang compiler as published with the upcomming
ARM macs has been preconfigured with
-Werror -Wimplicit-function-declaration
as the default behavior and thus is in conflict with the existing base
assumption of the autoconf system that minimalistic C-code used for
compile/link allows to check for the existence of a specific function
in libc without a need to know which system #include file is used to
define a prototype for that function.
This clang version, as a result of this default, behaves like a C++
compiler and aborts if a function is used with no previous function
prototype. This caused most of the existing autoconf test to fail with
error messages about missing prototypes.
We implemented a workaround using these methods for the identified
problems:
- Most of the exit() calls in the various main() functions have
been replaced by return() to avoid a need to
#include <stdlib.h> in special since these test may be the
case for layered tests that #include files from the higher
level parts.
- Many autoconf tests programs now #include more system include
files, e.g. stdlib.h and unistd.h to avoid missing prototype
errors. This cannot reliably be done in tests that are used as
a base for higher level tests where the high level test
#includes own system include files, since older platforms do
not support to #include the same file twice.
So this is tricky...
- A test for a Linux glibc bug caused by incorect #pragma weak
usage inside glibc that prevents one or more functions from
ecvt()/fcvt()/gcvt() from being usable outside glibc now uses
hand-written prototypes for some of the libc interface
functions in order to avoid using the system includes. If we
did not do that, we could not use ecvt()/fcvt()/gcvt() on
MacOS anymore.
Thanks to Ryan Schmidt from macports for reporting and for the given
help that was needed for remote debugging.
Please send the needed feedback on whether the current state of the
configure script results on correct autoconf results on the M1 Macs.
CMake 3.19.1
ci: update to use CMake 3.19.0
gitlab-ci: update macOS jobs to use Xcode 12.0
Revert “specify language flag when source LANGUAGE property is set”
FindGTest: Revert “Allow either “Debug” or “Release” configurations.”
Makefiles: Fix CMAKE_EXPORT_COMPILE_COMMANDS crash with custom compile rule
Xcode: Fix custom command work-dir placeholders in “new build system”
Tests: Match RunCMake.CMP0111 stderr more strictly
cmTarget: Do not enforce CMP0111 on imported INTERFACE libraries
cmVisualStudio10TargetGenerator: Avoid GetFullPath on INTERFACE library
cmGlobalGenerator: FindMakeProgram() at a generator-specific time
cmFileTime: Fix overflow on time computation
Help: Fix ‘… versionadded’ directives for CTEST_CUSTOM_* variables
CUDA: Clang CUDA 11.1 support
CUDA: Error if can’t determine toolkit library root
CMake 3.19 Release Notes
************************
Changes made since CMake 3.18 include the following.
New Features
============
Presets
-------
* "cmake(1)" and "cmake-gui(1)" now recognize "CMakePresets.json" and
"CMakeUserPresets.json" files (see "cmake-presets(7)").
Generators
----------
* The "Xcode" generator now uses the Xcode “new build system” when
generating for Xcode 12.0 or higher. See the
"CMAKE_XCODE_BUILD_SYSTEM" variable. One may use "-T buildsystem=1"
to switch to the legacy build system.
* The "Xcode" generator gained support for linking libraries and
frameworks via the *Link Binaries With Libraries* build phase
instead of always by embedding linker flags directly. This behavior
is controlled by a new "XCODE_LINK_BUILD_PHASE_MODE" target
property, which is initialized by a new
"CMAKE_XCODE_LINK_BUILD_PHASE_MODE" variable.
* The Visual Studio Generators for VS 2015 and above gained support
for the Visual Studio Tools for Android. One may now set
"CMAKE_SYSTEM_NAME" to "Android" to generate ".vcxproj" files for
the Android tools.
Languages
---------
* CMake learned to support "ISPC" as a first-class language that can
be enabled via the "project()" and "enable_language()" commands.
"ISPC" is currently supported by the Makefile Generators and the
"Ninja" generator on Linux, macOS, and Windows using the Intel ISPC
compiler.
* "CUDA" language support for Clang now includes:
* separable compilation ("CUDA_SEPARABLE_COMPILATION"), and
* finding scattered toolkit installations when cross-compiling.
File-Based API
--------------
* The "cmake-file-api(7)" “codemodel” version 2 "version" field has
been updated to 2.2.
* The "cmake-file-api(7)" “codemodel” version 2 “target” object gained
a new "languageStandard" field in the "compileGroups" objects.
Command-Line
------------
* The "cmake(1)" command-line tool’s "--install" mode gained a "--
default-directory-permissions" option.
* "cmake(1)" gained a "-E create_hardlink" command-line tool that can
be used to create hardlinks between files.
GUI
---
* The "CMake GUI" now has an environment variable editor.
Commands
--------
* The "add_test()" command now (officially) supports whitespace and
other special characters in the name for the test it creates. See
policy "CMP0110".
* The "cmake_language()" command gained a "DEFER" mode to schedule
command calls to occur at the end of processing a directory.
* The "configure_file()" command gained a "NO_SOURCE_PERMISSIONS"
option to suppress copying the input file’s permissions to the
output file.
* The "execute_process()" command gained a "COMMAND_ERROR_IS_FATAL"
option to specify a fatal error.
* The "file(ARCHIVE_CREATE)" command gained a "COMPRESSION_LEVEL"
option to specify the compression level.
* The "file(CHMOD)" and "file(CHMOD_RECURSE)" subcommands were added
to set permissions of files and directories.
* The "file(DOWNLOAD)" command "" argument is now optional. If
it is not specified, the file is not saved.
* The "file(GENERATE)" command gained a new "TARGET" keyword to
support resolving target-dependent generator expressions.
* The "file()" command gained a new "REAL_PATH" sub-command to compute
a path with symlinks resolved.
* The "find_package()" command learned to handle a version range.
* The "separate_arguments()" command gained a new "PROGRAM" option. It
allows the arguments to be treated as a program invocation and will
resolve the executable to a full path if it can be found.
* The "DIRECTORY" option of the "set_property()", "get_property()",
and "get_directory_property()" commands now accepts references to
binary directory paths, such as the value of
"CMAKE_CURRENT_BINARY_DIR".
* The "string()" command gained a set of new "JSON" sub commands that
provide JSON parsing capabilities.
Variables
---------
* The "CMAKE_CLANG_VFS_OVERLAY" variable was added to tell Clang to
use a VFS overlay to support the Windows SDK when cross-compiling
from hosts with case-sensitive filesystems.
* The "CMAKE_MFC_FLAG" variable now supports generator expressions.
* The "CMAKE_OPTIMIZE_DEPENDENCIES" variable was added to initialize
the new "OPTIMIZE_DEPENDENCIES" target property and avoid
unnecessarily building dependencies for a static library.
* The "CMAKE_PCH_INSTANTIATE_TEMPLATES" variable was added to
initialize the new "PCH_INSTANTIATE_TEMPLATES" target property.
* The "CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM" variable was
added to tell the Visual Studio Generators what maximum version of
the Windows SDK to choose.
Properties
----------
* The "EXCLUDE_FROM_ALL" target property now supports "generator
expressions".
* The "OPTIMIZE_DEPENDENCIES" target property was added to avoid
unnecessarily building dependencies for a static library.
* The "PCH_INSTANTIATE_TEMPLATES" target property was added to enable
template instantiation in the precompiled header. This is enabled by
default and may significantly improve compile times. Currently only
supported for Clang (version 11 or later).
* The "WIN32_EXECUTABLE" target property now supports "generator
expressions".
Modules
-------
* The "CheckCompilerFlag" module has been added to generalize
"CheckCCompilerFlag" and "CheckCXXCompilerFlag" to more languages.
It also supports the "CUDA" and "ISPC" languages.
* The "CheckLinkerFlag" module now supports the "CUDA" language.
* The "CheckSourceCompiles" module has been added to generalize
"CheckCSourceCompiles" and "CheckCXXSourceCompiles" to more
languages. It also supports the "CUDA" and "ISPC" languages.
* The "CheckSourceRuns" module has been added to generalize
"CheckCSourceRuns" and "CheckCXXSourceRuns" to more languages. It
also supports the "CUDA" language.
* The "CMakePackageConfigHelpers" module gained support for version
ranges.
* The "FindCUDAToolkit" module gained support for finding CUDA
toolkits that do not contain "nvcc", as well as for finding
scattered toolkit installations when cross-compiling.
* The "FindPackageHandleStandardArgs" module learned to handle version
ranges. It also gained the "find_package_check_version()" command to
check the validity of a version against version-related arguments of
"find_package()" command.
* The "FindPython3", "FindPython2" and "FindPython" modules gained the
ability to handle a version range.
* The "FindPython3", "FindPython2" and "FindPython" modules provide,
respectively, the variable "Python3_LINK_OPTIONS",
"Python2_LINK_OPTIONS" and "Python_LINK_OPTIONS" for link options.
* The "FindSDL" module now provides:
* An imported target "SDL::SDL".
* Result variables "SDL_LIBRARIES" and "SDL_INCLUDE_DIRS".
* Version variables "SDL_VERSION", "SDL_VERSION_MAJOR",
"SDL_VERSION_MINOR", and "SDL_VERSION_PATCH".
* The "FindSWIG" module gained the ability to handle a version range.
* The "FindTIFF" module gained a "CXX" component to find the "tiffxx"
library containing C++ bindings.
* The "FindVulkan" module now provides a "Vulkan::glslc" imported
target and associated "Vulkan_GLSLC_EXECUTABLE" variable which
contain the path to the GLSL SPIR-V compiler.
* The "UseSWIG" module gained support for new source file properties
"OUTPUT_DIR" and "OUTFILE_DIR" to manage output directories on a
per-source basis.
CTest
-----
* "ctest(1)" now supports the CUDA "compute-sanitizer" checker
(previously known as "cuda-memcheck") as the
"CTEST_MEMORYCHECK_COMMAND". The different tools ("memcheck",
"racecheck", "synccheck" and "initcheck") supported by "compute-
sanitizer" can be selected by adding appropriate flags to the
"CTEST_MEMORYCHECK_COMMAND_OPTIONS" variable. The default flags are
"--tool memcheck --leak-check full".
CPack
-----
* CPack gained the "CPACK_PRE_BUILD_SCRIPTS",
"CPACK_POST_BUILD_SCRIPTS", and "CPACK_PACKAGE_FILES" variables.
* The "CPack External Generator" gained the
"CPACK_EXTERNAL_BUILT_PACKAGES" variable.
* The "CPack WIX Generator" gained a "CPACK_WIX_CUSTOM_XMLNS" option
to specify custom XML namespaces.
Other
-----
* Interface Libraries may now have source files added via
"add_library()" or "target_sources()". Those with sources will be
generated as part of the build system.
Deprecated and Removed Features
===============================
* Compatibility with versions of CMake older than 2.8.12 is now
deprecated and will be removed from a future version. Calls to
"cmake_minimum_required()" or "cmake_policy()" that set the policy
version to an older value now issue a deprecation diagnostic.
* An explicit deprecation diagnostic was added for policy "CMP0071"
("CMP0071" and below were already deprecated). The "cmake-
policies(7)" manual explains that the OLD behaviors of all policies
are deprecated and that projects should port to the NEW behaviors.
* macOS SDKs older than 10.5 are no longer supported.
* "cmake-gui(1)" now requires Qt5. Support for compiling with Qt4 has
been removed.
* The "cmake(1)" command-line option "--warn-unused-vars" has been
removed and is now silently ignored. The option has not worked
correctly since CMake 3.3.
Documentation
=============
The following guides have been added:
* "IDE Integration Guide"
* "Importing and Exporting Guide"
Other Changes
=============
* Building for macOS will now use the latest SDK available on the
system, unless the user has explicitly chosen a SDK using
"CMAKE_OSX_SYSROOT". The deployment target or system macOS version
will not affect the choice of SDK.
* The "CMAKE_<LANG>_COMPILER" variable may now be used to store
“mandatory” compiler flags like the "CC" and other environment
variables.
* The "CMAKE_<LANG>_FLAGS_INIT" variable will now be considered during
the compiler identification check if other sources like
"CMAKE_<LANG>_FLAGS" or "CFLAGS" are not set.
* The "find_program()" command now requires permission to execute but
not to read the file found. See policy "CMP0109".
* An imported target missing its location property fails during
generation if the location is used. See policy "CMP0111".
* The following target-based generator expressions that query for
directory or file name components no longer add a dependency on the
evaluated target. See policy "CMP0112".
* "TARGET_FILE_DIR"
* "TARGET_LINKER_FILE_BASE_NAME"
* "TARGET_LINKER_FILE_NAME"
* "TARGET_LINKER_FILE_DIR"
* "TARGET_SONAME_FILE_NAME"
* "TARGET_SONAME_FILE_DIR"
* "TARGET_PDB_FILE_NAME"
* "TARGET_PDB_FILE_DIR"
* "TARGET_BUNDLE_DIR"
* "TARGET_BUNDLE_CONTENT_DIR"
* Makefile Generators no longer repeat custom commands from target
dependencies. See policy "CMP0113".
* The "ExternalProject" module handling of step target dependencies
has been revised. See policy "CMP0114".
* The "OSX_ARCHITECTURES" target property is now respected for the
"ASM" language.
* If "CUDA" compiler detection fails with user-specified
"CMAKE_CUDA_ARCHITECTURES" or "CMAKE_CUDA_HOST_COMPILER", an error
is raised.
This mechanism is a kludge -- I would like to just say
LIBS+= -lm
but that doesn't work with cmake. Feel free to replace this by a
better mechanism for cmake!
2020-05-03 Jeremy Sowden <jeremy@azazel.net>
* configure.ac: bump version to 0.7.3.
2020-05-03 Jeremy Sowden <jeremy@azazel.net>
* src/Makefile.am: bump library version to 3.0.1.
2020-05-03 Jeremy Sowden <jeremy@azazel.net>
* src/wmgeneral.c, src/wmgeneral.h: fix multiple definitions of
global variable. The `display` variable is declared in
wmgeneral.h with no explicit linkage. This may result in there
being definitions of it in the library and the object-files of
applications which link against it, which causes link failures
when building these applications with GCC 10, since this uses
-fno-common by default. Add `extern` to the header declaration
and a separate declaration with no linkage in wmgeneral.c where it
is initialized.
2020-05-03 Jeremy Sowden <jeremy@azazel.net>
* Makefile.am, autogen: add autogen.
2019-06-13 Jeremy Sowden <jeremy@azazel.net>
* src/daargs.c: removed assertion that short-form options have
length 2. The mixed-option parsing code includes an assertion
that short-form options have a length of two. However, there is
no other validation of this requirement and some dock-apps do not
comply with it, which means that if one exec's them with an
unrecognized option or a mix of short options, the assertion fails
and the app aborts. For example:
$ /usr/bin/wmail --help | grep '\<display\>'
-display <string> display to use
$ /usr/bin/wmail --blah
wmail: daargs.c:126: contains: Assertion `strlen(needle) == 2' failed.
Aborted
Since there is no explicit statement of this requirement, let's
replace the assertion with a conditional.
2019-01-04 Anil N' via Window Maker Development <wmaker-dev@googlegroups.com>
* src/damain.c: Fix for missing windowname and one more.
- "Untitled window" appears in xfce4-wmdock-plugin's enumeration
of dockapps using libdockapp.
- Reference to string buffer that might not live long enough.
2018-06-27 Doug Torrance <dtorrance@piedmont.edu>
* Makefile.am, NEWS: Update old windowmaker.org/dockapps urls to
dockapps.net
2018-05-14 Doug Torrance <dtorrance@piedmont.edu>
* NEWS, configure.ac: Update mailing list links to new Google
Groups.
2017-08-31 Doug Torrance <dtorrance@piedmont.edu>
* src/dapixmap.c, src/dockapp.h: Add DAMakeShapeFromData() and
DAMakeShapeFromFile() functions. libdockapp supports shaped
dockapps with the DASetShape() function, but this function
requires as input a bitmap. Previously, there was no support for
creating such a bitmap from XBM data without using Xlib directly.
We add two functions, DAMakeShapeFromData(), which is a wrapper
around XCreateBitmapFromData and allows developers to #include XBM
data, and DAMakeShapeFromFile(), which is a wrapper around
XReadBitmapfile and lets developers specify the path to an XBM
file.
2017-08-30 Doug Torrance <dtorrance@piedmont.edu>
* src/daargs.c, src/daargs.h, src/damain.c: Make
DAParseArguments() optional. Some dockapps may want to handle
command line options themselves, so we make this function
optional. Previously, if this function was skipped, then a
segfault would result when trying to access the _daContext global
while first creating the dockapp window. Now we check if
_daContext has been initialized first, and if not, we initialize
it.
2017-08-12 Doug Torrance <dtorrance@piedmont.edu>
* Makefile.am: Use Requires.private in pkg-config file to avoid
overlinking.
2017-04-27 Doug Torrance <dtorrance@piedmont.edu>
* src/damain.c: Don't withdraw dockapps in windowed mode. In
Window Maker, windows with application class "DockApp" are
automatically withdrawn. We don't want this in windowed mode. We
use the application name instead, with the usual convention of
capitalizing the initial letter.
2017-04-26 Doug Torrance <dtorrance@piedmont.edu>
* src/wmgeneral.c: Do not include pathnames in Window Name and
Class Properties Patch by Corin-EU from GitHub [1]. In
libdockapps file wmgeneral.c, wname is set from argv[0] and is
then used to set the window name and class resource. Often
applications are called with their full path which then means that
the window name has a path in it, thereby requiring an unwieldy
path specific string for "Name" in WMState if the applet is to be
captured in the WM dock. The simple solution is that wname should
be the basename of argv[0] to ensure that the window name for the
applet is the simple and obvious one. Thus the inclusion of
header file libgen.h is required. Just say "no" to path slashes
"/" in window name/class resources ....
[1] https://github.com/d-torrance/dockapps/issues/5
2015-10-20 Doug Torrance <dtorrance@piedmont.edu>
* configure.ac: Bump to version 0.7.2.
2015-10-20 Doug Torrance <dtorrance@piedmont.edu>
* Makefile.am: Clean generated file dockapp.pc.
Based on the Debian patch [1].
[1] https://sources.debian.net/src/1:0.7.1-1/debian/patches/
clean_dockapp.pc.patch/
2015-10-20 Doug Torrance <dtorrance@piedmont.edu>
* configure.ac, src/Makefile.am:
Remove AC_PATH_XTRA macro from configure.ac
We already check for libraries with the PKG_CHECK_MODULES macros.
This also allows the Debian package to drop the Build-Depend on
libice-dev. Based on the Debian patch [1].
[1] https://sources.debian.net/src/1:0.7.1-1/debian/patches/
remove_AC_PATH_XTRA.diff/
2015-10-20 Doug Torrance <dtorrance@piedmont.edu>
* Recompress fonts without timestamp.
This fixes the package-contains-timestamped-gzip warning given by
Lintian for the Debian package. (This warning is really
unnecessary, as its purpose it to check for reproducible builds and
the fonts are not compressed at build time, but I see no harm in
removing these timestamps.)
2015-10-17 Doug Torrance <dtorrance@piedmont.edu>
* configure.ac: Bump to version 0.7.1.
2015-10-17 Doug Torrance <dtorrance@piedmont.edu>
* Makefile.am: Update update-changelog target in Makefile.
Only grab libdockapp commits.
2015-10-17 Doug Torrance <dtorrance@piedmont.edu>
* examples/basic/basic.c, examples/rectangles/rectangles.c: Update
header location in examples.
2015-10-09 Shining <wmaker-dev@linuxcondom.net>
* README: Simplify instructions to generate a ./configure script.
Based on suggestions by Alexey Frolov and BALATON Zoltan.
2015-10-05 Shining <wmaker-dev@linuxcondom.net>
* README: Info about generating 'configure' script in README.
In the README it is said to run ./configure but there's no such
script in the tarball. I wrote instructions to generate a
./configure with libtool and autotools.
2015-08-15 Rodolfo García Peñas (kix) <kix@kix.es>
* Include libwmgeneral in libdockapp.
This patch includes the libwmgeneral library in the libdockapp library.
The new library is now version 3 (previous was version 2) and it
includes the new include folder in $libdir/libdockapp. The wmgeneral
files were moved from the previous folder (libwmgeneral) and the folder
is now removed.
Signed-off-by: Rodolfo García Peñas (kix) <kix@kix.es>
2014-11-28 Doug Torrance <dtorrance@monmouthcollege.edu>
* NEWS, configure.ac: Release version 0.6.4.
2014-11-28 Doug Torrance <dtorrance@monmouthcollege.edu>
* Makefile.am, NEWS, configure.ac: Update contact information.
2014-11-28 Doug Torrance <dtorrance@monmouthcollege.edu>
* Add update-changelog target to Makefile to update ChangeLog.
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* ChangeLog, NEWS, examples/basic/basic.c, src/dockapp.h:
Merge ChangeLog into NEWS (they were largely the same).
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* examples/basic/basic.c: Add #include
<time.h> to basic example.
Otherwise, we get the following compiler warning
basic.c: Infunction ‘main’: basic.c:111:2: warning: implicit
declaration of function ‘time’ [-Wimplicit-function-declaration]
srandom(time(NULL));
^
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* README, examples/Makefile.am, examples/basic/Imakefile,
examples/basic/Makefile, examples/rectangles/Imakefile,
examples/rectangles/Makefile: Replace example
Imakefiles with Makefiles. imake is deprecated.
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* examples/basic/basic.c, examples/rectangles/rectangles.c,
src/daargs.c, src/daargs.h, src/dacallback.c, src/dacolor.c,
src/daevent.c, src/damain.c, src/dapixmap.c, src/darect.c,
src/dashaped.c, src/dautil.c, src/dockapp.h: Use consistent code
formatting.
Used uncrustify to minimize warnings and errors from checkpatch.pl
in the Window Maker source tree.
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* examples/basic/Imakefile, examples/basic/basic.c,
examples/rectangles/Imakefile, examples/rectangles/rectangles.c,
src/Makefile.am, src/daargs.c, src/daargs.h, src/dacallback.c,
src/dacolor.c, src/daevent.c, src/damain.c, src/dapixmap.c,
src/darect.c, src/dashaped.c, src/dautil.c, src/dautil.h,
src/dockapp.h: Remove CVS cruft.
2014-11-25 Doug Torrance <dtorrance@monmouthcollege.edu>
* examples/basic/Imakefile, examples/basic/README,
examples/basic/basic.c, examples/rectangles/Imakefile,
examples/rectangles/rectangles.c, fonts/Makefile.am, src/dacallback.c,
src/dacolor.c, src/daevent.c, src/damain.c, src/dapixmap.c,
src/dashaped.c, src/dockapp.h: Remove trailing whitespace.
2014-11-24 Doug Torrance <dtorrance@monmouthcollege.edu>
* INSTALL, Makefile.in, aclocal.m4, compile, config.guess,
config.sub, configure, dockapp.pc, examples/Makefile.in,
fonts/Makefile.in, install-sh, ltmain.sh, missing, src/Makefile.in:
Remove autotools-generated files.
2014-11-24 Doug Torrance <dtorrance@monmouthcollege.edu>
* Add version 0.6.3 to repository.
Obtained from:
http://sourceforge.net/projects/files/
libdockapp-0.6.3.tar.gz/download
** Changes above this point from git log in dockapps git repository. **
2014-06-06 Doug Torrance <dtorrance@monmouthcollege.edu>
* ChangeLog, NEWS: updated Changelog and NEWS files with new version
2014-06-06 Doug Torrance <dtorrance@monmouthcollege.edu>
* Makefile.am: add xext to dockapp.pc
2014-06-06 Doug Torrance <dtorrance@monmouthcollege.edu>
* configure.ac, src/Makefile.am: add xpm to linked libraries
2014-06-06 Doug Torrance <dtorrance@monmouthcollege.edu>
* .gitignore, autogen.sh, do_verify.sh: add more autotools-generated
files to .gitignore
2014-06-06 Doug Torrance <dtorrance@monmouthcollege.edu>
* configure.ac, src/Makefile.am: use pkg-config for linked libraries
2014-05-02 Doug Torrance <dtorrance@monmouthcollege.edu>
* Makefile.am: added BUGS to distribution tarball
2014-05-02 Doug Torrance <dtorrance@monmouthcollege.edu>
* .gitignore: Update .gitignore (add configure.no-verify).
2014-05-01 Doug Torrance <dtorrance@monmouthcollege.edu>
* .gitignore, Makefile.am: Add pkg-config dockapp.pc file.
2014-05-01 Doug Torrance <dtorrance@monmouthcollege.edu>
* configure.ac: Modernize configure.ac.
2014-05-01 Doug Torrance <dtorrance@monmouthcollege.edu>
* .gitignore, Makefile.in, aclocal.m4, compile, config.guess,
config.sub, configure, examples/Makefile.in, fonts/Makefile.in,
ltmain.sh, missing, src/Makefile.in: Remove autotools-generated
files, update .gitignore.
2014-05-01 Doug Torrance <dtorrance@monmouthcollege.edu>
* fonts/Makefile.am: Actually added fonts to distribution tarball.
Despite the commit message of the previous commit, this was not
done. Now it is.
2014-05-01 Doug Torrance <dtorrance@monmouthcollege.edu>
* configure.ac, fonts/Makefile.am, fonts/fonts.alias,
fonts/fonts.dir: Various changes to `make install' of fonts.
* Use font-util macros.
* Include fonts in distribution tarball.
* Removed fonts.dir (built by `make install') and fonts.alias (empty
file).
2014-04-30 Doug Torrance <dtorrance@monmouthcollege.edu>
* examples/Makefile.am: rewrite examples Makefile.am to ensure they
are included in the tarball
2014-04-30 Doug Torrance <dtorrance@monmouthcollege.edu>
* INSTALL, Makefile.in, aclocal.m4, compile, config.guess,
config.sub, configure, configure.ac, configure.in,
examples/Makefile.in, fonts/Makefile.in, install-sh, ltmain.sh,
missing, src/Makefile.in: rename configure.in -> configure.ac
2014-04-30 Doug Torrance <dtorrance@monmouthcollege.edu>
* .gitignore: added .gitignore
2014-04-30 Doug Torrance <dtorrance@monmouthcollege.edu>
* CVS/Entries, CVS/Repository, CVS/Root, autom4te.cache/output.0,
autom4te.cache/output.1, autom4te.cache/requests,
autom4te.cache/traces.0, autom4te.cache/traces.1,
examples/CVS/Entries, examples/CVS/Repository, examples/CVS/Root,
examples/basic/CVS/Entries, examples/basic/CVS/Repository,
examples/basic/CVS/Root, examples/rectangles/CVS/Entries,
examples/rectangles/CVS/Repository, examples/rectangles/CVS/Root,
examples/shapes/CVS/Entries, examples/shapes/CVS/Repository,
examples/shapes/CVS/Root, fonts/CVS/Entries, fonts/CVS/Repository,
fonts/CVS/Root, src/CVS/Entries, src/CVS/Repository, src/CVS/Root:
Removed CVS directories
2014-04-24 Doug Torrance <dtorrance@monmouthcollege.edu>
* Initial commit
** Changes above this point from git log in sourceforge git repository. **
This change has a few useful new features, along with a lot of bugfixes and some internal code reorganization for future projects. We have been questing to improve test quality and stamp down bugs that came in over the 1.6 series.
As usual many thanks to the numerous contributors who sent in patches or helped test this release!
Fixes
crawler: remove bad mutex unlock during error
idle_timeout: avoid long hangs during shutdown
extstore: use fcntl locking on disk file
portability fix for getsubopt
illumos build fixes + require libevent2
core: generalize extstore's defered IO queue
fix connection limit tests
logger: fix spurious watcher hangups
watcher.t: reduce flakiness
Extend test CA validity to 500 years
adjust "t/idle-timeout.t" be more forgiving
New Features
arm64: Re-add arm crc32c hw acceleration for extstore
restart mode: expose memory_file path in stats settings
'shutdown graceful' command for raising SIGUSR1
Introduce NAPI ID based worker thread selection (see doc/napi_ids.txt)
item crawler hash table walk mode
Features
Automatic updates to go.sum
Previously, go.mod-related quick fixes would not make corresponding
changes to your go.sum file. Now, when you add or remove dependencies
from your module, your go.sum will be updated accordingly.
Removed support for go mod tidy on save
We have removed the support for running go mod tidy on save for
go.mod files. It proved to be too slow and expensive to be worth
it.
Experimental
Multi-module workspace support
The proposal described in golang/go#32394 is still in development
and off by default. See our progress by tracking the multi-module
workspace milestone and project.
Enable multi-module workspace support by adding the following to
your settings:
"gopls": { "experimentalWorkspaceModule": true, }
With this setting, you will be able to open a directory that contains
multiple modules. Most features will work across modules, but some,
such as goimports, will not work as expected.
Give this a try if you're interested in this new feature, but please
note that it is still very experimental.
Fixes
A list of all issues fixed can be found in the gopls/v0.5.3 milestone.
New in 1.16.3:
* New features added
- In the testsuite summary, the "for $(PACKAGE_STRING)" suffix
can be overridden with the AM_TESTSUITE_SUMMARY_HEADER variable.
* Bugs fixed
- Python 3.10 version number no longer considered to be 3.1.
- Broken links in manual fixed or removed, and new script
contrib/checklinkx (a small modification of W3C checklink) added,
with accompany target checklinkx to recheck urls.
- install-exec target depends on $(BUILT_SOURCES).
- valac argument matching more precise, to avoid garbage in DIST_COMMON.
- Support for Vala in VPATH builds fixed so that both freshly-generated and
distributed C files work, and operation is more reliable with or without
an installed valac.
- Dejagnu doesn't break on directories containing spaces.
* Distribution
- new variable AM_DISTCHECK_DVI_TARGET, to allow overriding the
"make dvi" that is done as part of distcheck.
* Miscellaneous changes
- install-sh tweaks:
. new option -p to preserve mtime, i.e., invoke cp -p.
. new option -S SUFFIX to attempt backup files using SUFFIX.
. no longer unconditionally uses -f when rm is overridden by RMPROG.
. does not chown existing directories.
- Removed function up_to_date_p in lib/Automake/FileUtils.pm.
We believe this function is completely unused.
- Support for in-tree Vala libraries improved.
* Noteworthy changes in release 3.7.4 (2020-11-14) [stable]
** Bug fixes
*** Bug fixes in yacc.c
In Yacc mode, all the tokens are defined twice: once as an enum, and then
as a macro. YYEMPTY was missing its macro.
*** Bug fixes in lalr1.cc
The lalr1.cc skeleton used to emit internal assertions (using YY_ASSERT)
even when the `parse.assert` %define variable is not enabled. It no
longer does.
The private internal macro YY_ASSERT now obeys the `api.prefix` %define
variable.
When there is a very large number of tokens, some assertions could be long
enough to hit arbitrary limits in Visual C++. They have been rewritten to
work around this limitation.
** Changes
The YYBISON macro in generated "regular C parsers" (from the "yacc.c"
skeleton) used to be defined to 1. It is now defined to the version of
Bison as an integer (e.g., 30704 for version 3.7.4).
8.6.0
-----
* New itertools
* :func:`all_unique`
* :func:`nth_product` and :func:`nth_permutation`
* Changes to existing itertools
* :func:`chunked` and :func:`sliced` now accept a ``strict`` parameter
* Other changes
* Python 3.5 has reached its end of life and is no longer supported.
* Python 3.9 is officially supported.
* Various documentation fixes
1.4.0
- Upgrade to libgit2 1.1, new ``GIT_BLAME_IGNORE_WHITESPACE`` constant
- Add wheels for Python 3.9
- Drop support for PyPy3 7.2
- New optional ``flags`` argument in ``Repository.__init__(...)``,
new ``GIT_REPOSITORY_OPEN_*`` constants
- Documentation
Overview of changes in GLib 2.66.3
==================================
* Fix awkward bug with `GPollFD` handling in some situations (work by Claudio
Saavedra and Eugene M)
* Fix sending FDs attached to very large D-Bus messages (work by Simon McVittie
and Giovanni Campagna)
* Bugs fixed:
- Main loop ignores GPollFD sources when there is at least one source ready with priority higher than default one
- Backport !1718 “gtrace: Add G_GNUC_PRINTF annotation” to glib-2-66
- Backport !1713 “gmain: g_main_context_check() can skip updating polled FD sources” to glib-2-66
- Backport !1711 “Fix race in socketclient-slow test” to glib-2-66
- Backport !1725 “gdbus: Cope with sending fds in a message that takes multiple writes” to glib-2-66
- Backport !1734 “glocalfileinfo: Use a single timeout source at a time for hidden file cache” to glib-2-66
Overview of changes in GLib 2.66.2
==================================
* Important and time-critical fix to DST transitions which will happen in Europe
on 2020-10-25 on distributions which use the ‘slim’ tzdata format (which is
now the default in tzdata/tzcode 2020b) (work by Claudi M., LRN)
* Further timezone handling changes to restore support for changing the timezone
when `/etc/localtime/` changes (work by António Fernandes, Sebastian Keller)
* Fix deadlock on Windows when `G_SLICE` is set in the environment (diagnosis by
Christoph Reiter)
* Fix UTF-8 validation when escaping URI components (thanks to Marc-André Lureau) (!1680)
* Bugs fixed:
- fstatat is available only on macOS 10.10+
- top bar time is incorrect, timezone map in control center is broken
- Setting G_SLICE makes Windows programs hang since 2.66
- Backport !1680 “guri: Fix UTF-8 validation when escaping URI components” to glib-2-66
- Backport !1684 “glocalfileinfo: Fix use of fstatat() on macOS < 10.10” to glib-2-66
- uri: add missing (not)nullable annotations
- Backport !1691 “gmain: Fix possible locking issue in source unref” to glib-2-66
- Backport !1692 “gsignal: Plug g_signal_connect_object leak” to glib-2-66
- Backport !1661 “Lookup fallback time zones in the cache to improve performance” to glib-2-66
- Backport !1698 “gslice: Inline win32 implementation of g_getenv() to avoid deadlock” to glib-2-66
- Backport !1683 “Fix the 6-days-until-the-end-of-the-month bug” to glib-2-66
- Backport !1706 “Add various missing nullable annotations” to glib-2-66
* Translation updates:
- Chinese (Taiwan)
- Portuguese
- Slovak
Overview of changes in GLib 2.66.1
==================================
* A performance problem where timezones were reloaded from disk every time a
`GTimeZone` was created has been fixed
`/etc/localtime` will not take effect until a process restarts; future changes
in a subsequent 2.66.x release will improve this
* Security fix for incorrect scope/zone ID parsing in URIs (!1669)
* Bugs fixed:
- Invalid Pointer Arithmetic in g_path_get_basename
- GDBus DBUS_COOKIE_SHA1 mechanism may use too old a key
- gtk3/glib crash on gimp
- Time zone cache is constantly invalidated if TZ is NULL
- gthreadedresolver: faulty logic in parse_res_txt
- Define G_MSVC_SYMBOL_PREFIX correctly for ARM
- Minor Coverity fixes
- Fix various signedness warnings
- glocalfile: Never require G_LOCAL_FILE_STAT_FIELD_ATIME
- trash portal: Handle portal failures
- gio-tool-trash: Prevent recursion to speed up emptying trash
- glist: Clarify that g_list_free() and friends only free an entire list
- utils: Limit the scope of the variable `max`
- Fix g_module_symbol() under Windows sometimes not succeeding
- guri: Fix URI scope parsing
- gdatetime: Avoid integer overflow creating dates too far in the past
* Translation updates:
- Danish
- Greek, Modern (1453-)
- Hebrew
- Latvian
- Portuguese
- Russian
0.56.0:
* meson test can now filter tests by subproject
* Native (build machine) compilers not always required by project()
* New extra_files key in target introspection
* Preliminary AIX support
* Wraps from subprojects are automatically promoted
* meson.build_root() and meson.source_root() are deprecated
* dep.as_link_whole()
* Add support for all Windows subsystem types
* Added NVidia HPC SDK compilers
* Project and built-in options can be set in native or cross files
* unstable-keyval is now stable keyval
* CMake subproject cross compilation support
* Machine file keys are stored case sensitive
* Consistency between declare_dependency() and pkgconfig.generate() variables
* Qt5 compile_translations now supports qresource preprocessing
* Controlling subproject dependencies with dependency(allow_fallback: ...)
* Custom standard library
* Improvements for the builtin curses dependency
* HDF5 dependency improvements
* External projects
* Per subproject warning_level option
* meson subprojects command
* Added CompCert C compiler
* Dependencies listed in test and benchmark introspection
* include_type support for the CMake subproject object dependency method
* Deprecate Dependency.get_pkgconfig_variable and Dependency.get_configtool_variable
0.18.0
Added support for creating missing folders when using --pylint-output-file
Now when pylint's ignore_patterns is blank, we don't ignore all files
Added cache invalidation when your pylintrc changes
Verified support for latest pytest and Python 3.9
Corrected badly named nodes (duplicated path) thanks to yanqd0
Added tests to source distribution thanks to sbraz
Changelog:
Notable Changes in NSS 3.59
Exported two existing functions from libnss, CERT_AddCertToListHeadWithData
and CERT_AddCertToListTailWithData
NOTE: NSS will soon require GCC 4.8 or newer. Gyp-based builds will stop
supporting older GCC versions first, followed a few releases later by the
make-based builds. Users of older GCC versions can continue to use the
make-based build system while they upgrade to newer versions of GCC.
Bugs fixed in NSS 3.59
* Bug 1607449 - Lock cert->nssCertificate to prevent a potential data race
* Bug 1672823 - Add Wycheproof test cases for HMAC, HKDF, and DSA
* Bug 1663661 - Guard against NULL token in nssSlot_IsTokenPresent
* Bug 1670835 - Support enabling and disabling signatures via Crypto Policy
* Bug 1672291 - Resolve libpkix OCSP failures on SHA1 self-signed root certs
when SHA1 signatures are disabled.
* Bug 1644209 - Fix broken SelectedCipherSuiteReplacer filter to solve some
test intermittents
* Bug 1672703 - Tolerate the first CCS in TLS 1.3 to fix a regression in our
CVE-2020-25648 fix that broke purple-discord
* Bug 1666891 - Support key wrap/unwrap with RSA-OAEP
* Bug 1667989 - Fix gyp linking on Solaris
* Bug 1668123 - Export CERT_AddCertToListHeadWithData and
CERT_AddCertToListTailWithData from libnss
* Bug 1634584 - Set CKA_NSS_SERVER_DISTRUST_AFTER for Trustis FPS Root CA
* Bug 1663091 - Remove unnecessary assertions in the streaming ASN.1 decoder
that affected decoding certain PKCS8 private keys when using NSS debug builds
* Bug 1670839 - Use ARM crypto extension for AES, SHA1 and SHA2 on MacOS.
Fix some pkglint while here.
Changes between GMP version 6.2.0 and 6.2.1
BUGS FIXED
* A possible overflow of type int is avoided for mpz_cmp on huge operands.
* Overflows are more carefully detected and reported for mpz_pow_ui.
* A bug in longlong.h for aarch64 sub_ddmmss, not affecting GMP, was healed.
* mini-gmp: mpz_out_str and mpq_out_str now correctly handle out of
range bases.
FEATURES
* C90 compliance.
* Initial support for Darwin on arm64, and improved portability.
* Support for more processors.
SPEEDUPS
* None, except indirectly through recognition of new CPUs.
- Add way to configure `MOB_WIP_BRANCH_QUALIFIER` via an environment
variable instead of `--branch` parameter. Helpful if multiple teams
work on the same repository.
- Add way to configure `MOB_WIP_BRANCH_QUALIFIER_SEPARATOR` via an
environment variable. Defaults to '/'. Will change to '-' in future
versions to prevent branch naming conflicts (one cannot have a branch
named `mob/main` and a branch named `mob/main/green` because
`mob/main` cannot be a file and a directory at the same time).
Upstream changes:
1.006 2020-09-28
- re-release with minor fixes to cover modern toolchain
- apply fix for RT#128096 reported by ANDK, thank you Andreas
Protocol Buffers v3.14.0
Python
Print google.protobuf.NullValue as null instead of "NULL_VALUE" when it is
used outside WKT Value/Struct.
Fix bug occurring when attempting to deep copy an enum type in python 3.
Add a setuptools extension for generating Python protobufs
Remove uses of pkg_resources in non-namespace packages.
[bazel/py] Omit google/init.py from the Protobuf runtime.
Removed the unnecessary setuptools package dependency for Python package
Fix PyUnknownFields memory leak
Protocol Buffers v3.14.0
Protocol Compiler
The proto compiler no longer requires a .proto filename when it is not
generating code.
Added flag --deterministic_output to protoc --encode=....
Fixed deadlock when using google.protobuf.Any embedded in aggregate options.
C++
Arenas are now unconditionally enabled. cc_enable_arenas no longer has
any effect.
Removed inlined string support, which is incompatible with arenas.
Fix a memory corruption bug in reflection when mixing optional and
non-optional fields.
Make SpaceUsed() calculation more thorough for map fields.
Add stack overflow protection for text format with unknown field values.
FieldPath::FollowAll() now returns a bool to signal if an out-of-bounds
error was encountered.
Performance improvements for Map.
Minor formatting fix when dumping a descriptor to .proto format with
DebugString.
UBSAN fix in RepeatedField.
When running under ASAN, skip a test that makes huge allocations.
Fixed a crash that could happen when creating more than 256 extensions in
a single message.
Fix a crash in BuildFile when passing in invalid descriptor proto.
Parser security fix when operating with CodedInputStream.
Warn against the use of AllowUnknownExtension.
Migrated to C++11 for-range loops instead of index-based loops where
possible. This fixes a lot of warnings when compiling with -Wsign-compare.
Fix segment fault for proto3 optional
Adds a CMake option to build libprotoc separately
This was lost in a previous update, and is required to ensure MACHINE_ARCH is
set correctly. Fixes MACHINE_ARCH issues reported on OpenBSD/amd64 by various
people.
The only other OS I can find that supports malloc_options is OpenBSD, and that
does not support the "A" flag. Besides, there are better ways to set the
flags instead of hardcoding them in a binary.
NEW IN WAF 2.0.21
-----------------
* Set the default --msvc_version from VSCMD_VER if present
* Force unit-test reruns on ut_str, ut_cmd or ut_path changes
* Describe Qt5's library detection
* Introduce conf.env.ASMDEFINES_ST to enable assembly-specific define flags
* Update extras/xcode6 to Python3
* Enable parameter "always" in extras/doxygen
* Fix extras/c_dumbpreproc as it was previously broken
* Fix extras/gccdeps and extras/msvcdeps on header renaming
* Improve extras/msvcdeps debug outputs and flags
* Add add MCST Elbrus CPU detection in c config
* Add minio object copies to extras/wafcache
2.25.0
Improvements
Added support for NETRC environment variable.
Dependencies
Requests now supports urllib3 v1.26.
Deprecations
Requests v2.25.x will be the last release series with support for Python 3.5.
The requests[security] extra is officially deprecated and will be removed in Requests v2.26.0.
10.1.0 -- 2020-10-31
--------------------
* compatibility with Mercurial 5.6
* numerous minor changes to packaging, Makefile, README moved to README.rst
* evolve: various improvements to content-divergence resolution
* evolve: fix various issues with --continue when solving content-divergence
* evolve: specify the source of config override for `server.bundle1=no`
* evolve: avoid leaving mergestate after instability resolution
* evolve: while resolving conflicts, the evolved node will no longer be a
dirstate parent (won't show up in `hg parents` and not as `@` in `hg log -G`,
but it will show up as `%` with hg >= 5.4)
* metaedit: update bookmark location when applicable
* rewind: add a --dry-run flag
* rewind: properly record rewind of splits as folds
topic (0.20.0)
* stack: support foo#stack relation revset (hg-5.4+ only)
* merge: add a experimental.topic.linear-merge option to allow oedipus merges
in some cases
Fixes
Fixed possible infinite loop when combining generators with section filter (-c option) (#2025)
Miscellaneous
Fixed ParseAndAddCatchTests not finding TEST_CASEs without tags (#2055, #2056)
ParseAndAddCatchTests supports CMP0110 policy for changing behaviour of add_test (#2057)
This was the shortlived change in CMake 3.18.0 that temporarily broke ParseAndAddCatchTests
Features
No new features have been added in this release.
Experimental
We have added support for a new allExperiments setting. By enabling
this flag, you will enable all experimental features that we intend
to roll out slowly. You can still disable individual settings (full
list of settings). In-progress features, such as multi-module
workspaces (below), will remain disabled until they are ready for
users.
Improved CPU utilization: experimentalDiagnosticsDelay
experimentalDiagnosticsDelay controls the amount of time that gopls
waits after the most recent file modification before computing deep
diagnostics. Simple diagnostics (parsing and type-checking) are
always run immediately on recently modified packages.
Enable it by setting it to a duration string, for example "200ms".
With allExperiments, this is set to "200ms".
Improved memory usage for workspaces with multiple folders:
experimentalPackageCacheKey
experimentalPackageCacheKey controls whether to use a coarser cache
key for package type information. If you use the gopls daemon, this
may reduce your total memory usage.
Enable it by setting it to true. With allExperiments, this is set
to true.
Multi-module workspace support
The proposal described in golang/go#32394 is still in development
and off by default. See our progress by tracking the multi-module
workspace milestone and project.
Enable multi-module workspace support by adding the following to
your settings:
"gopls": { "experimentalWorkspaceModule": true, }
With this setting, you will be able to open a directory that contains
multiple modules. Most features will work across modules, but some,
such as goimports, will not work as expected.
Give this a try if you're interested in this new feature, but please
note that it is still very experimental.
Support for semantic tokens
This is a new, unreleased LSP feature that provides additional
syntax highlighting. In advance of this new LSP version, we have
added preliminary support for this feature. Enable it by setting:
"gopls": { "semanticTokens": true, }
It will not be enabled with allExperiments.
Fixes
A list of all issues fixed can be found in the gopls/v0.5.2 milestone.
For editor clients
All command names have been given gopls. prefixes, to avoid
conflicting with commands registered by other language servers.
This should not have affected any clients.
5.41.2 - 2020-11-08
This patch fixes urls() strategy ensuring that ~ (tilde) is treated
as one of the url-safe characters (issue #2658).
5.41.1 - 2020-11-03
This patch improves our CLI help and documentation.
1.23.0:
Features
api-core: pass retry from result() to done()
Bug Fixes
map LRO errors to library exception types
harden install to use full paths, and windows separators on windows
update out-of-date comment in exceptions.py
0.15.0:
Added
- Add `--export` option to `set` to make it prepend the binding with `export`
Changed
- Make `set` command create the `.env` file in the current directory if no `.env` file was
found.
Fixed
- Fix potentially empty expanded value for duplicate key.
- Fix import error on Python 3.5.0 and 3.5.1.
- Fix parsing of unquoted values containing several adjacent space or tab characters
2.37 2020-11-02 09:09:13 -0700
- Tests that rely on its behavior unset ALIEN_BUILD_PKG_CONFIG (gh#239)
2.36_01 2020-10-31 03:33:21 -0600
- Fixed a bug where Probe and PkgConfig plugins could provide compiler / linker flags
when the PkgConfig probe fails, but another probe succeed. (gh#238)
2.35_01 2020-10-28 02:06:21 -0600
- Added install properties: system_probe_class and system_probe_instance_id (gh#237)
- Added hook properties: probe_class and probe_instance_id (gh#237)
2.34_01 2020-10-27 04:23:24 -0600
- Added instance_id property to Alien::Build::Plugin class (gh#235)
- Added plugin_instance_prop method to Alien::Build class (gh#235)
2.33 2020-09-21 03:21:40 -0600
- Skip problematic test on cygwin (gh#232)
5.6: not documented
= TortoiseHg 5.5.2 =
TortoiseHg 5.5.2 is a regularly scheduled bug-fix release
== Bug Fixes ==
py3: fix a bytes + str concatenation when running the resolve tool (fixes#5596 (closed))
resolve: fix a bytes vs str issue when performing a merge without auto-resolve
bugreport: fix a bytes vs str issue for a SettingsDialog argument
wix: fix the 32-bit installation (fixes#5622 (closed))
py3: ensure qtlib._styles is str (ref #810, #5599 (closed))
= TortoiseHg 5.5.1 =
TortoiseHg 5.5.1 is a regularly scheduled bug-fix release
= TortoiseHg 5.5 =
TortoiseHg 5.5 is a quarterly feature release
== Bug Fixes ==
hgcommands: don't index **opts with bytes (fixes#5567 (closed))
fileview: fix UI freezes on newer version of QScintilla
py3: numerous python3 fixes
== Improvements ==
cleanup: remove BitBucket references
topics: improve support for the topic extension
= TortoiseHg 5.1 through 5.4.2 =
TODO
Upstream release notes:
* Disabled platform-check verification of extensions by default
(now defaulting php-only), set platform-check to true if you want a complete
check
* Improved platform-check handling of issue reporting
* Fixed platform-check to only check non-dev requires even if require-dev
dependencies are installed
* Fixed issues dealing with custom installers which return trailing slashes in
getInstallPath (ideally avoid doing this as there might be other issues left)
* Fixed issues when curl functions are disabled
* Fixed gitlab-domains/github-domains to make sure if they are overridden the
default value remains present
* Fixed issues removing/upgrading packages from path repositories on Windows
* Fixed regression in 2.0.4 when handling of git@bitbucket.org URLs in vcs
repositories
* Fixed issue running create-project in current directory on Windows
Changes for Version 2.13 (2020-11-01)
* Added support for interwiki links.
* Enable <del> and <ins> markup in wiki.
* Improvements to the Forum threading display.
* Added support for embedding pikchr markup in markdown and fossil-wiki content.
* The new "pikchr" command can render pikchr scripts, optionally pre-processed with TH1 blocks and variables exactly like site skins are.
* The new pikchrshow page provides an editor and previewer for pikchr markup.
* In /wikiedit and /fileedit, Ctrl-Enter can now be used initiate a preview and to toggle between the editor and preview tabs.
* The /artifact and /file views, when in line-number mode, now support interactive selection of a range of lines to hyperlink to.
* Enhance the /finfo webpage so that when query parameters identify both a filename and a checkin, the resulting graph tracks the identified file across renames.
* The built-in SQLite is updated to an alpha of version 3.34.0, and the minimum SQLite version is increased to 3.34.0 because the /finfo change in the previous bullet depends on enhancements to recursive common table expressions that are only available in SQLite 3.34.0 and later.
* Countless other minor refinements and documentation improvements.
