ports/databases/py-sqlite3, branch main

databases/py-sqlite3: account for Python 3.13+

2025-11-02T00:41:41+00:00

Fix includes so internal headers are properly picked up

misc: unbreak the ports tree

2025-11-01T21:07:05+00:00

lang/python314: get port ready to ship

2025-11-01T20:11:56+00:00

claim maintainership on the new port - not doing that with the
previous commit by wen@ to have a clear distinction who contributed
what.

- require archivers/zstd since it's part of the Python standard library:
  https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-zstandard

- refresh Makefile.pre.in patch

- skip test_gdb without WITH_DEBUG

  test_gdb has test_pretty_print, which requires debug symbols.
  Skip it if WITH_DEBUG is not defined.

- drop --with-system-ffi configure option, which is no longer supported
  and its behaviour is now the default

- move sqlite3 extension back into port
  because the separate port fails to build
  (mark the external python:-3.13)

PR:		282176

python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc

2025-06-19T20:28:47+00:00

EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.

Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.

Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.

Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.

PR: 274671
Event: Kitchener-Waterloo Hackathon 202506

databases/py-sqlite3: convert to USE_PYTHON=pep517

2025-03-12T02:32:06+00:00

PR: 268283

databases/py-sqlite3: remove Python 2 support

2025-03-08T06:24:43+00:00

No remaining consumers in the tree. This is to prepare for conversion
to USE_PYTHON=pep517, as none of such tooling works with Python 2.

PR: 268283

python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal

2025-03-08T04:05:21+00:00

Any missed ports, feel free to bump.

Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.

*: Mark TESTING_UNSAFE

2024-03-16T01:20:08+00:00

Revert "*/py-{gdbm,sqlite3,tkinter}: switch from distutils to setuptools"

2022-12-15T17:31:40+00:00

This reverts commit 7446740638e7d833fde0962e71ef440a6af3c749.

The change is not valid as setuptools have deprecated setup.py,
while distutils will be supported in existing point releases.
Python 3.12 support will require different solution.

PR:		268283

*/py-{gdbm,sqlite3,tkinter}: switch from distutils to setuptools

2022-12-15T15:14:33+00:00

For python modules which come from python itself, switch from
distutils (no longer present in python 3.12) to setuptools, fixing
these mudules for python 3.12.

PR:		268283
Approved by:	vishwin (python@)