Page MenuHomeFreeBSD

vishwin (Charlie Li)
User

Projects

User Details

User Since
Jan 26 2018, 10:31 AM (269 w, 2 d)

Recent Activity

Today

vishwin committed R11:bd7a4e938a60: devel/py-build: restore USE_PYTHON=allflavors but limit to 3.8+ (authored by vishwin).
devel/py-build: restore USE_PYTHON=allflavors but limit to 3.8+
Mon, Mar 27, 5:51 AM
vishwin committed R11:33333715d11b: python.mk: use gpep517 as build frontend on Python 3.7 (authored by vishwin).
python.mk: use gpep517 as build frontend on Python 3.7
Mon, Mar 27, 5:09 AM
vishwin committed R11:a4d616aff942: devel/py-gpep517: add (authored by vishwin).
devel/py-gpep517: add
Mon, Mar 27, 4:49 AM

Yesterday

vishwin committed R11:ef942f79b3c0: lang/python310: add LibreSSL support (authored by vishwin).
lang/python310: add LibreSSL support
Sun, Mar 26, 2:39 PM

Wed, Mar 22

vishwin requested review of D39209: lang/rust: switch to USES=cargo.
Wed, Mar 22, 2:11 PM
vishwin added a member for rust: vishwin.
Wed, Mar 22, 1:57 PM
vishwin requested review of D39208: cargo.mk: move cargo-crates-generate-lockfile to depend on patch.
Wed, Mar 22, 1:56 PM
vishwin added a comment to D39205: cargo.mk: account for DIST_SUBDIR in cargo-checksum.
% git grep -B 5 DIST_SUBDIR= -- `git grep --max-depth=2 -l cargo`
graphics/librsvg2-rust/Makefile-PORTVERSION=    2.54.5
graphics/librsvg2-rust/Makefile-PORTREVISION=   6
graphics/librsvg2-rust/Makefile-CATEGORIES=     graphics gnome
graphics/librsvg2-rust/Makefile-MASTER_SITES=   GNOME
graphics/librsvg2-rust/Makefile-PKGNAMESUFFIX=  2-rust
graphics/librsvg2-rust/Makefile:DIST_SUBDIR=    gnome2
--
lang/rust-bootstrap/Makefile-CATEGORIES=        lang
lang/rust-bootstrap/Makefile-MASTER_SITES=      https://static.rust-lang.org/dist/
lang/rust-bootstrap/Makefile-PKGNAMEPREFIX=     ${FLAVOR:S/_/-/g}-
lang/rust-bootstrap/Makefile-PKGNAMESUFFIX=     -bootstrap
lang/rust-bootstrap/Makefile-DISTNAME=  ${PORTNAME}c-${PORTVERSION}-src
lang/rust-bootstrap/Makefile:DIST_SUBDIR=       rust

Neither of these currently use USES=cargo.

Wed, Mar 22, 1:48 PM
vishwin requested review of D39205: cargo.mk: account for DIST_SUBDIR in cargo-checksum.
Wed, Mar 22, 1:34 PM

Thu, Mar 16

vishwin added a comment to D39124: Mk/Uses/python.mk: Support PEP440 versioning.

We're safe, no exp-run needed:

% git grep -B 5 PORTVERSION= -- `git grep --max-depth=2 -l pep517`
CHANGES-  with EXTRACT_ONLY.
CHANGES-
CHANGES-  A simple example:
CHANGES-
CHANGES-    PORTNAME=     bar
CHANGES:    PORTVERSION=  1.0
--
databases/py-aiosqlite/Makefile-PORTNAME=       aiosqlite
databases/py-aiosqlite/Makefile:PORTVERSION=    0.18.0
--
devel/mercurial/Makefile-PORTNAME=      mercurial
devel/mercurial/Makefile:PORTVERSION=   6.3.2
--
devel/nox/Makefile-PORTNAME=    nox
devel/nox/Makefile:PORTVERSION= 2022.11.21
--
devel/py-RPyC/Makefile-PORTNAME=        rpyc
devel/py-RPyC/Makefile:PORTVERSION=     5.3.1
--
devel/py-argh/Makefile-PORTNAME=        argh
devel/py-argh/Makefile:PORTVERSION=     0.28.1
--
devel/py-build/Makefile-PORTNAME=       build
devel/py-build/Makefile:PORTVERSION=    0.10.0
--
devel/py-find-libpython/Makefile-PORTNAME=      find-libpython
devel/py-find-libpython/Makefile:PORTVERSION=   0.3.0
--
devel/py-flit-core/Makefile-PORTNAME=   flit-core
devel/py-flit-core/Makefile:PORTVERSION=        3.8.0
--
devel/py-flit/Makefile-PORTNAME=        flit
devel/py-flit/Makefile:PORTVERSION=     3.8.0
--
devel/py-installer/Makefile-PORTNAME=   installer
devel/py-installer/Makefile:PORTVERSION=        0.6.0
--
devel/py-interface-meta/Makefile-PORTNAME=      interface-meta
devel/py-interface-meta/Makefile:PORTVERSION=   1.3.0
--
devel/py-jsonschema/Makefile-PORTNAME=  jsonschema
devel/py-jsonschema/Makefile:PORTVERSION=       4.17.3
--
devel/py-lazy_loader/Makefile-PORTNAME= lazy_loader
devel/py-lazy_loader/Makefile:PORTVERSION=      0.1
--
devel/py-packaging/Makefile-PORTNAME=   packaging
devel/py-packaging/Makefile:PORTVERSION=        23.0
--
devel/py-pathspec/Makefile-PORTNAME=    pathspec
devel/py-pathspec/Makefile:PORTVERSION= 0.11.1
--
devel/py-pdm-pep517/Makefile-PORTNAME=  pdm-pep517
devel/py-pdm-pep517/Makefile:PORTVERSION=       1.1.0
--
devel/py-pdm/Makefile-PORTNAME= pdm
devel/py-pdm/Makefile:PORTVERSION=      2.2.1
--
devel/py-pep517/Makefile-PORTNAME=      pep517
devel/py-pep517/Makefile:PORTVERSION=   0.13.0
--
devel/py-pyls-black/Makefile-PORTNAME=  pyls-black
devel/py-pyls-black/Makefile:PORTVERSION=       0.4.7
--
devel/py-pyproject_hooks/Makefile-PORTNAME=     pyproject_hooks
devel/py-pyproject_hooks/Makefile:PORTVERSION=  1.0.0
--
devel/py-pytest-metadata/Makefile-PORTNAME=     pytest-metadata
devel/py-pytest-metadata/Makefile:PORTVERSION=  2.0.4
--
devel/py-pytoolconfig/Makefile-PORTNAME=        pytoolconfig
devel/py-pytoolconfig/Makefile:PORTVERSION=     1.2.5
--
devel/py-requirementslib/Makefile-PORTNAME=     requirementslib
devel/py-requirementslib/Makefile:PORTVERSION=  2.2.3
--
devel/py-typing-extensions/Makefile-PORTNAME=   typing-extensions
devel/py-typing-extensions/Makefile:PORTVERSION=        4.4.0
--
devel/py-virtualenv/Makefile-PORTNAME=  virtualenv
devel/py-virtualenv/Makefile:PORTVERSION=       20.20.0
--
finance/py-financedatabase/Makefile-PORTNAME=   financedatabase
finance/py-financedatabase/Makefile:PORTVERSION=        2.0.9
--
print/py-pydyf/Makefile-PORTNAME=       pydyf
print/py-pydyf/Makefile:PORTVERSION=    0.5.0
--
print/py-weasyprint/Makefile-PORTNAME=  weasyprint
print/py-weasyprint/Makefile:PORTVERSION=       58.0
--
security/py-securesystemslib/Makefile-PORTNAME= securesystemslib
security/py-securesystemslib/Makefile:PORTVERSION=      0.26.0
--
security/py-tuf/Makefile-PORTNAME=      tuf
security/py-tuf/Makefile:PORTVERSION=   2.1.0
--
sysutils/py-docker/Makefile-PORTNAME=   docker
sysutils/py-docker/Makefile:PORTVERSION=        6.0.1
--
textproc/py-pyphen/Makefile-PORTNAME=   pyphen
textproc/py-pyphen/Makefile:PORTVERSION=        0.13.0
--
textproc/py-sphinx/Makefile-PORTNAME=   sphinx
textproc/py-sphinx/Makefile:PORTVERSION=        5.3.0
--
textproc/py-tomli/Makefile-PORTNAME=    tomli
textproc/py-tomli/Makefile:PORTVERSION= 2.0.1
--
www/py-dj40-django-auth-ldap/Makefile-PORTNAME= django-auth-ldap
www/py-dj40-django-auth-ldap/Makefile:PORTVERSION=      4.1.0
--
www/py-dj41-django-auth-ldap/Makefile-PORTNAME= django-auth-ldap
www/py-dj41-django-auth-ldap/Makefile:PORTVERSION=      4.1.0
--
www/py-dj41-django-cors-headers/Makefile-PORTNAME=      django-cors-headers
www/py-dj41-django-cors-headers/Makefile:PORTVERSION=   3.14.0
--
www/py-dj41-django-rich/Makefile-PORTNAME=      django-rich
www/py-dj41-django-rich/Makefile:PORTVERSION=   1.5.0
--
www/py-django-auth-ldap/Makefile-PORTNAME=      django-auth-ldap
www/py-django-auth-ldap/Makefile:PORTVERSION=   4.1.0
--
www/py-fastapi/Makefile-PORTNAME=       fastapi
www/py-fastapi/Makefile:PORTVERSION=    0.92.0
Thu, Mar 16, 8:12 PM
vishwin accepted D39124: Mk/Uses/python.mk: Support PEP440 versioning.
Thu, Mar 16, 5:40 PM
vishwin added a member for Python: vishwin.
Thu, Mar 16, 5:39 PM
vishwin accepted D39124: Mk/Uses/python.mk: Support PEP440 versioning.

Haha beat me to it! Also had this sitting locally, checking that existing PORTREVISION uses didn't break (all good there).

Thu, Mar 16, 5:28 PM

Wed, Mar 15

vishwin requested review of D39095: devel/py-wheel: update to 0.40.0.
Wed, Mar 15, 2:23 PM

Mon, Mar 13

vishwin added a comment to D38802: benchmarks/uica: update to g20230115+2022.12.
In D38802#889186, @fuz wrote:

Auto-generating pycode files is off the cards, so this change is no longer needed.

Mon, Mar 13, 5:54 PM
vishwin committed R11:6c8bee42bcfc: chinese/libpinyin: update to 2.8.1 (authored by vishwin).
chinese/libpinyin: update to 2.8.1
Mon, Mar 13, 12:16 AM

Sun, Mar 12

vishwin added a comment to D39004: devel/meson: flavourise.

Looks incomplete. patch-setup.py was adjusting manpage location, obsoleted by 003a571d1d65. To fix polkit action may require either expanding USES=uniquefiles:dirs (implied by USE_PYTHON=concurrent) to handle the conflicting file/directory or adjusting ${TMPPLIST} from post-patch gated by PKGNAMESUFFIX.

Sun, Mar 12, 3:31 PM
vishwin added a comment to D39004: devel/meson: flavourise.

So the default-python based package can additionally install everything under plain names, or there can be another package that depends on the default python's and adds symlinks to the relevant entry points, commands, documentation, without all those 39 and -3.9 names.

Sun, Mar 12, 2:21 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

devel/meson-python: patch out hardcoded meson invocations

Sun, Mar 12, 2:15 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

devel/meson-python: add BINARY_ALIAS

Sun, Mar 12, 1:15 PM
vishwin added a comment to D39004: devel/meson: flavourise.

Doing it this way, when building meson-python on a non-default Python, fails because literally bin/meson is expected, not bin/meson-${PYTHON_VER}.

Sun, Mar 12, 12:56 PM
vishwin abandoned D34739: lang/python: add bytecode trigger.
Sun, Mar 12, 12:02 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

devel/meson: bump PORTREVISION for package change

Sun, Mar 12, 12:01 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

add USE_PYTHON=concurrent and remove polkit action, as it file conflicts and doesn't work properly here anyway

Sun, Mar 12, 12:01 PM

Sat, Mar 11

vishwin closed D39004: devel/meson: flavourise.
Sat, Mar 11, 4:37 PM
vishwin committed R11:b883eac8e32d: devel/meson: enable FLAVORs (authored by vishwin).
devel/meson: enable FLAVORs
Sat, Mar 11, 4:37 PM

Thu, Mar 9

vishwin updated the diff for D39004: devel/meson: flavourise.

devel/meson-python: adjust dependency lines

Thu, Mar 9, 8:25 PM
vishwin updated the test plan for D39004: devel/meson: flavourise.
Thu, Mar 9, 8:16 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

meson.mk: use entry point in dependency specifier, PKGNAME changes when not default FLAVOR

Thu, Mar 9, 8:15 PM
vishwin updated the test plan for D39004: devel/meson: flavourise.
Thu, Mar 9, 8:11 PM
vishwin updated the test plan for D39004: devel/meson: flavourise.
Thu, Mar 9, 8:09 PM
vishwin updated the diff for D39004: devel/meson: flavourise.

meson.mk: FLAVOR was apparently not needed here

Thu, Mar 9, 8:08 PM
vishwin updated the test plan for D39004: devel/meson: flavourise.
Thu, Mar 9, 7:58 PM
vishwin requested review of D39004: devel/meson: flavourise.
Thu, Mar 9, 7:49 PM
vishwin committed R11:46a71ea3bf00: python.mk: introduce PY_SETUPTOOLS (authored by vishwin).
python.mk: introduce PY_SETUPTOOLS
Thu, Mar 9, 5:37 PM
vishwin committed R11:f69954332f98: textproc/meld: update to 3.22.0 (authored by vishwin).
textproc/meld: update to 3.22.0
Thu, Mar 9, 5:19 PM
vishwin committed R11:67de7ad43c69: strip_RECORD.py: move to Mk/Scripts (authored by vishwin).
strip_RECORD.py: move to Mk/Scripts
Thu, Mar 9, 11:21 AM
vishwin committed R11:316d64c81e7b: devel/meson-python: add (authored by vishwin).
devel/meson-python: add
Thu, Mar 9, 4:49 AM
vishwin committed R11:a1039fe12a28: python.mk: add PEP517_BUILD_CONFIG_SETTING (authored by vishwin).
python.mk: add PEP517_BUILD_CONFIG_SETTING
Thu, Mar 9, 4:35 AM
vishwin committed R11:8731e3328335: python.mk: add USE_PYTHON=cython_test (authored by vishwin).
python.mk: add USE_PYTHON=cython_test
Thu, Mar 9, 4:25 AM
vishwin committed R11:43ae3588e62e: python.mk: use PYTHON_MAJOR_VER for Python 2/3 conditionals (authored by vishwin).
python.mk: use PYTHON_MAJOR_VER for Python 2/3 conditionals
Thu, Mar 9, 4:19 AM
vishwin committed R11:97741a0217bc: python.mk: document individual module variables (authored by vishwin).
python.mk: document individual module variables
Thu, Mar 9, 4:13 AM
vishwin committed R11:b0a6205495e0: python.mk: move PEP-517 docs above distutils (authored by vishwin).
python.mk: move PEP-517 docs above distutils
Thu, Mar 9, 3:59 AM
vishwin committed R11:16a6fecb4ff8: python.mk: use script to process RECORD for the first pass (authored by vishwin).
python.mk: use script to process RECORD for the first pass
Thu, Mar 9, 3:44 AM
vishwin committed R11:1e9c9994ae53: Tools/scripts: add strip_RECORD.py (authored by vishwin).
Tools/scripts: add strip_RECORD.py
Thu, Mar 9, 3:23 AM
vishwin committed R11:588237f00b8f: python.mk: add man/ to PEP-517 autoplist (authored by vishwin).
python.mk: add man/ to PEP-517 autoplist
Thu, Mar 9, 3:08 AM

Tue, Feb 28

vishwin removed a reviewer for D34739: lang/python: add bytecode trigger: mandree.
Tue, Feb 28, 8:20 PM
vishwin added a comment to D34739: lang/python: add bytecode trigger.

You are distracting again, and your arguments are not relevant. Functions can have arguments, so you can cater for the few differences. A Python port that isn't CPython need not call the refactored function at all.

Tue, Feb 28, 8:20 PM
vishwin added a comment to D34739: lang/python: add bytecode trigger.

So, the trigger is redundantly duplicated across all Python versions. This is bad style and error-prone.

Please refactor this to a common script (either we keep it in Tools/ or else in a separate port), and just run it from the trigger (which has the port-specific %%PYTHON_*%% variables, with the necessary arguments.
That also makes it amenable to separate testing and maintenance independent of the Python package.

Tue, Feb 28, 7:47 PM
vishwin removed a reviewer for D34739: lang/python: add bytecode trigger: mandree.
Tue, Feb 28, 7:37 PM
vishwin updated the diff for D34739: lang/python: add bytecode trigger.

yeet bytecode from USE_PYTHON=distutils because to hell with them

Tue, Feb 28, 6:47 AM
vishwin removed reviewers for D34739: lang/python: add bytecode trigger: portmgr, tcberner, fluffy, arrowd, mandree.
Tue, Feb 28, 6:41 AM
vishwin updated the diff for D34739: lang/python: add bytecode trigger.

now that we apparently have to appease non-fatal errors not part of the build, as if package builders are sentient beings

Tue, Feb 28, 6:40 AM
vishwin committed R11:922e7f41450b: lang/python: restore USES=python variables and SUB_LIST (no-op) (authored by vishwin).
lang/python: restore USES=python variables and SUB_LIST (no-op)
Tue, Feb 28, 12:01 AM

Mon, Feb 27

vishwin added a comment to D34739: lang/python: add bytecode trigger.

For those who've lived under a rock, I'm not under mentorship.

Mon, Feb 27, 9:45 PM

Sun, Feb 26

vishwin committed R11:853d0bf6fbe1: python.mk: add etc/ to PEP-517 autoplist (authored by vishwin).
python.mk: add etc/ to PEP-517 autoplist
Sun, Feb 26, 6:50 PM
vishwin committed R11:89b14cd3aecc: lang/cjs: correct licence file locations (authored by vishwin).
lang/cjs: correct licence file locations
Sun, Feb 26, 3:47 AM
vishwin closed D38050: python.mk: PEP-517 data_files support.
Sun, Feb 26, 3:15 AM
vishwin committed R11:18982c467f6c: python.mk: PEP-517 data_files support (authored by vishwin).
python.mk: PEP-517 data_files support
Sun, Feb 26, 3:15 AM
vishwin updated the diff for D38050: python.mk: PEP-517 data_files support.

only allow select directories under hier(7)

Sun, Feb 26, 3:07 AM

Sat, Feb 25

vishwin closed D37917: x11/cinnamon: update to 5.4.
Sat, Feb 25, 8:53 PM
vishwin committed R11:2d87115f8c5e: x11/cinnamon: update to 5.4 (authored by vishwin).
x11/cinnamon: update to 5.4
Sat, Feb 25, 8:53 PM
vishwin updated the diff for D37917: x11/cinnamon: update to 5.4.

lang/cjs: pull in commit from cjs to fix clang-15 build

Sat, Feb 25, 8:21 PM
vishwin committed R11:9fbe5f4d774c: python.mk: explicitly pass ${PREFIX} to ${PEP517_INSTALL_CMD} (authored by vishwin).
python.mk: explicitly pass ${PREFIX} to ${PEP517_INSTALL_CMD}
Sat, Feb 25, 5:36 PM
vishwin committed R11:4ed59043fe8e: devel/mercurial: convert to PEP-517 (authored by vishwin).
devel/mercurial: convert to PEP-517
Sat, Feb 25, 5:15 PM

Feb 22 2023

vishwin committed R11:339bbb94eb45: devel/libgtop: change DIST_SUBDIR to gnome for consistency (authored by vishwin).
devel/libgtop: change DIST_SUBDIR to gnome for consistency
Feb 22 2023, 5:46 AM

Feb 18 2023

vishwin committed R11:e7a9ba1fecd9: devel/py-typing-extensions: unbreak circular dependency (authored by vishwin).
devel/py-typing-extensions: unbreak circular dependency
Feb 18 2023, 5:54 PM

Feb 15 2023

vishwin closed D34739: lang/python: add bytecode trigger.
Feb 15 2023, 9:36 PM
vishwin committed R11:c17ddfbf66e2: lang/python: add bytecode trigger (authored by vishwin).
lang/python: add bytecode trigger
Feb 15 2023, 9:36 PM
vishwin updated the diff for D34739: lang/python: add bytecode trigger.
  • silence bytecode compile/delete messages, except for errors
  • add CHANGES and UPDATING entries for SUB_LIST and trigger
Feb 15 2023, 8:51 PM
vishwin added inline comments to D34739: lang/python: add bytecode trigger.
Feb 15 2023, 1:03 PM

Feb 14 2023

vishwin updated the diff for D34739: lang/python: add bytecode trigger.

use more SUB_LIST entries on triggers

Feb 14 2023, 1:18 PM

Feb 12 2023

vishwin abandoned D38461: lang/python: do not write bytecode when running as root.

Obviated in favour of D34739

Feb 12 2023, 6:19 PM

Feb 11 2023

vishwin abandoned D38429: python.mk: don't write bytecode whilst building under PEP-517.

Obviated in favour of D34739

Feb 11 2023, 10:44 PM
vishwin retitled D34739: lang/python: add bytecode trigger from python: add first prototype for __pycache__ trigger to lang/python: add bytecode trigger.
Feb 11 2023, 10:41 PM
vishwin updated the diff for D34739: lang/python: add bytecode trigger.

individualise between the different interpreters/distributions

Feb 11 2023, 10:40 PM

Feb 10 2023

vishwin added a comment to D38429: python.mk: don't write bytecode whilst building under PEP-517.

pip is unacceptably heavy dependency-wise and cannot be bootstrapped (in that circular dependencies will result) how installer, build et al can. It is also not intended for "system" use. installer currently does not track bytecode in RECORD or anywhere else.

Feb 10 2023, 9:15 PM

Feb 9 2023

vishwin added a comment to D38429: python.mk: don't write bytecode whilst building under PEP-517.

Most others package bytecode, but again as a crutch due to lack of a trigger function that we have. Most others also don't have the strict/static plist that we do; pacman for instance just takes whatever in their equivalent ${STAGEDIR} and calls it a day. Therein lies our problem: there is no reliable way to reliably track bytecode for the purposes of a static plist with the latest Python packaging tooling, not even with wildcards. (We had a fighting chance with the old distutils method, but that's another story.) It is compounded by no stability guarantees within the bytecodes themselves, further cementing that these are little more than instruction caches tailored to each individual installation.

Feb 9 2023, 5:07 PM
vishwin added a comment to D38461: lang/python: do not write bytecode when running as root.

Alternatively, instead of special handling for root, writing bytecode on import can be unconditionally disabled by default. Still does not affect any manual bytecode compilation via compile_py, compileall, et al (apparent in that none of the lang/python ports have changed plists), nor does it affect utilising existing bytecode so long as they match the timestamps and specific Python interpreter they were built against. Most importantly, there is still no divergence from upstream as far as code interpretation and execution is concerned, just less filesystem pollution.

Feb 9 2023, 8:53 AM
vishwin added a comment to D38461: lang/python: do not write bytecode when running as root.

pkg's INSTALL_AS_USER is not a default setting.

Feb 9 2023, 8:44 AM
vishwin added a comment to D38461: lang/python: do not write bytecode when running as root.

There is no difference from upstream as far as actual Python interpretation and execution is concerned. The only difference is no more filesystem-polluting instruction caching when ran as root if such files do not already exist. Manually invoking compile_py, compileall et al are unchanged.

Feb 9 2023, 8:02 AM
vishwin added a comment to D38429: python.mk: don't write bytecode whilst building under PEP-517.
In D38429#875110, @mat wrote:

So what, we have to forbid users running python bits to do anything as root?

Feb 9 2023, 7:57 AM
vishwin added a comment to D38461: lang/python: do not write bytecode when running as root.

It makes sense in that packaged bytecode is going away.

Feb 9 2023, 7:53 AM
vishwin requested review of D38461: lang/python: do not write bytecode when running as root.
Feb 9 2023, 7:49 AM

Feb 8 2023

vishwin added a comment to D38429: python.mk: don't write bytecode whilst building under PEP-517.

Started an upstream discussion https://github.com/python/cpython/issues/101702 since I'm not sure of any good way to pass the variable globally in the environment for every stage (important for the interactive stage)

Feb 8 2023, 6:33 PM
vishwin added a comment to D34739: lang/python: add bytecode trigger.

Approximating the process as if the Python packaging tooling is the final arbiter, this has to run:

  • on Python package install/update
  • on Python distribution update
  • on deinstall
Feb 8 2023, 12:17 PM
vishwin commandeered D34739: lang/python: add bytecode trigger.
Feb 8 2023, 12:12 PM
vishwin added a comment to D38429: python.mk: don't write bytecode whilst building under PEP-517.
In D38429#874508, @mat wrote:

From what I understand, you removed sunpoet's fix because of some hypothetical future problem that may never happen.

This problem exists right now, because bytecode is not to be packaged, period. We (and many other operating system-level packagers) have been doing it wrong for years, and only as a crutch due to lack of a trigger mechanism that we now have. D34739 uses trigger support; having bytecode packaged hampers development of that, because proper operation cannot be verified.

Feb 8 2023, 12:05 PM

Feb 7 2023

vishwin requested review of D38429: python.mk: don't write bytecode whilst building under PEP-517.
Feb 7 2023, 10:58 PM
vishwin updated the diff for D37920: devel/py-packaging: convert to USE_PYTHON=pep517.

use DISTVERSION, bump PORTREVISION, MAINTAINER to python@ as infrastructure

Feb 7 2023, 2:18 AM
vishwin retitled D37920: devel/py-packaging: convert to USE_PYTHON=pep517 from devel/py-packaging: update to 22.0 to devel/py-packaging: convert to USE_PYTHON=pep517.
Feb 7 2023, 2:14 AM
vishwin closed D34789: devel/py-installer: convert to PEP-517 build and packaging.
Feb 7 2023, 1:53 AM
vishwin committed R11:70c7afe71d93: devel/py-installer: convert to USE_PYTHON=pep517 (authored by vishwin).
devel/py-installer: convert to USE_PYTHON=pep517
Feb 7 2023, 1:53 AM
vishwin updated the diff for D34789: devel/py-installer: convert to PEP-517 build and packaging.

another round of stray paths smh

Feb 7 2023, 1:45 AM
vishwin updated the diff for D34789: devel/py-installer: convert to PEP-517 build and packaging.

convert to DISTVERSION, bump PORTREVISION, fix PEP517_BUILD_DEPEND

Feb 7 2023, 1:43 AM
vishwin closed D34786: devel/py-flit-core: convert to self-hosting bootstrap.
Feb 7 2023, 1:22 AM
vishwin committed R11:04ccdc92b5b9: devel/py-flit-core: convert to self-hosting bootstrap (authored by vishwin).
devel/py-flit-core: convert to self-hosting bootstrap
Feb 7 2023, 1:22 AM
vishwin updated the diff for D34786: devel/py-flit-core: convert to self-hosting bootstrap.

hopefully no more stray paths

Feb 7 2023, 1:12 AM
vishwin updated the diff for D34786: devel/py-flit-core: convert to self-hosting bootstrap.

rebase (stray paths)

Feb 7 2023, 1:09 AM
vishwin updated the diff for D34786: devel/py-flit-core: convert to self-hosting bootstrap.

devel/py-flit-core: switch to DISTVERSION and simplify

Feb 7 2023, 1:07 AM