ikiwiki missing? #372
Assignees
Comments
|
Thanks for the bug report. This is currently missing due to this dependency failure: I'll take a look at that today, it should be relatively straight-forward to fix. As for printing the current branch, there's no way to do that directly from pkgin but you could run something like or to print it. |
|
Thank you for looking into it! P.S.: Shouldn't it be part of pkgin to show the current brach? Wouldn't that make troubleshooting much easier for you guys, if you would provide a command for displaying the version/branch? This is probably worthy of a separate issue… |
|
It would need some thinking about, as it's possible to use multiple repositories, and that feature is hopefully going to see some enhancements soon as part of a GSOC project. I'm not sure it would end up any simpler than just extracting it directly from the configuration files, but it's probably worth reporting an issue on the pkgin project page anyway to see if others would find it useful. As for the OS X packages, they will only be tracking trunk from now on rather than the stable branches, so you can assume it would always report "trunk" :) |
|
I opened an issue over at pkgin. |
ghost
mentioned this issue
|
This is now available |
jperkin
pushed a commit
that referenced
this issue
Aug 24, 2016
Changes from 3.2.2 to 3.2.3
Improvements
It is now possible to use HDF5 with the new shared library naming scheme (>= 1.8.10, hdf5.dll instead of hdf5dll.dll) on Windows (gh-540). Thanks to Tadeu Manoel.
Now :program: ptdump sorts output by node name and does not print a backtrace if file cannot be opened. Thanks to Zbigniew Jędrzejewski-Szmek.
Bugs fixed
Only run tables.tests.test_basics.UnicodeFilename if the filesystem encoding is utf-8. Closes gh-485.
Add lib64 to posix search path. (closes gh-507) Thanks to Mehdi Sadeghi.
Ensure cache entries are removed if fewer than 10 (closes gh-529). Thanks to Graham Jones.
Fix segmentation fault in a number of test cases that use index.Index (closes gh-532 and gh-533). Thanks to Diane Trout.
Fixed the evaluation of transcendental functions when numexpr is compiled with VML support (closes gh-534, PR #536). Thanks to Tom Kooij.
Make sure that index classes use buffersizes that are a multiple of chunkshape[0] (closes gh-538, PR #538). Thanks to Tom Kooij.
Ensure benchmark paths exist before benchmarks are executed (PR #544). Thanks to rohitjamuar.
Other changes
Minimum Cython version is now v0.21
Changes from 3.2.1.1 to 3.2.2
Bug fixed
Fix AssertionError in Row.__init_loop. See gh-477.
Fix issues with Cython 0.23. See gh-481.
Only run tables.tests.test_basics.UnicodeFilename if the filesystem encoding is utf-8. Closes gh-485.
Fix missing missing PyErr_Clear. See gh-#486.
Fix the C type of some numpy attributes. See gh-494.
Cast selection indices to integer. See gh-496.
Fix indexesextension._keysort_string. Closes gh-497 and gh-498.
Changes from 3.2.1 to 3.2.1.1
Fix permission on distributed source distribution
Other changes
Minimum Cython version is now v0.21
Changes from 3.2.0 to 3.2.1
Bug fixed
Fix indexesextension._keysort. Fixes gh-455. Thanks to Andrew Lin.
Changes from 3.1.1 to 3.2.0
Improvements
The nrowsinbuf is better computed now for EArray/CArray having a small chunkshape in the main dimension. Fixes #285.
PyTables should be installable very friendly via pip, including NumPy being installed automatically in the unlikely case it is not yet installed in the system. Thanks to Andrea Bedini.
setup.py has been largely simplified and now it requires setuptools. Although we think this is a good step, please keep us informed this is breaking some installation in a very bad manner.
setup.py now is able to used pkg-config, if available, to locate required libraries (hdf5, bzip2, etc.). The use of pkg-config can be controlled via setup.py command line flags or via environment variables. Please refer to the installation guide (in the User Manual) for details. Closes gh-442.
It is now possible to create a new node whose parent is a softlink to another group (see gh-422). Thanks to Alistair Muldal.
link.SoftLink objects no longer need to be explicitly dereferenced. Methods and attributes of the linked object are now automatically accessed when the user acts on a soft-link (see gh-399). Thanks to Alistair Muldal.
Now ptrepack recognizes hardlinks and replicates them in the output (repacked) file. This saves disk space and makes repacked files more conformal to the original one. Closes gh-380.
New pttree script for printing HDF5 file contents as a pretty ASCII tree (closes gh-400). Thanks to Alistair Muldal.
The internal Blosc library has been downgraded to version 1.4.4. This is in order to still allow using multiple threads inside Blosc, even on multithreaded applications (see gh-411, gh-412, gh-437 and gh-448).
The print_versions() function now also reports the version of compression libraries used by Blosc.
Now the setup.py tries to use the ‘-march=native’ C flag by default. In falls back on ‘-msse2’ if ‘-march=native’ is not supported by the compiler. Closes gh-379.
Fixed a spurious unicode comparison warning (closes gh-372 and gh-373).
Improved handling of empty string attributes. In previous versions of PyTables empty string were stored as scalar HDF5 attributes having size 1 and value ‘0’ (an empty null terminated string). Now empty string are stored as HDF5 attributes having zero size
Added a new cookbook recipe and a couple of examples for simple threading with PyTables.
The redundant utilsextension.get_indices() function has been eliminated (replaced by slice.indices()). Closes gh-195.
Allow negative indices in point selection (closes gh-360)
Index wasn’t being used if it claimed there were no results. Closes gh-351 (see also gh-353)
Atoms and Col types are no longer generated dynamically so now it is easier for IDEs and static analysis tool to handle them (closes gh-345)
The keysort functions in idx-opt.c have been cythonised using fused types. The perfomance is mostly unchanged, but the code is much more simpler now. Thanks to Andrea Bedini.
Small unit tests re-factoring:
print_versions() and tests.common.print_heavy() functions
moved to the tests.common module
always use print_versions() when test modules are called as scripts
use the unittest2 package in Python 2.6.x
removed internal machinery used to replicate unittest2 features
always use tests.common.PyTablesTestCase as base class for all test cases
code of the old tasts.common.cleanup() function has been moved to tests.common.PyTablesTestCase.tearDown() method
new implementation of tests.common.PyTablesTestCase.assertWarns() compatible with the one provided by the standard unittest module in Python >= 3.2
use tests.common.PyTablesTestCase.assertWarns() as context manager when appropriate
use the unittest.skipIf() decorator when appropriate
new :class:tests.comon.TestFileMixin: class
Bugs fixed
Fixed compatibility problems with numpy 1.9 and 1.10-dev (closes gh-362 and gh-366)
Fixed compatibility with Cython >= 0.20 (closes gh-386 and gh-387)
Fixed support for unicode node names in LRU cache (only Python 2 was affected). Closes gh-367 and gh-369.
Fixed support for unicode node titles (only Python 2 was affected). Closes gh-370 and gh-374.
Fixed a bug that caused the silent truncation of unicode attributes containing the ‘0’ character. Closes gh-371.
Fixed descr_from_dtype() to work as expected with complex types. Closes gh-381.
Fixed the tests.test_basics.ThreadingTestCase test case. Closes gh-359.
Fix incomplete results when performing the same query twice and exhausting the second iterator before the first. The first one writes incomplete results to seqcache (gh-353)
Fix false results potentially going to seqcache if tableextension.Row.update() is used during iteration (see gh-353)
Fix Column.create_csindex() when there’s NaNs
Fixed handling of unicode file names on windows (closes gh-389)
No longer not modify sys.argv at import time (closes gh-405)
Fixed a performance issue on NFS (closes gh-402)
Fixed a nasty problem affecting results of indexed queries. Closes gh-319 and probably gh-419 too.
Fixed another problem affecting results of indexed queries too. Closes gh-441.
Replaced “len(xrange(start, stop, step))” -> “len(xrange(0, stop - start, step))” to fix issues with large row counts with Python 2.x. Fixes #447.
Other changes
Cython is not a hard dependency anymore (although developers will need it so as to generated the C extension code).
The number of threads used by default for numexpr and Blosc operation that was set to the number of available cores have been reduced to 2. This is a much more reasonable setting for not creating too much overhead.
jperkin
pushed a commit
that referenced
this issue
Aug 24, 2016
Add ALTERNATIVES file. 3.0.0 ===== **Incompatible changes** A number of incompatible changes were made in this release, with the intent of removing features deprecated for a long time or change existing behaviors in order to make them less surprising/more useful. * Reinterpretation mode has now been removed. Only plain and rewrite mode are available, consequently the ``--assert=reinterp`` option is no longer available. Thanks `@flub`_ for the PR. * The following deprecated commandline options were removed: * ``--genscript``: no longer supported; * ``--no-assert``: use ``--assert=plain`` instead; * ``--nomagic``: use ``--assert=plain`` instead; * ``--report``: use ``-r`` instead; Thanks to `@RedBeardCode`_ for the PR (`#1664`_). * ImportErrors in plugins now are a fatal error instead of issuing a pytest warning (`#1479`_). Thanks to `@The-Compiler`_ for the PR. * Removed support code for Python 3 versions < 3.3 (`#1627`_). * Removed all ``py.test-X*`` entry points. The versioned, suffixed entry points were never documented and a leftover from a pre-virtualenv era. These entry points also created broken entry points in wheels, so removing them also removes a source of confusion for users (`#1632`_). Thanks `@obestwalter`_ for the PR. * ``pytest.skip()`` now raises an error when used to decorate a test function, as opposed to its original intent (to imperatively skip a test inside a test function). Previously this usage would cause the entire module to be skipped (`#607`_). Thanks `@omarkohl`_ for the complete PR (`#1519`_). * Exit tests if a collection error occurs. A poll indicated most users will hit CTRL-C anyway as soon as they see collection errors, so pytest might as well make that the default behavior (`#1421`_). A ``--continue-on-collection-errors`` option has been added to restore the previous behaviour. Thanks `@olegpidsadnyi`_ and `@omarkohl`_ for the complete PR (`#1628`_). * Renamed the pytest ``pdb`` module (plugin) into ``debugging`` to avoid clashes with the builtin ``pdb`` module. * Raise a helpful failure message when requesting a parametrized fixture at runtime, e.g. with ``request.getfixturevalue``. Previously these parameters were simply never defined, so a fixture decorated like ``@pytest.fixture(params=[0, 1, 2])`` only ran once (`#460`_). Thanks to `@nikratio`_ for the bug report, `@RedBeardCode`_ and `@tomviner`_ for the PR. * ``_pytest.monkeypatch.monkeypatch`` class has been renamed to ``_pytest.monkeypatch.MonkeyPatch`` so it doesn't conflict with the ``monkeypatch`` fixture. * ``--exitfirst / -x`` can now be overridden by a following ``--maxfail=N`` and is just a synonym for ``--maxfail=1``. **New Features** * Support nose-style ``__test__`` attribute on methods of classes, including unittest-style Classes. If set to ``False``, the test will not be collected. * New ``doctest_namespace`` fixture for injecting names into the namespace in which doctests run. Thanks `@milliams`_ for the complete PR (`#1428`_). * New ``--doctest-report`` option available to change the output format of diffs when running (failing) doctests (implements `#1749`_). Thanks `@hartym`_ for the PR. * New ``name`` argument to ``pytest.fixture`` decorator which allows a custom name for a fixture (to solve the funcarg-shadowing-fixture problem). Thanks `@novas0x2a`_ for the complete PR (`#1444`_). * New ``approx()`` function for easily comparing floating-point numbers in tests. Thanks `@kalekundert`_ for the complete PR (`#1441`_). * Ability to add global properties in the final xunit output file by accessing the internal ``junitxml`` plugin (experimental). Thanks `@tareqalayan`_ for the complete PR `#1454`_). * New ``ExceptionInfo.match()`` method to match a regular expression on the string representation of an exception (`#372`_). Thanks `@omarkohl`_ for the complete PR (`#1502`_). * ``__tracebackhide__`` can now also be set to a callable which then can decide whether to filter the traceback based on the ``ExceptionInfo`` object passed to it. Thanks `@The-Compiler`_ for the complete PR (`#1526`_). * New ``pytest_make_parametrize_id(config, val)`` hook which can be used by plugins to provide friendly strings for custom types. Thanks `@palaviv`_ for the PR. * ``capsys`` and ``capfd`` now have a ``disabled()`` context-manager method, which can be used to temporarily disable capture within a test. Thanks `@nicoddemus`_ for the PR. * New cli flag ``--fixtures-per-test``: shows which fixtures are being used for each selected test item. Features doc strings of fixtures by default. Can also show where fixtures are defined if combined with ``-v``. Thanks `@hackebrot`_ for the PR. * Introduce ``pytest`` command as recommended entry point. Note that ``py.test`` still works and is not scheduled for removal. Closes proposal `#1629`_. Thanks `@obestwalter`_ and `@davehunt`_ for the complete PR (`#1633`_). * New cli flags: + ``--setup-plan``: performs normal collection and reports the potential setup and teardown and does not execute any fixtures and tests; + ``--setup-only``: performs normal collection, executes setup and teardown of fixtures and reports them; + ``--setup-show``: performs normal test execution and additionally shows setup and teardown of fixtures; + ``--keep-duplicates``: py.test now ignores duplicated paths given in the command line. To retain the previous behavior where the same test could be run multiple times by specifying it in the command-line multiple times, pass the ``--keep-duplicates`` argument (`#1609`_); Thanks `@d6e`_, `@kvas-it`_, `@sallner`_, `@ioggstream`_ and `@omarkohl`_ for the PRs. * New CLI flag ``--override-ini``/``-o``: overrides values from the ini file. For example: ``"-o xfail_strict=True"``'. Thanks `@blueyed`_ and `@fengxx`_ for the PR. * New hooks: + ``pytest_fixture_setup(fixturedef, request)``: executes fixture setup; + ``pytest_fixture_post_finalizer(fixturedef)``: called after the fixture's finalizer and has access to the fixture's result cache. Thanks `@d6e`_, `@sallner`_. * Issue warnings for asserts whose test is a tuple literal. Such asserts will never fail because tuples are always truthy and are usually a mistake (see `#1562`_). Thanks `@kvas-it`_, for the PR. * Allow passing a custom debugger class (e.g. ``--pdbcls=IPython.core.debugger:Pdb``). Thanks to `@anntzer`_ for the PR. **Changes** * Plugins now benefit from assertion rewriting. Thanks `@sober7`_, `@nicoddemus`_ and `@flub`_ for the PR. * Change ``report.outcome`` for ``xpassed`` tests to ``"passed"`` in non-strict mode and ``"failed"`` in strict mode. Thanks to `@hackebrot`_ for the PR (`#1795`_) and `@gprasad84`_ for report (`#1546`_). * Tests marked with ``xfail(strict=False)`` (the default) now appear in JUnitXML reports as passing tests instead of skipped. Thanks to `@hackebrot`_ for the PR (`#1795`_). * Highlight path of the file location in the error report to make it easier to copy/paste. Thanks `@suzaku`_ for the PR (`#1778`_). * Fixtures marked with ``@pytest.fixture`` can now use ``yield`` statements exactly like those marked with the ``@pytest.yield_fixture`` decorator. This change renders ``@pytest.yield_fixture`` deprecated and makes ``@pytest.fixture`` with ``yield`` statements the preferred way to write teardown code (`#1461`_). Thanks `@csaftoiu`_ for bringing this to attention and `@nicoddemus`_ for the PR. * Explicitly passed parametrize ids do not get escaped to ascii (`#1351`_). Thanks `@ceridwen`_ for the PR. * Fixtures are now sorted in the error message displayed when an unknown fixture is declared in a test function. Thanks `@nicoddemus`_ for the PR. * ``pytest_terminal_summary`` hook now receives the ``exitstatus`` of the test session as argument. Thanks `@blueyed`_ for the PR (`#1809`_). * Parametrize ids can accept ``None`` as specific test id, in which case the automatically generated id for that argument will be used. Thanks `@palaviv`_ for the complete PR (`#1468`_). * The parameter to xunit-style setup/teardown methods (``setup_method``, ``setup_module``, etc.) is now optional and may be omitted. Thanks `@okken`_ for bringing this to attention and `@nicoddemus`_ for the PR. * Improved automatic id generation selection in case of duplicate ids in parametrize. Thanks `@palaviv`_ for the complete PR (`#1474`_). * Now pytest warnings summary is shown up by default. Added a new flag ``--disable-pytest-warnings`` to explicitly disable the warnings summary (`#1668`_). * Make ImportError during collection more explicit by reminding the user to check the name of the test module/package(s) (`#1426`_). Thanks `@omarkohl`_ for the complete PR (`#1520`_). * Add ``build/`` and ``dist/`` to the default ``--norecursedirs`` list. Thanks `@mikofski`_ for the report and `@tomviner`_ for the PR (`#1544`_). * ``pytest.raises`` in the context manager form accepts a custom ``message`` to raise when no exception occurred. Thanks `@palaviv`_ for the complete PR (`#1616`_). * ``conftest.py`` files now benefit from assertion rewriting; previously it was only available for test modules. Thanks `@flub`_, `@sober7`_ and `@nicoddemus`_ for the PR (`#1619`_). * Text documents without any doctests no longer appear as "skipped". Thanks `@graingert`_ for reporting and providing a full PR (`#1580`_). * Ensure that a module within a namespace package can be found when it is specified on the command line together with the ``--pyargs`` option. Thanks to `@taschini`_ for the PR (`#1597`_). * Always include full assertion explanation during assertion rewriting. The previous behaviour was hiding sub-expressions that happened to be ``False``, assuming this was redundant information. Thanks `@bagerard`_ for reporting (`#1503`_). Thanks to `@davehunt`_ and `@tomviner`_ for the PR. * ``OptionGroup.addoption()`` now checks if option names were already added before, to make it easier to track down issues like `#1618`_. Before, you only got exceptions later from ``argparse`` library, giving no clue about the actual reason for double-added options. * ``yield``-based tests are considered deprecated and will be removed in pytest-4.0. Thanks `@nicoddemus`_ for the PR. * ``[pytest]`` sections in ``setup.cfg`` files should now be named ``[tool:pytest]`` to avoid conflicts with other distutils commands (see `#567`_). ``[pytest]`` sections in ``pytest.ini`` or ``tox.ini`` files are supported and unchanged. Thanks `@nicoddemus`_ for the PR. * Using ``pytest_funcarg__`` prefix to declare fixtures is considered deprecated and will be removed in pytest-4.0 (`#1684`_). Thanks `@nicoddemus`_ for the PR. * Raise helpful failure message, when requesting parametrized fixture at runtime, e.g. with ``request.getfuncargvalue``. BACKWARD INCOMPAT: Previously these params were simply never defined. So a fixture decorated like ``@pytest.fixture(params=[0, 1, 2])`` only ran once. Now a failure is raised. Fixes (`#460`_). Thanks to `@nikratio`_ for bug report, `@RedBeardCode`_ and `@tomviner`_ for the PR. * Passing a command-line string to ``pytest.main()`` is considered deprecated and scheduled for removal in pytest-4.0. It is recommended to pass a list of arguments instead (`#1723`_). * Rename ``getfuncargvalue`` to ``getfixturevalue``. ``getfuncargvalue`` is still present but is now considered deprecated. Thanks to `@RedBeardCode`_ and `@tomviner`_ for the PR (`#1626`_). * ``optparse`` type usage now triggers DeprecationWarnings (`#1740`_). * ``optparse`` backward compatibility supports float/complex types (`#457`_). * Refined logic for determining the ``rootdir``, considering only valid paths which fixes a number of issues: `#1594`_, `#1435`_ and `#1471`_. Thanks to `@blueyed`_ and `@davehunt`_ for the PR. * Always include full assertion explanation. The previous behaviour was hiding sub-expressions that happened to be False, assuming this was redundant information. Thanks `@bagerard`_ for reporting (`#1503`_). Thanks to `@davehunt`_ and `@tomviner`_ for PR. * Renamed the pytest ``pdb`` module (plugin) into ``debugging``. * Better message in case of not using parametrized variable (see `#1539`_). Thanks to `@tramwaj29`_ for the PR. * Updated docstrings with a more uniform style. * Add stderr write for ``pytest.exit(msg)`` during startup. Previously the message was never shown. Thanks `@BeyondEvil`_ for reporting `#1210`_. Thanks to `@JonathonSonesen`_ and `@tomviner`_ for the PR. * No longer display the incorrect test deselection reason (`#1372`_). Thanks `@ronnypfannschmidt`_ for the PR. * The ``--resultlog`` command line option has been deprecated: it is little used and there are more modern and better alternatives (see `#830`_). Thanks `@nicoddemus`_ for the PR. * Improve error message with fixture lookup errors: add an 'E' to the first line and '>' to the rest. Fixes `#717`_. Thanks `@blueyed`_ for reporting and a PR, `@eolo999`_ for the initial PR and `@tomviner`_ for his guidance during EuroPython2016 sprint. **Bug Fixes** * Parametrize now correctly handles duplicated test ids. * Fix internal error issue when the ``method`` argument is missing for ``teardown_method()`` (`#1605`_). * Fix exception visualization in case the current working directory (CWD) gets deleted during testing (`#1235`_). Thanks `@bukzor`_ for reporting. PR by `@marscher`_. * Improve test output for logical expression with brackets (`#925`_). Thanks `@DRMacIver`_ for reporting and `@RedBeardCode`_ for the PR. * Create correct diff for strings ending with newlines (`#1553`_). Thanks `@Vogtinator`_ for reporting and `@RedBeardCode`_ and `@tomviner`_ for the PR. * ``ConftestImportFailure`` now shows the traceback making it easier to identify bugs in ``conftest.py`` files (`#1516`_). Thanks `@txomon`_ for the PR. * Add an 'E' to the first line of error messages from FixtureLookupErrorRepr. Fixes `#717`_. Thanks `@blueyed`_ for reporting, `@eolo999`_ for the PR and `@tomviner`_ for his guidance during EuroPython2016 sprint. * Text documents without any doctests no longer appear as "skipped". Thanks `@graingert`_ for reporting and providing a full PR (`#1580`_). * Fixed collection of classes with custom ``__new__`` method. Fixes `#1579`_. Thanks to `@Stranger6667`_ for the PR. * Fixed scope overriding inside metafunc.parametrize (`#634`_). Thanks to `@Stranger6667`_ for the PR. * Fixed the total tests tally in junit xml output (`#1798`_). Thanks to `@cryporchild`_ for the PR. * Fixed off-by-one error with lines from ``request.node.warn``. Thanks to `@blueyed`_ for the PR.
jperkin
pushed a commit
that referenced
this issue
Oct 22, 2016
version 1.11.1: 2016-06-14
* new guesser infrastructure, support for emacs and vim modelines (#489)
* javascript bugfix for nested objects with quoted keys (#496)
* new theme: Gruvbox (thanks @jamietanna!)
* praat: lots of improvements (thanks @jjatria)
* fix for rougify error when highlighting from stdin (#493)
* new lexer: kotlin (thanks @meleyal!)
* new lexer: cfscript (thanks @mjclemente!)
version 1.11.0: 2016-06-06
* groovy:
o remove pathological regexes and add basic support for
triple-quoted strings (#485)
o add the "trait" keyword and fix project url (thanks @glaforge! #378)
* new lexer: coq (thanks @gmalecha! #389)
* gemspec license now more accurate (thanks @connorshea! #484)
* swift:
o properly support nested comments (thanks @dblessing! #479)
o support swift 2.2 features (thanks @radex #376 and @wokalski #442)
o add indirect declaration (thanks @nRewik! #326)
* new lexer: verilog (thanks @Razer6! #317)
* new lexer: typescript (thanks @Seikho! #400)
* new lexers: jinja and twig (thanks @robin850! #402)
* new lexer: pascal (thanks @alexcu!)
* css: support attribute selectors (thanks @skoji! #426)
* new lexer: shell session (thanks @sio4! #481)
* ruby: add support for <<~ heredocs (thanks @tinci! #362)
* recognize comments at EOF in SQL, Apache, and CMake (thanks @julp! #360)
* new lexer: phtml (thanks @Igloczek #366)
* recognize comments at EOF in CoffeeScript (thanks @rdavila! #370)
* c/c++:
o support c11/c++11 features (thanks @Tosainu! #371)
o Allow underscores in identifiers (thanks @coverify! #333)
* rust: add more builtin types (thanks @RalfJung! #372)
* ini: allow hyphen keys (thanks @KrzysiekJ! #380)
* r: massively improve lexing quality (thanks @klmr! #383)
* c#:
o add missing keywords (thanks @BenVlodgi #384 and @SLaks #447)
* diff: do not require newlines at the ends (thanks @AaronLasseigne! #387)
* new lexer: ceylon (thanks @bjansen! #414)
* new lexer: biml (thanks @japj! #415)
* new lexer: TAP - the test anything protocol (thanks @mblayman! #409)
* rougify bugfix: treat input as utf8 (thanks @japj! #417)
* new lexer: jsonnet (thanks @davidzchen! #420)
* clojure: associate *.cljc for cross-platform clojure (thanks @alesguzik! #423)
* new lexer: D (thanks @nikibobi! #435)
* new lexer: smarty (thanks @tringenbach! #427)
* apache:
o add directives for v2.4 (thanks @stanhu!)
o various improvements (thanks @julp! #301)
- faster keyword lookups
- fix nil error on unknown directive (cf #246, #300)
- properly manage case-insensitive names (cf #246)
- properly handle windows CRLF
* objective-c:
o support literal dictionaries and block arguments (thanks @BenV!
#443 and #444)
o Fix error tokens when defining interfaces (thanks @meleyal! #477)
* new lexer: NASM (thanks @sraboy! #457)
* new lexer: gradle (thanks @nerro! #468)
* new lexer: API Blueprint (thanks @kylef! #261)
* new lexer: ActionScript (thanks @honzabrecka! #241)
* terminal256 formatter: stop confusing token names (thanks @julp! #367)
* new lexer: julia (thanks @mpeteuil! #331)
* new lexer: cmake (thanks @julp! #302)
* new lexer: eiffel (thanks @Conaclos! #323)
* new lexer: protobuf (thanks @fqqb! #327)
* new lexer: fortran (thanks @CruzR! #328)
* php: associate *.phpt files (thanks @Razer6!)
* python: support raise from and yield from (thanks @mordervomubel! #324)
* new VimL example (thanks @tpope! #315)
jperkin
pushed a commit
that referenced
this issue
Oct 22, 2016
3.5.3 - 2016-10-05
This is a bug fix release.
Bugs fixed:
If the same test was running concurrently in two processes and there were examples already in the test database which no longer failed, Hypothesis would sometimes fail with a FileNotFoundError (IOError on Python 2) because an example it was trying to read was deleted before it was read. (Issue #372).
Drawing from an integers() strategy with both a min_value and a max_value would reject too many examples needlessly. Now it repeatedly redraws until satisfied. (Pull request #366. Thanks to Calen Pennington for the contribution).
3.5.2 - 2016-09-24
This is a bug fix release.
The Hypothesis pytest plugin broke pytest support for doctests. Now it doesn’t.
3.5.1 - 2016-09-23
This is a bug fix release.
Hypothesis now runs cleanly in -B and -BB modes, avoiding mixing bytes and unicode.
unittest.TestCase tests would now have shown up in the new statistics mode. Now they do.
Similarly, stateful tests would not have shown up in statistics and now they do.
Statistics now print with pytest node IDs (the names you’d get in pytest verbose mode).
3.5.0 - 2016-09-22
This is a feature release.
fractions() and decimals() strategies now support min_value and max_value parameters. Thanks go to Anne Mulhern for the development of this feature.
The Hypothesis pytest plugin now supports a –hypothesis-show-statistics parameter that gives detailed statistics about the tests that were run. Huge thanks to Jean-Louis Fuchs and Adfinis-SyGroup for funding the development of this feature.
There is a new event() function that can be used to add custom statistics.
Additionally there have been some minor bug fixes:
In some cases Hypothesis should produce fewer duplicate examples (this will mostly only affect cases with a single parameter).
py.test command line parameters are now under an option group for Hypothesis (thanks to David Keijser for fixing this)
Hypothesis would previously error if you used function annotations on your tests under Python 3.4.
The repr of many strategies using lambdas has been improved to include the lambda body (this was previously supported in many but not all cases).
jperkin
pushed a commit
that referenced
this issue
Oct 22, 2016
Restrict to ruby22 and ruby23.
v3.1.5
Bugfixes
* #394 prevent crashes when Listen is stopped too soon (e.g. before
being started or initialized)
v3.1.4
Bugfixes
* #393 - relaxed rb-fsevent dependency to allow install on older OSX
releases (thanks to @robmckinnon)
v3.1.3
Bug fixes
* #387 - fix JRuby support both in dependencies (by allowing Ruby 2.2.3)
and behavior (JRuby Dir.entries workaround)
* #387 - prevent JRuby from hanging when stopping on Linux (and Travis)
* #387 - activate JRuby-9.0.5.0 on Travis to declare support for JRuby
(tests are flaky, but that's due to timing issues)
v3.1.2
Security enhancements
* #377 require at least Ruby 2.2.4 to avoid CVE-2015-7551 (see
https://www.ruby-lang.org/en/news/2015/12/16/ruby-2-2-4-released/)
Bugfixes
* #383 allow stopping when not fully initialized (fixes guard/guard#822
(comment))
Improvements
* #378 warn users if their Ruby is buggy or vulnerable (controversial to
some, but very extensively justified)
Development
* #377 use ruby_dep for managing ruby requirements
* #379 make RuboCop pass (thanks to @jvanbaarsen)
* #384 avoid rubygems duplicate dependency error (gem given in both
runtime and development dependencies)
v3.1.1
Bugfixes
* #373 explicitly require forwardable for delegation (fixes #372)
v3.1.0
Bugfixes
* #370 - gracefully fallback to polling on old older unsupported OSX
versions (thanks to @vaz)
Improvements
* #371 - update dependency to Ruby 2.2.x since 2.1 and earlier are EOL
(minor version bumped to 3.1 in case backporting is needed)
Development
* #371 - fix all RuboCop offenses to avoid noise during development
jperkin
pushed a commit
that referenced
this issue
Mar 20, 2017
kramdown 1.13.2 released 2017/01/07 This release fixes some minor issues - updating is recommended. Changes 3 bug fixes: * Fix footnote link spacing to use non-breaking space (pull request #399 by Martyn Chamberlin) * Show warning for unreferenced footnote definitions (fixes #400 reported by Kyle Barbour) * Fix test cases with respect to Ruby 2.4 (fixes #401 reported by Connor Shea) kramdown 1.13.1 released 2016/11/25 This release fixes the GFM header ID generation for more cases, updating is very recommended. Changes 1 bug fix: * Fix GFM header ID generation when code spans, math elements, entities, typographic symbols or smart quotes are used (fixes #391 reported by Nick Fagerlund) kramdown 1.13.0 released 2016/11/20 The biggest change in this release is the introduction of a converter for man pages. Although there already exist two solutions (ronn and kramdown-man), both are not completely satisfactory: * Ronn doesn't use standard Markdown syntax for all elements. * kramdown-man only converts a subset of the available element types. The new man page converter uses standard kramdown syntax and supports nearly all element types, including tables. This release also brings some enhancements for the GFM parser. One thing to note is that the header ID generation is now more compatible to GFM which also means that some IDs will be different - so check the documents on which you use the GFM parser, especially when you are using Jekyll or Github Pages. Organizational-wise, issues and pull requests on Github that pertain to feature requests have been closed and are now tracked through a dedicated kramdown project on Github. Changes 4 minor changes: * Add new converter for man pages * Header ID generation for the GFM parser is now more compatible to GFM (fixes #267, requested by chadpowers) * Update to the MathJax math engine to allow formatting the preview as code / pre > code (pull request #372 by Florian Klampfer) * Allow tabs in table separator lines (pull request #370 by Shuanglei Tao) 2 bug fixes: * Compactly nested lists are now handled correctly after fixing a bug in indentation detection (fixes #368 reported by Christopher Brown) * GFM parser: Allow indenting the delimiting lines of fenced code blocks for better GFM compatibility (pull request #369 by Shuanglei Tao) 2 other fixes and enhancements: * Added information on how to run tests to README.md (fixes #377 reported by Aron Griffis) * Added information about how to use KaTeX with the MathJax math engine (fixes #292 reported by Adrian Sieber, information by Dato Sim�«Ñ)
jperkin
pushed a commit
that referenced
this issue
Apr 27, 2017
## [1.13.1][] (2017-03-31) ### Breaking changes * None ### Bug fixes * [#397](https://github.com/capistrano/sshkt/pull/397): Fix NoMethodError assign_defaults with net-ssh older than 4.0.0 - [@shirosaki](https://github.com/shirosaki) ## [1.13.0][] (2017-03-24) ### Breaking changes * None ### New features * [#372](capistrano/sshkit#372): Use cp_r in local backend with recursive option - [@okuramasafumi](https://github.com/okuramasafumi) ### Bug fixes * [#390](capistrano/sshkit#390): Properly wrap Ruby StandardError w/ add'l context - [@mattbrictson](https://github.com/mattbrictson) * [#392](capistrano/sshkit#392): Fix open two connections with changed cache key - [@shirosaki](https://github.com/shirosaki)
wiedi
pushed a commit
to wiedi/pkgsrc-legacy
that referenced
this issue
Jan 28, 2018
pkgsrc changes:
- switch to using qt5 (to follow upstream)
- handle ${PREFIX} in more places
- fix package COMMENT (remove "for IBus")
- GCC_REQD 4.7 for c++11
- add patch comments
See PR pkg/52689 for more details.
Upstream changes:
(from https://github.com/google/mozc/blob/master/docs/release_history.md)
Summary of changes between 2.19.2644.102 and 2.20.2673.102 as follows.
Third party libraries:
None.
Build related changes:
--qtver GYP build option was removed (280e38f).
Mozc for macOS now uses macOS 10.11 SDK by default (b2a74bb).
Major changes:
src/data/installer/credits_ja.html was removed (2ec6c8f).
Mozc for macOS now generates 64-bit executables. 32-bit machine is no longer supported on macOS.
Mozc for Android now has more translations (d914458).
Fixed issues:
TritonDataCenter#187: build_mozc.py always generates 32 bit binaries on 64 bit OSX
TritonDataCenter#327: Switch to Qt5 from Qt4
TritonDataCenter#348: DirectWrite may fail to render text in certain enviromnents
TritonDataCenter#391: ImportError: gen_zip_code_seed.py
TritonDataCenter#399: OK/Cancel buttons on Mozc key binding editor dialog cannot be clicked on Windows
TritonDataCenter#400: Close icon on GUI dialogs do not work on Windows
Total commits:
30 commits.
Summary of changes between 2.18.2613.102 and 2.19.2643.102 as follows.
Third party libraries:
protobuf: e8ae137 -> c44ca26
Dropped dependency on fonttools
Build related changes:
--qtver=5 GYP build option is implicitly assumed on macOS and Linux builds (f76c304). On Windows, --qtver=4 is still the default.
Major changes:
Mozc for macOS now supports 10.12 as a runtime environment.
Mozc for Android now uses on-device font to render keytop icons (f5dcad).
Fixed issues:
TritonDataCenter#263: Incorrect position in voiced sound marks on the key pad in Android
TritonDataCenter#384: HUAWEI P9 lite does not show MozcView.
TritonDataCenter#388: Having multiple abbreviation user dictionary entries with the same reading should be supported
TritonDataCenter#389: Emoticon user dictionary entry should not be treated a content word
Total commits:
39 commits.
Summary of changes between 2.17.2532.102 and 2.18.2612.102 as follows.
Third party libraries:
protobuf: d5fb408 -> e8ae137
GYP: e2e928b -> 4ec6c4e
breakpad: d2904bb -> 85b27e4
Dropped dependency on zlib
Build related changes:
Renamed src/mozc_version_template.txt to src/data/version/mozc_version_template.bzl
Reference build environment now uses Ubuntu 14.04.5 (a7cbf72)
Reference build environment now uses Ninja 1.7.1 (d2bc62b)
Removed --android_compiler GYP option (5ce7fa6)
Android build requires Android NDK r12b (5ce7fa6)
Major changes:
Improved Store Apps compatibility on Windows (0488082)
Fixed issues:
NPE in UserDictionaryToolActivity.onPostResume on Android (09b47c3)
TritonDataCenter#273: Compilation errors in Android arm64 and mips64 build
TritonDataCenter#373: Unexpected size bloat of the APK
TritonDataCenter#374: Duplicate candidates after Undo
TritonDataCenter#375: 90- is suggested from 090-
TritonDataCenter#376: Suggestion-only user dictionary entry may not work
TritonDataCenter#377: Abbreviation user dictionary entry may not work
TritonDataCenter#378: Suppression word may not work
TritonDataCenter#379: Single character noun user dictionary entry may not work
TritonDataCenter#380: Dependency on dictionary/pos_matcher.h from session/session_server.cc is missing in GYP rules
TritonDataCenter#382: Fix typo
Total commits:
84 commits.
Summary of changes between 2.17.2405.102 and 2.17.2531.102 as follows.
Third party libraries:
protobuf: 1a59a71 -> d5fb408
Build related changes:
Building Mozc for Windows requires Visual Studio 2015 update 3.
--qtdir option is no longer supported in Linux desktop build (d003076).
Major changes:
Updated system dictionary.
Removed several Shift-JIS-based normalizations on Windows (26241b0).
Mozc for Windows requires SSE2 even on 32-bit environment.
Mozc for Windows supports Windows 7 SP1 and later only.
Mozc for macOS supports macOS 10.9 and later only.
Mozc for desktop platforms (Windows, macOS, desktop Linux) supports Qt5 behind --qtver=5 GYP option.
Fixed issues:
Fix OOM when importing too large dictionary file on Android (5c859ae)
TritonDataCenter#298: Fix NPE on Samsung devices on showing toast
TritonDataCenter#315: Switch to Visual C++ 2015
TritonDataCenter#372: Discontinue the support of Windows Vista
Total commits:
128 commits.
Summary of changes between 2.17.2355.102 and 2.17.2404.102 as follows.
Third party libraries:
protobuf: 172019c -> 1a59a71
Build related changes:
Building Mozc requires protobuf 3.0 or later.
--android_stl GYP option is removed in Android build. You cannot use GNU STL to build Mozc for Android anymore.
Major changes:
None.
Fixed issues:
TritonDataCenter#369: Unexpected software keyboard layout can be chosen
TritonDataCenter#370: Mozc keeps crashing on Android N Developer Preview 5
TritonDataCenter#371: Shortcut word in personal dictionary should not be used for multi segment conversion
Total commits:
50 commits.
Summary of changes between 2.17.2323.102 and 2.17.2354.102 as follows.
Third party libraries:
None.
Build related changes:
None.
Major changes:
2.17.2323.102 and later commits in OSS repository preserve the original CL commit date in Google internal repository.
Consider to specify --topo-order option to git log to see commits in the actual commit order.
Multiple performance improvements in Android.
Fixed issues:
None.
Total commits:
32 commits.
Summary of changes between 2.17.2314.102 and 2.17.2322.102 as follows.
Third party libraries:
googletest: 1d53731 -> 82b11b8
WTL: 9.0.4140 -> 9.1.5321
Build related changes:
Building macOS binaries now requires Ninja instead of xcodebuild.
Major changes:
None.
Fixed issues:
TritonDataCenter#247: Use ninja to build Mac binaries
TritonDataCenter#355: Native resource leak due to the missing pthread_detach call in mozc::Thread::Detach
TritonDataCenter#361: ImmSetCandidateWindow() with CFS_EXCLUDE isn't supported on Win Vista and Win7
Total commits:
15 commits.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ikiwiki package seems to be missing in the OS X version of pkgsrc. Output of
pkgin search ikiwiki:I'm using pkgsrc-2016Q1 (after updating; btw. how would I get pkgin print out the currently used version?) and have still ikiwiki-3.20150614 installed.
I'm on OS X 10.11.4
The text was updated successfully, but these errors were encountered: