Cleanup dev setup

- Removes buildout; test_layer now fetches the crate package itself
- Removes setup.py
- Removes stale bin/test
- Removes stale requirements.txt
- Updates DEVELOP.rst
- Removes poethepoet. Most python developers are familiar with `ruff`,
  `mypy` and `pytest`, no need to add an extra DSL on top that
  obfuscates what's being used.
- Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial
  enough and Python developers should be familiar with them.

Author: mfussenegger

DEVELOP.rst

@@ -5,95 +5,49 @@ CrateDB Python developer guide
 Setup
 =====
 
-Optionally install Python package and project manager `uv`_,
-in order to significantly speed up the package installation::
-
-    {apt,brew,pip,zypper} install uv
-    alias pip="uv pip"
-
-To start things off, bootstrap the sandbox environment::
+Clone the repository::
 
     git clone https://github.com/crate/crate-python
     cd crate-python
-    source bootstrap.sh
-
-This command should automatically install all prerequisites for the development
-sandbox and drop you into the virtualenv, ready for invoking further commands.
-
-
-Running tests
-=============
-
-All tests will be invoked using the Python interpreter that was used when
-creating the Python virtualenv. The test runner is `zope.testrunner`_.
-
-Some examples are outlined below. In order to learn about more details,
-see, for example, `useful command-line options for zope-testrunner`_.
-
-Run all tests::
 
-    poe test
+Setup a virtualenv and install the package::
 
-Run specific tests::
+    python -m venv .venv
+    source .venv/bin/activate
+    python -m pip install --group dev --group docs -e .
 
-    # Select modules.
-    bin/test -t test_cursor
-    bin/test -t client
-    bin/test -t testing
+Or if using `uv`_::
 
-    # Select doctests.
-    bin/test -t http.rst
+    uv venv .venv
+    source .venv/bin/activate
+    uv pip install --group dev --group docs -e .
 
-Ignore specific test directories::
 
-    bin/test --ignore_dir=testing
-
-The ``LayerTest`` test cases have quite some overhead. Omitting them will save
-a few cycles (~70 seconds runtime)::
-
-    bin/test -t '!LayerTest'
-
-Invoke all tests without integration tests (~10 seconds runtime)::
-
-    bin/test --layer '!crate.testing.layer.crate' --test '!LayerTest'
-
-Yet ~60 test cases, but only ~1 second runtime::
+Running tests
+=============
 
-    bin/test --layer '!crate.testing.layer.crate' --test '!LayerTest' \
-        -t '!test_client_threaded' -t '!test_no_retry_on_read_timeout' \
-        -t '!test_wait_for_http' -t '!test_table_clustered_by'
+Ensure the virtualenv is active and run tests using `pytest`_::
 
-To inspect the whole list of test cases, run::
+    python -m pytest
 
-    bin/test --list-tests
 
-The CI setup on GitHub Actions (GHA) provides a full test matrix covering
-relevant Python versions. You can invoke the software tests against a specific
-Python interpreter or multiple `Python versions`_ on your workstation using
-`uv`_, by supplying the ``--python`` command-line option, or by defining the
-`UV_PYTHON`_ environment variable prior to invoking ``source bootstrap.sh``.
+See also:
 
-*Note*: Before running the tests, make sure to stop all CrateDB instances which
-are listening on the default CrateDB transport port to avoid side effects with
-the test layer.
+- `How to invoke pytest <https://docs.pytest.org/en/stable/how-to/usage.html>` for more information.
 
 
 Formatting and linting code
 ===========================
 
-To use Ruff for code formatting, according to the standards configured in
-``pyproject.toml``, use::
-
-    poe format
-
-To lint the code base using Ruff and mypy, use::
+Use `ruff`_ for code formatting and linting::
 
-    poe lint
+    ruff format --check .
+    ruff check .
 
-Linting and software testing, all together now::
 
-    poe check
+Use ``mypy`` for type checking::
 
+    mypy
 
 Renew certificates
 ==================
@@ -147,7 +101,7 @@ Writing documentation
 
 The docs live under the ``docs`` directory.
 
-The docs are written written with ReStructuredText_ and processed with Sphinx_.
+The docs are written with ReStructuredText_ and processed with Sphinx_.
 
 Build the docs by running::
 
@@ -171,4 +125,4 @@ nothing special you need to do to get the live docs to update.
 .. _uv: https://docs.astral.sh/uv/
 .. _UV_PYTHON: https://docs.astral.sh/uv/configuration/environment/#uv_python
 .. _versions hosted on ReadTheDocs: https://readthedocs.org/projects/crate-python/versions/
-.. _zope.testrunner: https://pypi.org/project/zope.testrunner/
+.. _pytest: https://docs.pytest.org/en/stable/

bin/test

@@ -1,5 +1,5 @@
 [build-system]
-requires = ["hatchling >= 1.26", "versioningit"]
+requires = ["hatch", "hatchling", "versioningit"]
 build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.sdist]
@@ -26,7 +26,7 @@ name = "crate"
 dynamic = ["version"]
 description = "CrateDB Python Client"
 authors = [{ name = "Crate.io", email = "office@crate.io" }]
-requires-python = ">=3.10"
+requires-python = ">=3.6"
 readme = "README.rst"
 license = "Apache-2.0"
 classifiers = [
@@ -35,34 +35,45 @@ classifiers = [
         "Operating System :: OS Independent",
         "Programming Language :: Python",
         "Programming Language :: Python :: 3",
+        "Programming Language :: Python :: 3.6",
+        "Programming Language :: Python :: 3.7",
+        "Programming Language :: Python :: 3.8",
+        "Programming Language :: Python :: 3.9",
         "Programming Language :: Python :: 3.10",
         "Programming Language :: Python :: 3.11",
         "Programming Language :: Python :: 3.12",
         "Programming Language :: Python :: 3.13",
         "Programming Language :: Python :: 3.14",
         "Programming Language :: Python :: Implementation :: CPython",
         "Programming Language :: Python :: Implementation :: PyPy",
+        "Programming Language :: SQL",
         "Topic :: Database",
+        "Topic :: Internet :: WWW/HTTP",
+        "Topic :: Scientific/Engineering :: Interface Engine/Protocol Translator",
+        "Topic :: System :: Networking",
 ]
 dependencies = [
     "importlib-metadata; python_version<'3.8'",
-    "orjson>=3.11.3",
+    "orjson",
     "urllib3",
     "verlib2>=0.3.1",
 ]
 
 [dependency-groups]
 dev = [
-    "certifi>=2025.10.5",
+    "backports.zoneinfo<1; python_version<'3.9'",
+    "certifi",
     "coverage<8",
     "mypy<1.20",
-    "poethepoet<1",
     "pytest<10",
-    "pytz>=2025.2",
+    "pytz",
     "ruff<0.15",
-    "setuptools>=80.9.0",
     "stopit<1.2",
 ]
+docs = [
+    "sphinx",
+    "crate-docs-theme",
+]
 
 
 [tool.coverage.run]
@@ -185,37 +196,3 @@ lint.per-file-ignores."src/crate/client/{connection.py,http.py}" = [
 lint.per-file-ignores."tests/client/test_http.py" = [
     "A004", # Import `ConnectionError` is shadowing a Python builtin
 ]
-
-
-# ===================
-# Tasks configuration
-# ===================
-
-[tool.poe.tasks]
-
-check = [
-  "lint",
-  "test",
-]
-
-format = [
-  { cmd = "ruff format ." },
-  # Configure Ruff not to auto-fix (remove!):
-  # unused imports (F401), unused variables (F841), `print` statements (T201), and commented-out code (ERA001).
-  { cmd = "ruff check --fix --ignore=ERA --ignore=F401 --ignore=F841 --ignore=T20 --ignore=ERA001 ." },
-]
-
-lint = [
-  { cmd = "ruff format --check ." },
-  { cmd = "ruff check ." },
-  { cmd = "mypy" },
-]
-
-test = [
-  { cmd = "coverage erase" },
-  { cmd = "coverage run -m pytest" },
-  { cmd = "coverage run bin/test" },
-  { cmd = "coverage combine" },
-  { cmd = "coverage xml" },
-  { cmd = "coverage report" },
-]