head 1.25; access; symbols pkgsrc-2023Q4:1.23.0.2 pkgsrc-2023Q4-base:1.23 pkgsrc-2023Q3:1.21.0.2 pkgsrc-2023Q3-base:1.21 pkgsrc-2023Q2:1.19.0.6 pkgsrc-2023Q2-base:1.19 pkgsrc-2023Q1:1.19.0.4 pkgsrc-2023Q1-base:1.19 pkgsrc-2022Q4:1.19.0.2 pkgsrc-2022Q4-base:1.19 pkgsrc-2022Q3:1.16.0.2 pkgsrc-2022Q3-base:1.16 pkgsrc-2022Q2:1.12.0.2 pkgsrc-2022Q2-base:1.12 pkgsrc-2022Q1:1.10.0.4 pkgsrc-2022Q1-base:1.10 pkgsrc-2021Q4:1.10.0.2 pkgsrc-2021Q4-base:1.10 pkgsrc-2021Q3:1.8.0.16 pkgsrc-2021Q3-base:1.8 pkgsrc-2021Q2:1.8.0.14 pkgsrc-2021Q2-base:1.8 pkgsrc-2021Q1:1.8.0.12 pkgsrc-2021Q1-base:1.8 pkgsrc-2020Q4:1.8.0.10 pkgsrc-2020Q4-base:1.8 pkgsrc-2020Q3:1.8.0.8 pkgsrc-2020Q3-base:1.8 pkgsrc-2020Q2:1.8.0.6 pkgsrc-2020Q2-base:1.8 pkgsrc-2020Q1:1.8.0.2 pkgsrc-2020Q1-base:1.8 pkgsrc-2019Q4:1.8.0.4 pkgsrc-2019Q4-base:1.8 pkgsrc-2019Q3:1.6.0.2 pkgsrc-2019Q3-base:1.6 pkgsrc-2019Q2:1.5.0.4 pkgsrc-2019Q2-base:1.5 pkgsrc-2019Q1:1.5.0.2 pkgsrc-2019Q1-base:1.5 pkgsrc-2018Q4:1.4.0.16 pkgsrc-2018Q4-base:1.4 pkgsrc-2018Q3:1.4.0.14 pkgsrc-2018Q3-base:1.4 pkgsrc-2018Q2:1.4.0.12 pkgsrc-2018Q2-base:1.4 pkgsrc-2018Q1:1.4.0.10 pkgsrc-2018Q1-base:1.4 pkgsrc-2017Q4:1.4.0.8 pkgsrc-2017Q4-base:1.4 pkgsrc-2017Q3:1.4.0.6 pkgsrc-2017Q3-base:1.4 pkgsrc-2017Q2:1.4.0.2 pkgsrc-2017Q2-base:1.4 pkgsrc-2017Q1:1.3.0.4 pkgsrc-2017Q1-base:1.3 pkgsrc-2016Q4:1.3.0.2 pkgsrc-2016Q4-base:1.3 pkgsrc-2016Q3:1.2.0.8 pkgsrc-2016Q3-base:1.2 pkgsrc-2016Q2:1.2.0.6 pkgsrc-2016Q2-base:1.2 pkgsrc-2016Q1:1.2.0.4 pkgsrc-2016Q1-base:1.2 pkgsrc-2015Q4:1.2.0.2 pkgsrc-2015Q4-base:1.2 pkgsrc-2015Q3:1.1.0.6 pkgsrc-2015Q3-base:1.1 pkgsrc-2015Q2:1.1.0.4 pkgsrc-2015Q2-base:1.1 pkgsrc-2015Q1:1.1.0.2 pkgsrc-2015Q1-base:1.1; locks; strict; comment @# @; 1.25 date 2024.01.20.08.01.49; author adam; state Exp; branches; next 1.24; commitid 5UXEkl06GjPo5aVE; 1.24 date 2024.01.16.18.18.35; author adam; state Exp; branches; next 1.23; commitid HvU0ECiUQV3XCHUE; 1.23 date 2023.11.27.15.37.10; author adam; state Exp; branches; next 1.22; commitid KsXtIC8zODwelgOE; 1.22 date 2023.11.02.11.01.10; author adam; state Exp; branches; next 1.21; commitid ZoSE4benWnknC1LE; 1.21 date 2023.09.20.16.45.52; author adam; state Exp; branches; next 1.20; commitid foPk9xaIliekUwFE; 1.20 date 2023.08.25.21.35.08; author adam; state Exp; branches; next 1.19; commitid InhKYvksGz6fldCE; 1.19 date 2022.12.19.08.22.10; author adam; state Exp; branches; next 1.18; commitid byWG4jd7jhHxX86E; 1.18 date 2022.11.27.12.09.29; author adam; state Exp; branches; next 1.17; commitid BTGNFkfudqBoVk3E; 1.17 date 2022.11.21.20.06.08; author adam; state Exp; branches; next 1.16; commitid MBmiF8FXmFaQKB2E; 1.16 date 2022.09.14.11.04.57; author adam; state Exp; branches; next 1.15; commitid AWf0pjPbBvOHWOTD; 1.15 date 2022.09.05.14.14.17; author adam; state Exp; branches; next 1.14; commitid GpoXdjPtcX8jhGSD; 1.14 date 2022.07.08.07.54.06; author adam; state Exp; branches; next 1.13; commitid NNOdw5oUZUzL44LD; 1.13 date 2022.07.07.10.41.40; author adam; state Exp; branches; next 1.12; commitid OKZSGWAri2Jc2XKD; 1.12 date 2022.05.11.09.30.52; author adam; state Exp; branches; next 1.11; commitid 90SspW9ftHPwtCDD; 1.11 date 2022.04.07.06.49.20; author adam; state Exp; branches; next 1.10; commitid AwVhTay1QixIFezD; 1.10 date 2021.10.26.11.23.06; author nia; state Exp; branches; next 1.9; commitid TS3y6sgAeGKWpjeD; 1.9 date 2021.10.07.15.02.13; author nia; state Exp; branches; next 1.8; commitid 0fS32tEWoNe7fTbD; 1.8 date 2019.12.03.16.50.59; author adam; state Exp; branches; next 1.7; commitid iidKO1CKjuacwhNB; 1.7 date 2019.10.19.14.32.09; author adam; state Exp; branches; next 1.6; commitid logGJ10HiwGgcuHB; 1.6 date 2019.08.22.11.47.04; author adam; state Exp; branches; next 1.5; commitid IiSe05CiKAib91AB; 1.5 date 2019.03.02.14.31.51; author adam; state Exp; branches; next 1.4; commitid ITWlXKjewPyuCNdB; 1.4 date 2017.05.04.17.46.53; author adam; state Exp; branches; next 1.3; commitid mYUgAA70wYHF86Qz; 1.3 date 2016.10.09.21.30.58; author bsiegert; state Exp; branches; next 1.2; commitid kKb2sTiLrQoV1wpz; 1.2 date 2015.11.04.02.00.03; author agc; state Exp; branches; next 1.1; commitid 8Vi0UoG7obKytIHy; 1.1 date 2014.12.31.13.18.58; author bsiegert; state Exp; branches; next ; commitid Qr4HuFN063fD8c4y; desc @@ 1.25 log @py-jsonschema: updated to 4.21.1 v4.21.1 * Slightly speed up the ``contains`` keyword by removing some unnecessary validator (re-)creation. @ text @$NetBSD: distinfo,v 1.24 2024/01/16 18:18:35 adam Exp $ BLAKE2s (jsonschema-4.21.1.tar.gz) = 880e93ec15e016a72c129270dca5ccd158b24b3bf50a09029d1674cf33e911c3 SHA512 (jsonschema-4.21.1.tar.gz) = b0744a80d64572307860c9238ff5048e062b7665d9ed97dd390bae0b168ab96497f359ddc4e95f052d8b177161e5b808ee432bd9fe182c1ea39cbad417db9278 Size (jsonschema-4.21.1.tar.gz) = 321491 bytes @ 1.24 log @py-jsonschema: updated to 4.21.0 v4.21.0 * Fix the behavior of ``enum`` in the presence of ``0`` or ``1`` to properly consider ``True`` and ``False`` unequal. * Special case the error message for ``{min,max}{Items,Length,Properties}`` when they're checking for emptiness rather than true length. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.23 2023/11/27 15:37:10 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.21.0.tar.gz) = 3fd33c5d14d7770cd0d904e1edb0e59a4b0b0d8ec54f116b899fb62f8725eeab SHA512 (jsonschema-4.21.0.tar.gz) = 7467a1c70e587d32c2d196050b60f01a765a27ac0c97f4481c2c654381863911999e7b8f7592ec6ce24a92fb81f4de4ce5197652977a82ace5b75928a6c2334c Size (jsonschema-4.21.0.tar.gz) = 321324 bytes @ 1.23 log @py-jsonschema: updated to 4.20.0 v4.20.0 * Properly consider items (and properties) to be evaluated by ``unevaluatedItems`` (resp. ``unevaluatedProperties``) when behind a ``$dynamicRef`` as specified by the 2020 and 2019 specifications. * ``jsonschema.exceptions.ErrorTree.__setitem__`` is now deprecated. More broadly, in general users of ``jsonschema`` should never be mutating objects owned by the library. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.22 2023/11/02 11:01:10 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.20.0.tar.gz) = d7bc2421b7b4513538765ba99e2b861bf652b1d9d8152b5fc9c27b6cfc0b44af SHA512 (jsonschema-4.20.0.tar.gz) = 916ce6e5a1cce19e52d34394797d59c4821a3e7abad0248d929a8d5975e8e5a2c0a270b2839d6e1800037a53d0ed8fd38ca44264a88653b5aaba1705d459cb47 Size (jsonschema-4.20.0.tar.gz) = 320243 bytes @ 1.22 log @py-jsonschema: updated to 4.19.2 v4.19.2 * Fix the error message for additional items when used with heterogeneous arrays. * Don't leak the ``additionalItems`` keyword into JSON Schema draft 2020-12, where it was replaced by ``items``. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.21 2023/09/20 16:45:52 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.19.2.tar.gz) = e90207185abafa7354cf10f56cfc37d7bb716aa9906cf4481be1c2b8290bef71 SHA512 (jsonschema-4.19.2.tar.gz) = 0820f0e6417cceb1017efe9b8fed6e386acbb194e786c97c89a94f173c22a8dfa8144f19ae46cbf44cb3d2b78b27d4631344e13e964d82d9810a513d328a95a0 Size (jsonschema-4.19.2.tar.gz) = 318786 bytes @ 1.21 log @py-jsonschema: updated to 4.19.1 v4.19.1 * Single label hostnames are now properly considered valid according to the ``hostname`` format. This is the behavior specified by the relevant RFC (1123). IDN hostname behavior was already correct. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.20 2023/08/25 21:35:08 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.19.1.tar.gz) = cf8f676b8c8cbb5f0fc656b40d7345edbfeac73cdd58debde7e619773b7efd5e SHA512 (jsonschema-4.19.1.tar.gz) = 60fa769faf6e3fc2c14eb9acd189c86e9d366b157230a5681d36552af0c159cb1ad33fd920668a36afdab98bc97253f91501704c5c07b5009fdaf9d29b52060d Size (jsonschema-4.19.1.tar.gz) = 318089 bytes @ 1.20 log @py-jsonschema: updated to 4.19.0 v4.19.0 ======= * Importing the ``Validator`` protocol directly from the package root is deprecated. Import it from ``jsonschema.protocols.Validator`` instead. * Automatic retrieval of remote references (which is still deprecated) now properly succeeds even if the retrieved resource does not declare which version of JSON Schema it uses. Such resources are assumed to be 2020-12 schemas. This more closely matches the pre-referencing library behavior. v4.18.6 ======= * Set a ``jsonschema`` specific user agent when automatically retrieving remote references (which is deprecated). v4.18.5 ======= * Declare support for Py3.12 v4.18.4 ======= * Improve the hashability of wrapped referencing exceptions when they contain hashable data. v4.18.3 ======= * Properly preserve ``applicable_validators`` in extended validators. Specifically, validators extending early drafts where siblings of ``$ref`` were ignored will properly ignore siblings in the extended validator. v4.18.2 ======= * Fix an additional regression with the deprecated ``jsonschema.RefResolver`` and pointer resolution. v4.18.1 ======= * Fix a regression with ``jsonschema.RefResolver`` based resolution when used in combination with a custom validation dialect (via ``jsonschema.validators.create``). v4.18.0 ======= This release majorly rehauls the way in which JSON Schema reference resolution is configured. It does so in a way that *should* be backwards compatible, preserving old behavior whilst emitting deprecation warnings. * ``jsonschema.RefResolver`` is now deprecated in favor of the new `referencing library `_. ``referencing`` will begin in beta, but already is more compliant than the existing ``$ref`` support. This change is a culmination of a meaningful chunk of work to make ``$ref`` resolution more flexible and more correct. Backwards compatibility *should* be preserved for existing code which uses ``RefResolver``, though doing so is again now deprecated, and all such use cases should be doable using the new APIs. Please file issues on the ``referencing`` tracker if there is functionality missing from it, or here on the ``jsonschema`` issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to use ``referencing``. In particular, this referencing change includes a change concerning *automatic* retrieval of remote references (retrieving ``http://foo/bar`` automatically within a schema). This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings. The ``referencing`` library itself will *not* automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default ``$ref`` resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error). * Support for Python 3.7 has been dropped, as it is nearing end-of-life. This should not be a "visible" change in the sense that ``requires-python`` has been updated, so users using 3.7 should still receive ``v4.17.3`` when installing the library. * On draft 2019-09, ``unevaluatedItems`` now properly does *not* consider items to be evaluated by an ``additionalItems`` schema if ``items`` is missing from the schema, as the specification says in this case that ``additionalItems`` must be completely ignored. * Fix the ``date`` format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal * Speed up validation of ``unevaluatedProperties`` Deprecations ------------ * ``jsonschema.RefResolver`` -- see above for details on the replacement * ``jsonschema.RefResolutionError`` -- see above for details on the replacement * relying on automatic resolution of remote references -- see above for details on the replacement * importing ``jsonschema.ErrorTree`` -- instead import it via ``jsonschema.exceptions.ErrorTree`` * importing ``jsonschema.FormatError`` -- instead import it via ``jsonschema.exceptions.FormatError`` @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.19 2022/12/19 08:22:10 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.19.0.tar.gz) = c62cf4c7db04f7684bab1c59bb7d31a840dd0bec3fcb646021abd597a32f7331 SHA512 (jsonschema-4.19.0.tar.gz) = 95cc156fe0505da469600cdbaaf921853a983d45f6b8570e5bbffe9ee41abbf5757b2ccddde443b0d833a3ebdcbff321bda54b136b47d7650d3a40f6402338fb Size (jsonschema-4.19.0.tar.gz) = 317546 bytes @ 1.19 log @py-jsonschema: updated to 4.17.3 v4.17.3 ======= * Fix instantiating validators with cached refs to boolean schemas rather than objects. v4.17.2 ======= * Empty strings are not valid relative JSON Pointers (aren't valid under the RJP format). * Durations without (trailing) units are not valid durations (aren't valid under the duration format). This involves changing the dependency used for validating durations (from ``isoduration`` to ``isodate``). @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.18 2022/11/27 12:09:29 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.17.3.tar.gz) = 008614470694f7bf3dc4b69cf624cee5f3eb79ab4a3c3997983f61d49e52746a SHA512 (jsonschema-4.17.3.tar.gz) = 626fc913c37d2e49e4b47c9e058aab4a96c1dc50c35d8def0b2ea0ca464dc25e3318d4fde4927c11ca38068743cd81779d5189464b821407ac1de1788bad30e2 Size (jsonschema-4.17.3.tar.gz) = 297785 bytes @ 1.18 log @py-jsonschema: updated to 4.17.1 v4.17.1 ======= * The error message when using ``unevaluatedProperties`` with a non-trivial schema value (i.e. something other than ``false``) has been improved @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.17 2022/11/21 20:06:08 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.17.1.tar.gz) = c8081541768185cda43f85c8686b2d9f6baced0d1973b2d230233c4276eb9d9c SHA512 (jsonschema-4.17.1.tar.gz) = 5d184ea60cf313c9fa6a3e1c2891432531aa7a25a5aced8e51aac46eb67fe7fd17bc9d141faa3e52a834f9067556225cfd3a592d80867b543f0dea42983e5d04 Size (jsonschema-4.17.1.tar.gz) = 296586 bytes @ 1.17 log @py-jsonschema: updated to 4.17.0 v4.17.0 ======= * The ``check_schema`` method on ``jsonschema.protocols.Validator`` instances now *enables* format validation by default when run. This can catch some additional invalid schemas (e.g. containing invalid regular expressions) where the issue is indeed uncovered by validating against the metaschema with format validation enabled as an assertion. * The ``jsonschema`` CLI (along with ``jsonschema.cli`` the module) are now deprecated. Use ``check-jsonschema`` instead, which can be installed via ``pip install check-jsonschema`` and found `here `_. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.16 2022/09/14 11:04:57 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.17.0.tar.gz) = 759437d0daeb12486d040e62c618dfb73f98d8e81316149a0f9dc67eb0bebbbf SHA512 (jsonschema-4.17.0.tar.gz) = a0160caea26527e5afbba48fea7f0700e8cd0bb5cbd9661501d34f5dd9857971ca3fd9982bc17f570d0b5a08eb5ecfd0e5182f78a0e0a6343621ed8360643166 Size (jsonschema-4.17.0.tar.gz) = 293414 bytes @ 1.16 log @py-jsonschema: updated to 4.16.0 v4.16.0 ======= * Improve the base URI behavior when resolving a ``$ref`` to a resolution URI which is different from the resolved schema's declared ``$id``. * Accessing ``jsonschema.draftN_format_checker`` is deprecated. Instead, if you want access to the format checker itself, it is exposed as ``jsonschema.validators.DraftNValidator.FORMAT_CHECKER`` on any ``jsonschema.protocols.Validator``. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.15 2022/09/05 14:14:17 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.16.0.tar.gz) = f2f85a575b4203252fbbaa253766fd7cd754460bbd9ae026700bae0c9d04f903 SHA512 (jsonschema-4.16.0.tar.gz) = c84abc992f410e9d558e2ce06c7172e9e2d298cff469baf8a23b1ea5b4777e6addfa757c5cc62b2e28e257721ee55e04bec0852e5f525adfa87392cbf712828f Size (jsonschema-4.16.0.tar.gz) = 292399 bytes @ 1.15 log @py-jsonschema: updated to 4.15.0 v4.15.0 * A specific API Reference page is now present in the documentation. * ``$ref`` on earlier drafts (specifically draft 7 and 6) has been "fixed" to follow the specified behavior when present alongside a sibling ``$id``. Specifically the ID is now properly ignored, and references are resolved against whatever resolution scope was previously relevant. v4.14.0 * ``FormatChecker.cls_checks`` is deprecated. Use ``FormatChecker.checks`` on an instance of ``FormatChecker`` instead. * ``unevaluatedItems`` has been fixed for draft 2019. It's nonetheless discouraged to use draft 2019 for any schemas, new or old. * Fix a number of minor annotation issues in ``protocols.Validator`` v4.13.0 * Add support for creating validator classes whose metaschema uses a different dialect than its schemas. In other words, they may use draft2020-12 to define which schemas are valid, but the schemas themselves use draft7 (or a custom dialect, etc.) to define which *instances* are valid. Doing this is likely not something most users, even metaschema authors, may need, but occasionally will be useful for advanced use cases. v4.12.1 * Fix some stray comments in the README. v4.12.0 * Warn at runtime when subclassing validator classes. Doing so was not intended to be public API, though it seems some downstream libraries do so. A future version will make this an error, as it is brittle and better served by composing validator objects instead. Feel free to reach out if there are any cases where changing existing code seems difficult and I can try to provide guidance. v4.11.0 * Make the rendered README in PyPI simpler and fancier. v4.10.3 * ``jsonschema.validators.validator_for`` now properly uses the explicitly provided default validator even if the ``$schema`` URI is not found. v4.10.2 * Fix a second place where subclasses may have added attrs attributes. v4.10.1 * Fix Validator.evolve (and APIs like ``iter_errors`` which call it) for cases where the validator class has been subclassed. Doing so wasn't intended to be public API, but given it didn't warn or raise an error it's of course understandable. The next release however will make it warn (and a future one will make it error). If you need help migrating usage of inheriting from a validator class feel free to open a discussion and I'll try to give some guidance. v4.10.0 * Add support for referencing schemas with ``$ref`` across different versions of the specification than the referrer's v4.9.1 * Update some documentation examples to use newer validator releases in their sample code. v4.9.0 * Fix relative ``$ref`` resolution when the base URI is a URN or other scheme. * ``pkgutil.resolve_name`` is now used to retrieve validators provided on the command line. This function is only available on 3.9+, so 3.7 and 3.8 (which are still supported) now rely on the `pkgutil_resolve_name `_ backport package. Note however that the CLI itself is due to be deprecated shortly in favor of `check-jsonschema `_. v4.8.0 * ``best_match`` no longer traverses into ``anyOf`` and ``oneOf`` when all of the errors within them seem equally applicable. This should lead to clearer error messages in some cases where no branches were matched. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.14 2022/07/08 07:54:06 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.15.0.tar.gz) = 7884b320e0cc8b4c5a00a28c8896384689523dcee32659ecd189608873bf718e SHA512 (jsonschema-4.15.0.tar.gz) = 8293b1dd7b16eb77b19ce89608384b3d97c1523ba080f38e6293390ba1b326d970721fdd6966623fc8a94b2b3357d1a68e1cc40b16eed037979fe6eb5684fa3f Size (jsonschema-4.15.0.tar.gz) = 290458 bytes @ 1.14 log @py-jsonschema: updated to 4.6.2 v4.6.2 * Fix a number of minor typos in docstrings, mostly private ones @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.13 2022/07/07 10:41:40 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.6.2.tar.gz) = 8898cb395d6b77dc95166793f1e5971f8d17aa43cfef7eb27755a17ec9ed60d3 SHA512 (jsonschema-4.6.2.tar.gz) = e41d6bda1bd6b12174201a70b5ad5209ab7c445faa6c947408f0fbc255839f3379ffe8b539760d993b435972936e4052300dbc420d4b87051f33180bced7efb2 Size (jsonschema-4.6.2.tar.gz) = 275975 bytes @ 1.13 log @py-jsonschema: updated to 4.6.1 v4.6.1 ------ * Gut the (incomplete) implementation of ``recursiveRef`` on draft 2019. It needs completing, but for now can lead to recursion errors. v4.6.0 ------ * Fix ``unevaluatedProperties`` and ``unevaluatedItems`` for types they should ignore * ``jsonschema`` now uses `hatch `_ for its build process. This should be completely transparent to end-users (and only matters to contributors). @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.12 2022/05/11 09:30:52 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.6.1.tar.gz) = ddfccdc4483d2dfa2c67b73effb1a81fbcb84da4d88f7ba6521c7d5963d85ec5 SHA512 (jsonschema-4.6.1.tar.gz) = 5c0e2806915ef4545092b0bffe4cc1207d9a6f2a6920c10894d5b7b2a9ed665093b7a9a68114d1a05528869e7d8aed902e7569800db4393fa810c0f6853f713d Size (jsonschema-4.6.1.tar.gz) = 278452 bytes @ 1.12 log @py-jsonschema: updated to 4.5.1 v4.5.0 ------ * Validator classes for each version now maintain references to the correct corresponding format checker * Development has moved to a `GitHub organization `_. No functional behavior changes are expected from the change. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.11 2022/04/07 06:49:20 adam Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.5.1.tar.gz) = f94cf3c999423b984611c5926f50d04ec749d66112b4eef9bab65abc0e9f014c SHA512 (jsonschema-4.5.1.tar.gz) = 3866a649ece45c1c69d3d5e9810cfdb094f1af82fcc08a186f9babd7516ad311c4bffa52f61f013bc84e7ab1be06605c5fab738c1c920ff8ce85a73429d9efde Size (jsonschema-4.5.1.tar.gz) = 282414 bytes @ 1.11 log @py-jsonschema: updated to 4.4.0 v4.4.0 ------ * Add ``mypy`` support * Add support for Python 3.11 v4.3.3 ------ * Properly report deprecation warnings at the right stack level v4.3.2 ------ * Additional performance improvements for resolving refs v4.3.1 ------ * Resolving refs has had performance improvements v4.3.0 ------ * Fix undesired fallback to brute force container uniqueness check on certain input types * Implement a PEP544 Protocol for validator classes v4.2.1 ------ * Pin ``importlib.resources`` from below v4.2.0 ------ * Use ``importlib.resources`` to load schemas * Ensure all elements of arrays are verified for uniqueness by ``uniqueItems`` v4.1.2 ------ * Fix ``dependentSchemas`` to properly consider non-object instances to be valid v4.1.1 ------ * Fix ``prefixItems`` not indicating which item was invalid within the instance path v4.1.0 ------ * Add Python 3.10 to the list of supported Python versions v4.0.1 ------ * Fix the declaration of minimum supported Python version v4.0.0 ------ * Partial support for Draft 2020-12 (as well as 2019-09). Thanks to Thomas Schmidt and Harald Nezbeda. * ``False`` and ``0`` are now properly considered non-equal even recursively within a container ``uniqueItems`` validation may be *slower* in some cases. Please feel free to report any significant performance regressions, though in some cases they may be difficult to address given the specification requirement. * The CLI has been improved, and in particular now supports a ``--output`` option (with ``plain`` (default) or ``pretty`` arguments) to control the output format. Future work may add additional machine-parsable output formats. * Code surrounding ``DEFAULT_TYPES`` and the legacy mechanism for specifying types to validators have been removed, as per the deprecation policy. Validators should use the ``TypeChecker`` object to customize the set of Python types corresponding to JSON Schema types. * Validation errors now have a ``json_path`` attribute, describing their location in JSON path format * Support for the IP address and domain name formats has been improved * Support for Python 2 and 3.6 has been dropped, with ``python_requires`` properly set. * ``multipleOf`` could overflow when given sufficiently large numbers. Now, when an overflow occurs, ``jsonschema`` will fall back to using fraction division * ``jsonschema.__version__``, ``jsonschema.validators.validators``, ``jsonschema.validators.meta_schemas`` and ``jsonschema.RefResolver.in_scope`` have been deprecated, as has passing a second-argument schema to ``Validator.iter_errors`` and ``Validator.is_valid``. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.10 2021/10/26 11:23:06 nia Exp $ d3 3 a5 3 BLAKE2s (jsonschema-4.4.0.tar.gz) = e04f27ea5b75c46c0df864c290704146bba3ab6ac15c5d80f50db96496c2b91b SHA512 (jsonschema-4.4.0.tar.gz) = 8e5c138f4debf7540e2cd131f3f208d1778927ac9036f5fa67bcf5db8c62fe1bb454c7818ee61acef64e856ea4b498ef6ab08be314a3c6b1e461e0bb44db41c7 Size (jsonschema-4.4.0.tar.gz) = 313519 bytes @ 1.10 log @textproc: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes Unfetchable distfiles (fetched conditionally?): ./textproc/convertlit/distinfo clit18src.zip @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.9 2021/10/07 15:02:13 nia Exp $ d3 3 a5 3 BLAKE2s (jsonschema-3.2.0.tar.gz) = 7d9dbc21ee91dce88b404292db47ac06d944dae1c8612e2c2ac0398203c73e05 SHA512 (jsonschema-3.2.0.tar.gz) = acbb4cec730a8cdab9f070593ed896064fbe082d464ec362adc952e4985e9eaa12ad0f2d55a04018ffdaf675e54037999a7219533dad6b84bf609f5dfe21bbab Size (jsonschema-3.2.0.tar.gz) = 167226 bytes @ 1.9 log @textproc: Remove SHA1 hashes for distfiles @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.8 2019/12/03 16:50:59 adam Exp $ d3 1 a3 1 RMD160 (jsonschema-3.2.0.tar.gz) = fb79174fba8955cf5433fa0e79d3ad3a48c590fb @ 1.8 log @py-jsonschema: updated to 3.2.0 v3.2.0 * Added a ``format_nongpl`` setuptools extra, which installs only ``format`` dependencies that are non-GPL @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.7 2019/10/19 14:32:09 adam Exp $ a2 1 SHA1 (jsonschema-3.2.0.tar.gz) = fbca135887b3c79e7f08fff6a34fef053746151b @ 1.7 log @py-jsonschema: updated to 3.1.1 3.1.1: * Regular expressions throughout schemas now respect the ECMA 262 dialect, as recommended by the specification. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.6 2019/08/22 11:47:04 adam Exp $ d3 4 a6 4 SHA1 (jsonschema-3.1.1.tar.gz) = 65f9ebd926599291dd3a832ba7d6b64373841ceb RMD160 (jsonschema-3.1.1.tar.gz) = a0a00e623dc2b4ac1aec882eb55f3014dbf01dcd SHA512 (jsonschema-3.1.1.tar.gz) = 28b8c7b8bfc72cc60d5fc44ce32990858ce2c1b1d88f6a28ea9f19123c8d29449d778ad55e0da72a9de30213d067ad5616a5d65ad1e0f7a9df375204096c6b18 Size (jsonschema-3.1.1.tar.gz) = 150179 bytes @ 1.6 log @py-jsonschema: updated to 3.0.2 v3.0.2 * Fixed a bug where 0 and False were considered equal by const and enum. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.5 2019/03/02 14:31:51 adam Exp $ d3 4 a6 4 SHA1 (jsonschema-3.0.2.tar.gz) = 47c75ca8426ca71ba59541b12985d1f7fa644364 RMD160 (jsonschema-3.0.2.tar.gz) = 938042de1ee392ab855abb2445c57426959a5fd8 SHA512 (jsonschema-3.0.2.tar.gz) = 13b65f318e1e2dc4a1d61399d517d39e53b0da71fbb5ec116e3b4ee274694300c6e2b3545058cd9f15129633fd093fa2d0c21ef1cce5356ca78e74187e7045c3 Size (jsonschema-3.0.2.tar.gz) = 143432 bytes @ 1.5 log @py-jsonschema: updated to 3.0.1 v3.0.0 * Support for Draft 6 and Draft 7 * Draft 7 is now the default * New TypeChecker object for more complex type definitions (and overrides) * Falling back to isodate for the date-time format checker is no longer attempted, in accordance with the specification @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.4 2017/05/04 17:46:53 adam Exp $ d3 4 a6 4 SHA1 (jsonschema-3.0.1.tar.gz) = fff9f3dc4c9f28e0008e482d1737723b71705d48 RMD160 (jsonschema-3.0.1.tar.gz) = 65018b00913131e736d01175fcca690aa1792d08 SHA512 (jsonschema-3.0.1.tar.gz) = 564e7385728b15387cd44c06cf50c36342fe4c6f497d208ce3d611d1659023e95ff032b2609a786cd9610bd915f878d138eef47913f18cc56eaae0651eb6efe8 Size (jsonschema-3.0.1.tar.gz) = 120834 bytes @ 1.4 log @v2.6.0 Support for Python 2.6 has been dropped. Improve a few error messages for uniqueItems and additionalProperties Fix an issue with ErrorTree's handling of multiple errors @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.3 2016/10/09 21:30:58 bsiegert Exp $ d3 4 a6 4 SHA1 (jsonschema-2.6.0.tar.gz) = 97e49df4601f7066d9954c0ec4d8d697887b32f0 RMD160 (jsonschema-2.6.0.tar.gz) = e4fb6118c531291fb705c9cc3629f1d5792a2dd8 SHA512 (jsonschema-2.6.0.tar.gz) = 03f916abd023b32fbe60f91718d6f2f94d8834bd1bd8ec85ab02f591a145161275c2cde25b037c4d2e94703b870159feb776d3556f011e4c394d2e20ab897b0b Size (jsonschema-2.6.0.tar.gz) = 53252 bytes @ 1.3 log @Update py-jsonschema to 2.5.1. There is no changelog for this version. v2.5.0 ------ * Improved performance on CPython by adding caching around ref resolution (#203) @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.2 2015/11/04 02:00:03 agc Exp $ d3 4 a6 4 SHA1 (jsonschema-2.5.1.tar.gz) = c30d415d250699630f302acb8efd660dd006a7ca RMD160 (jsonschema-2.5.1.tar.gz) = c3e5b05ad1829ed1425928babb3d96211d0f027a SHA512 (jsonschema-2.5.1.tar.gz) = 9e8f6ce16504b7ae7ef1ceb44ecb07eab85923e40967bd8e502b9fa779e772b547db90f56ca951d06591b951e7240db1071e909ac75543d42f6f2495f6de3298 Size (jsonschema-2.5.1.tar.gz) = 50855 bytes @ 1.2 log @Add SHA512 digests for distfiles for textproc category Problems found locating distfiles: Package cabocha: missing distfile cabocha-0.68.tar.bz2 Package convertlit: missing distfile clit18src.zip Package php-enchant: missing distfile php-enchant/enchant-1.1.0.tgz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.1 2014/12/31 13:18:58 bsiegert Exp $ d3 4 a6 4 SHA1 (jsonschema-2.4.0.tar.gz) = 35d4d90ce942a4b030eda75e9a2b32f97e121a98 RMD160 (jsonschema-2.4.0.tar.gz) = 2c48450248267e754dab237f48af949a15762205 SHA512 (jsonschema-2.4.0.tar.gz) = 111d60f6b490c016a69bed6b0b22cc6395c949d4510fdcb530757d6e61720cd2e1e3346293a5dd1b6501b262b36510ec08ab4ed76dc7484065e692e041232a93 Size (jsonschema-2.4.0.tar.gz) = 48293 bytes @ 1.1 log @Add a package for py-jsonschema. From DESCR: jsonschema is an implementation of JSON Schema for Python (supporting 2.6+ including Python 3). Features: - Full support for Draft 3 and Draft 4 of the schema. - Lazy validation that can iteratively report all validation errors. - Small and extensible - Programmatic querying of which properties or items failed validation. @ text @d1 1 a1 1 $NetBSD$ d5 1 @