error: internal error: accessed dependencies from pyproject.nix project, not uv.lock

[srid]

description

On NixOS, activating direnv leads to:

environment

I'm on NixOS with Nix 2.24.10. Initiated the template like this:

[cameronraysmith]

Many thanks for reporting this @srid. We're using a one-line command directly from the README (or with my global om installation locally via om init) which invokes pytest in the devshell with nix develop rather than including direnv allow there

python-nix-template/README.md

Lines 25 to 40 in 660ec17

	nix --accept-flake-config run github:juspay/omnix -- init github:sciexp/python-nix-template -o pnt-mono --non-interactive --params '{
	"package-name-kebab-case": "pnt-mono",
	"package-name-snake-case": "pnt_mono",
	"monorepo-package": true,
	"git-org": "pnt-mono",
	"author": "Pnt Mono",
	"author-email": "mono@pnt.org",
	"vscode": true,
	"github-ci": true,
	"nix-template": false
	}' && \
	cd pnt-mono && \
	git init && \
	git commit --allow-empty -m "initial commit (empty)" && \
	git add . && \
	nix develop --accept-flake-config -c pytest

Here's the associated CI log:

• https://github.com/sciexp/python-nix-template/actions/runs/14670715797/job/41176408200

There are two issues

1. If you initialize the template for a directory sample, then delete it, and then attempt to initialize the same template in the same directory again, the active direnv state for that directory will not have been revoked (direnv status --> Found RC allowed 0) and will immediately attempt to activate on reentry to that directory. To fix this we need to add a direnv revoke ./sample/ before the command to cd into it to bring the template initialization process closer to precise idempotency. This needs to be updated in the CI template.yaml, README, and in the template welcome message.
2. When initializing the single-package version of the template with "monorepo-package": false we need to make sure we update the uv.lock file before staging it with git add .

We could use (diff with update on RHS)

om init github:sciexp/python-nix-template -o sample --non-int   om init github:sciexp/python-nix-template -o sample --non-int
   "package-name-kebab-case": "sample",                            "package-name-kebab-case": "sample",
   "package-name-snake-case": "sample",                            "package-name-snake-case": "sample",
   "monorepo-package": false,                                      "monorepo-package": false,
   "git-org": "srid",                                              "git-org": "srid",
   "author": "Srid",                                               "author": "Srid",
   "author-email": "srid@srid.ca",                                 "author-email": "srid@srid.ca",
   "vscode": true,                                                 "vscode": true,
   "github-ci": true,                                              "github-ci": true,
   "nix-template": false                                           "nix-template": false
 }' && \                                                         }' && \
                                                              >  direnv revoke ./sample/ && \
 cd sample && \                                                  cd sample && \
 git init && \                                                   git init && \
 git commit --allow-empty -m "initial commit (empty)" && \       git commit --allow-empty -m "initial commit (empty)" && \
                                                              >  nix run github:NixOS/nixpkgs/nixos-unstable#uv -- lock && \
 git add . && \                                                  git add . && \
 nix develop --accept-flake-config -c pytest                  |  direnv allow && \
                                                              >  eval "$(direnv export $(basename $SHELL))" && \
                                                              >  pytest

but it's a bit ugly and confusing to require the eval and thus seems to make more sense to keep the execution of pytest in the devshell via nix develop

om init github:sciexp/python-nix-template -o sample --non-interactive --params '{
   "package-name-kebab-case": "sample",
   "package-name-snake-case": "sample",
   "monorepo-package": false,
   "git-org": "srid",
   "author": "Srid",
   "author-email": "srid@srid.ca",
   "vscode": true,
   "github-ci": true,
   "nix-template": false
 }' && \
 (command -v direnv >/dev/null 2>&1 && direnv revoke ./sample/ || true) && \
 cd sample && \
 git init && \
 git commit --allow-empty -m "initial commit (empty)" && \
 nix run github:NixOS/nixpkgs/nixos-unstable#uv -- lock && \
 git add . && \
 nix develop --accept-flake-config -c pytest && \
 echo "Run 'direnv allow' to activate the nix devshell with direnv"

and leave it to the user to run direnv allow if they would like to do so.
This version of the command you used addresses both of the issues above.

Added a slightly modified version of this in

• fix(docs): account for instantiation in dirs with active direnv state #38

[cameronraysmith]

Incidentally noted potential for confusion regarding the template string replacement of one of the cache names in

• template string replacement overwrites the cachix cache name assuming user has already created one for their template instance #36

when reviewing this.

[cameronraysmith]

Feel free to reopen if #38 and the discussion above didn't resolve this for you.