Minor changes to fix uv sync

[oerc0122]

This seems to fix the uv sync issues and should be fully portable.

Issues:

• Test on different setups
• Whether to remove duplicate test group/dep.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
4358	4279	98%	0%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 134da71 by action🐍

[github-actions]

Test Results

   22 files   -     25     22 suites   - 25   19m 58s ⏱️ - 28m 30s
1 118 tests ±     0  1 112 ✅ ±     0   6 💤 ± 0  0 ❌ ±0 
9 975 runs   - 16 609  9 918 ✅  - 16 519  57 💤  - 90  0 ❌ ±0 

Results for commit 134da71. ± Comparison against base commit 9a15150.

♻️ This comment has been updated with latest results.

[ajjackson]

I'm still running into trouble here. Do you have suggested incantation to use this in a clean environment?

FROM python:3.14

RUN pip install uv

RUN git clone --branch fix-uv-sync --single-branch https://github.com/pace-neutrons/euphonic.git /opt/

WORKDIR /opt/euphonic

# This would be nice
# RUN uv sync
# RUN uv sync --upgrade

# But even this is failing
RUN bash -c 'uv venv && source .venv/bin/activate && uv sync --active --no-editable'
RUN bash -c  'source .venv/bin/activate && uv sync --active --no-editable --upgrade'

[ajjackson]

Making a record from side chat: the problem seems to be the dynamic versioning which causes an editable install. If that is removed, things work:

FROM python:3.14

RUN pip install uv

RUN git clone --branch fix-uv-sync --single-branch https://github.com/pace-neutrons/euphonic.git /opt/euphonic

WORKDIR /opt/euphonic

RUN ls /opt && pwd && ls .
RUN sed -i 's/dynamic = \["version"\]//' pyproject.toml
RUN sed -i 's/name = "Euphonic"/name = "Euphonic"\nversion = "1.8.0"/' pyproject.toml
RUN cat pyproject.toml

RUN uv sync
RUN uv sync --upgrade

But we like the dynamic versioning because it means we can tell if a JSON dump came from a development build between full version tags.

[ajjackson]

This uv issue was the hint we needed, to understand "why" editable builds were running even when under --no-editable astral-sh/uv#10996