[Midnightbsd-cvs] [MidnightBSD/mports] 70f3fe: lang/python314: update to 3.14.7 (#1265)

[Lucas Holt]

  Branch: refs/heads/master
  Home:   https://github.com/MidnightBSD/mports
  Commit: 70f3fe12991e81406b0b9192ee1da2433c7fff34
      https://github.com/MidnightBSD/mports/commit/70f3fe12991e81406b0b9192ee1da2433c7fff34
  Author: Lucas Holt <luke at foolishgames.com>
  Date:   2026-09-15 (Tue, 15 Sep 2026)

  Changed paths:
    M lang/python314/Makefile.version
    M lang/python314/distinfo
    R lang/python314/files/patch-Lib_test_test__posix.py
    M lang/python314/pkg-plist

  Log Message:
  -----------
  lang/python314: update to 3.14.7 (#1265)

Update `lang/python314` from 3.14.3 to 3.14.7.

Checksum and size match FreeBSD's `lang/python314` distinfo for the same
tarball:

```
SHA256 (python/Python-3.14.7.tar.xz) = 3b48dac8fb59f62eaa67ac83c1eb12bda1b7a08406dd286e252c11a66be27f81
SIZE (python/Python-3.14.7.tar.xz) = 24053924
```

## Dropped `files/patch-Lib_test_test__posix.py`

The patch no longer applies, because upstream fixed this themselves.
3.14.7 now handles
`EOPNOTSUPP` from `posix_fallocate()` unconditionally:

```python
elif inst.errno == errno.EOPNOTSUPP:
    # ZFS on FreeBSD, FFS on NetBSD, etc.
    raise unittest.SkipTest(
        "the file system does not support posix_fallocate()")
```

That is what the patch was adding for FreeBSD. FreeBSD dropped the patch
for the same
reason (their `lang/python314/files/` now carries only 4 patches, none
for `test_posix.py`),
and no other python port in this tree has ever carried it — it was
introduced with the
original "lang/python314: add 3.14" commit. It also contained a
tab/space indentation
defect in the line it inserted.

## pkg-plist updates (+103 / -9)

- bundled pip `25.3` → `26.2.1`
- added: new `test_free_threading`, `test_tkinter`, `test_capi`,
`test_tools`, `test_json`
  and `test/support` modules, plus `idlelib` and `test` data files
- removed: `_test_gc_fast_cycles` and `test_pyrepl/eio_test_script`,
which upstream deleted

## Validation

- clean `build` → `fake` → `package` cycle succeeds (`Fake succeeded`,
`.mport` created)
- built interpreter smoke-tested:

```
version : 3.14.7
ssl     : OpenSSL 3.0.20 7 Apr 2026
modules : all core imports OK
```

## Pre-existing issues, not addressed here

Both were verified against pristine `master` and are unrelated to this
bump:

- `portlint` reports `FATAL: Makefile: [35]: use a tab (not space) after
a variable name`
  (`DISABLED_EXTENSIONS`) — reproduces on the unmodified port.
- Two `libdata/pkgconfig/*.pc` "missing from the plist" notices, caused
by the staging
  path-doubling in `Makefile:169`
(`${CP} ${FAKE_DESTDIR}${PREFIX}/... ${PREFIX}/...` — `${PREFIX}` is
already
`FAKE_DESTDIR`-prefixed in `post-install`). Non-fatal, and identical at
3.14.3.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01NSsgED5s7GPYJNb1HxuaU9

Signed-off-by: Lucas Holt <luke at foolishgames.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>



To unsubscribe from these emails, change your notification settings at https://github.com/MidnightBSD/mports/settings/notifications