refactor: remove .python-version file and update README for clarity

Author: tlambert03

.python-version

@@ -6,12 +6,17 @@
 [![CI](https://github.com/pymmcore-plus/pymmcore-nano/actions/workflows/ci.yml/badge.svg)](https://github.com/pymmcore-plus/pymmcore-nano/actions/workflows/ci.yml)
 [![codecov](https://codecov.io/gh/pymmcore-plus/pymmcore-nano/branch/main/graph/badge.svg)](https://codecov.io/gh/pymmcore-plus/pymmcore-nano)
 
-Experimental python bindings for [CMMCore](https://github.com/micro-manager/mmCoreAndDevices)
-(the device abstraction layer for micro-manager) using [nanobind](https://nanobind.readthedocs.io/en/latest/).
-
-This package can be used as a (mostly) drop-in replacement for [`pymmcore`](https://pypi.org/project/pymmcore/).
-There are a few slight differences in behavior.  You are encouraged to try it where you might use
-pymmcore; and [let us know](https://github.com/pymmcore-plus/pymmcore-nano/issues) if you run into any issues!
+Experimental python bindings for
+[CMMCore](https://github.com/micro-manager/mmCoreAndDevices) (the device
+abstraction layer for micro-manager) using
+[nanobind](https://nanobind.readthedocs.io/en/latest/) instead of SWIG.
+
+This package can be used as a drop-in replacement for
+[`pymmcore`](https://pypi.org/project/pymmcore/). There are a few slight
+differences in behavior.  You are encouraged to try it where you might use
+pymmcore; and [let us
+know](https://github.com/pymmcore-plus/pymmcore-nano/issues) if you run into any
+issues!
 
 ## Installation
 
@@ -33,45 +38,45 @@ For example, the version `11.3.0.71.2` refers to:
 
 - MMCore version 11.3.0
 - Device interface 71
-- pymmcore-nano build number of 2 (this is a zero indexed version that resets each time
-the MMCore or Device Interface versions increment)
+- pymmcore-nano build number of 2 (this is a zero indexed version that resets
+  each time the MMCore or Device Interface versions increment)
 
 ## For Developers
 
 ### Clone repo
 
 ```sh
 git clone https://github.com/pymmcore-plus/pymmcore-nano.git
-git submodule update --init
+cd pymmcore-nano
 ```
 
 ### Setup dev environment (editable install)
 
-Make sure you have uv installed: <https://docs.astral.sh/uv/getting-started/installation/>
+Make sure you have uv installed:
+<https://docs.astral.sh/uv/getting-started/installation/>
 
-This project uses `just` as a task runner.
-If you have `just` installed (e.g. `brew install just`), you can fully setup the project with:
+This project uses `just` as a task runner. If you have `just` installed (e.g.
+`brew install just`), you can fully setup the project with:
 
 ```sh
 just install
 ```
 
-If you prefer not to install `just` globally, you can install it with the rest of the
-project dependencies using uv.  Then activate the environment and call `just install`
+If you prefer not to install `just` globally, you can install it with the rest
+of the project dependencies using uv.  Then activate the environment and call
+`just install`
 
 ```sh
 uv sync --no-install-project
 . .venv/bin/activate  # Windows: .venv\Scripts\activate
 just install
 ```
 
-This repo contains a few device adapters that are useful for testing,
-in src/mmCoreAndDevices/DeviceAdapters.  These adapters are built as a part of the
-installation.  
-
-On windows, in order to build the SequenceTester device (optional) you will also
-need boost installed (e.g. `choco install boost-msvc-14.3`, or similar version
-according to your version of visual studio)
+Note that one of the dev dependencies is
+[`mm-test-adapters`](https://pypi.org/project/mm-test-adapters/), this brings in
+a few device adapters that are useful for testing purposes. (The version of
+`mm-test-adapters` should match the device interface version you are building
+against.)
 
 ### Test
 
@@ -96,27 +101,12 @@ To release a new version:
 - commit changes to main
 - run `just release`
 
-### Updating `mmCoreAndDevices` source code
-
-Rather than using git submodules, this repository checks in the
-[`mmCoreAndDevices`](https://github.com/micro-manager/mmCoreAndDevices) source
-code. This makes measuring C++ code coverage easier, as the `mmCoreAndDevices`
-code is included in the same repository (see codecov results
-[here](https://app.codecov.io/gh/pymmcore-plus/pymmcore-nano/tree/main/src%2FmmCoreAndDevices)),
-and it also makes it easier to make changes to the `mmCoreAndDevices` code
-directly from this repository (e.g., to fix bugs or add features that are
-pending in the upstream repo).
+### Updating `MMCore` and `MMDevice`
 
-To bring in new changes from the upstream `mmCoreAndDevices` repository, you can
-run:
-
-```python
-python scripts/update_sources.py
-```
+The versions of `MMCore` and `MMDevice` that this project builds against are
+pinned in the `subprojects/mmcore.wrap` and `subprojects/mmdevice.wrap` files,
+respectively.  To build against a new version, update the `revision` field in
+the appropriate wrap file and re-run `just install`.
 
-After updating, you can test the build and python code as usual.
-
-```sh
-just build
-pytest
-```
+For version changes that bump the Device Interface version, you will also want
+to update the version of `mm-test-adapters` in the `pyproject.toml` file.

README.md

@@ -2,6 +2,6 @@ gcov-ignore-parse-errors = negative_hits.warn
 exclude-throw-branches = yes
 html-theme = github.green
 print-summary = yes
-filter = src/mmCoreAndDevices/MMCore/MMCore.cpp
+filter = subprojects/mmcore/MMCore.cpp
 exclude-lines-by-pattern = .*(LOG_ERROR|CMMError).*
 exclude-noncode-lines = yes

gcovr.cfg

@@ -60,9 +60,6 @@ version:
 check:
 	pre-commit run --all-files --hook-stage manual
 
-pull-mmcore:
-	git subtree pull --prefix=src/mmCoreAndDevices https://github.com/micro-manager/mmCoreAndDevices main --squash
-
 # MUST run just version and commit changes before.
 release:
 	git branch --show-current | grep -q main || (echo "Not on main branch" && exit 1)