head 1.5; access; symbols pkgsrc-2023Q4:1.5.0.2 pkgsrc-2023Q4-base:1.5 pkgsrc-2023Q3:1.4.0.8 pkgsrc-2023Q3-base:1.4 pkgsrc-2023Q2:1.4.0.6 pkgsrc-2023Q2-base:1.4 pkgsrc-2023Q1:1.4.0.4 pkgsrc-2023Q1-base:1.4 pkgsrc-2022Q4:1.4.0.2 pkgsrc-2022Q4-base:1.4 pkgsrc-2022Q3:1.2.0.12 pkgsrc-2022Q3-base:1.2 pkgsrc-2022Q2:1.2.0.10 pkgsrc-2022Q2-base:1.2 pkgsrc-2022Q1:1.2.0.8 pkgsrc-2022Q1-base:1.2 pkgsrc-2021Q4:1.2.0.6 pkgsrc-2021Q4-base:1.2 pkgsrc-2021Q3:1.2.0.4 pkgsrc-2021Q3-base:1.2 pkgsrc-2021Q2:1.2.0.2 pkgsrc-2021Q2-base:1.2 pkgsrc-2021Q1:1.1.0.32 pkgsrc-2021Q1-base:1.1 pkgsrc-2020Q4:1.1.0.30 pkgsrc-2020Q4-base:1.1 pkgsrc-2020Q3:1.1.0.28 pkgsrc-2020Q3-base:1.1 pkgsrc-2020Q2:1.1.0.24 pkgsrc-2020Q2-base:1.1 pkgsrc-2020Q1:1.1.0.4 pkgsrc-2020Q1-base:1.1 pkgsrc-2019Q4:1.1.0.26 pkgsrc-2019Q4-base:1.1 pkgsrc-2019Q3:1.1.0.22 pkgsrc-2019Q3-base:1.1 pkgsrc-2019Q2:1.1.0.20 pkgsrc-2019Q2-base:1.1 pkgsrc-2019Q1:1.1.0.18 pkgsrc-2019Q1-base:1.1 pkgsrc-2018Q4:1.1.0.16 pkgsrc-2018Q4-base:1.1 pkgsrc-2018Q3:1.1.0.14 pkgsrc-2018Q3-base:1.1 pkgsrc-2018Q2:1.1.0.12 pkgsrc-2018Q2-base:1.1 pkgsrc-2018Q1:1.1.0.10 pkgsrc-2018Q1-base:1.1 pkgsrc-2017Q4:1.1.0.8 pkgsrc-2017Q4-base:1.1 pkgsrc-2017Q3:1.1.0.6 pkgsrc-2017Q3-base:1.1 pkgsrc-2017Q2:1.1.0.2 pkgsrc-2017Q2-base:1.1; locks; strict; comment @# @; 1.5 date 2023.10.28.19.57.03; author wiz; state Exp; branches; next 1.4; commitid jP8MYROLWZ3yJqKE; 1.4 date 2022.11.29.08.42.10; author wiz; state Exp; branches; next 1.3; commitid uv2Vm98VTdBjIz3E; 1.3 date 2022.11.28.18.42.09; author adam; state Exp; branches; next 1.2; commitid lV6mfhBDb3X64v3E; 1.2 date 2021.04.06.20.01.36; author adam; state Exp; branches; next 1.1; commitid X4quB8Ju9dT5PgOC; 1.1 date 2017.04.14.12.31.06; author leot; state Exp; branches; next ; commitid kSiNuuTTtz0T1vNz; desc @@ 1.5 log @python/wheel.mk: simplify a lot, and switch to 'installer' for installation This follows the recommended bootstrap method (flit_core, build, installer). However, installer installs different files than pip, so update PLISTs for all packages using wheel.mk and bump their PKGREVISIONs. @ text @@@comment $NetBSD$ ${PYSITELIB}/${WHEEL_INFODIR}/LICENSE ${PYSITELIB}/${WHEEL_INFODIR}/METADATA ${PYSITELIB}/${WHEEL_INFODIR}/RECORD ${PYSITELIB}/${WHEEL_INFODIR}/WHEEL ${PYSITELIB}/${WHEEL_INFODIR}/top_level.txt ${PYSITELIB}/${WHEEL_INFODIR}/zip-safe ${PYSITELIB}/kaitaistruct.py ${PYSITELIB}/kaitaistruct.pyc ${PYSITELIB}/kaitaistruct.pyo @ 1.4 log @py-kaitaistruct: convert to use wheel.mk to fix build @ text @a1 1 ${PYSITELIB}/${WHEEL_INFODIR}/INSTALLER a4 1 ${PYSITELIB}/${WHEEL_INFODIR}/REQUESTED a5 1 ${PYSITELIB}/${WHEEL_INFODIR}/direct_url.json d10 1 @ 1.3 log @py-kaitaistruct: updated to 0.10 0.10 read_bytes(): use previous implementation again for small reads For small reads, the new code that tries to avoid unnecessary reads is noticeably slower than the previous code that reads unconditionally. In the worst case (1-byte reads), the new code is 13 times as slow as the previous implementation. The potential memory/IO savings only become worth it for larger reads, where the performance difference disappears. @ text @d1 10 a10 7 @@comment $NetBSD: PLIST,v 1.2 2021/04/06 20:01:36 adam Exp $ ${PYSITELIB}/${EGG_INFODIR}/PKG-INFO ${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt ${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt ${PYSITELIB}/${EGG_INFODIR}/requires.txt ${PYSITELIB}/${EGG_INFODIR}/top_level.txt ${PYSITELIB}/${EGG_INFODIR}/zip-safe a12 1 ${PYSITELIB}/kaitaistruct.pyo @ 1.2 log @py-kaitaistruct: updated to 0.9 0.9: Add ValidationExprError @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1 2017/04/14 12:31:06 leot Exp $ d5 1 @ 1.1 log @Import py-kaitaistruct-0.7 as devel/py-kaitaistruct Kaitai Struct is a declarative language used for describe various binary data structures, laid out in files or in memory: i.e. binary file formats, network stream packet formats, etc. The main idea is that a particular format is described in Kaitai Struct language (.ksy file) and then can be compiled with ksc into source files in one of the supported programming languages. These modules will include a generated code for a parser that can read described data structure from a file / stream and give access to it in a nice, easy-to-comprehend API. @ text @d1 1 a1 1 @@comment $NetBSD$ d6 1 @