With rye {root:uri}/../../packages/ seems to traverse more than 2 folders up

[ShravanSunder]

i'm trying to use rye sync with a python monorepo and root:uri

the resolution of folders doesn't seem to work. for example

    "askluna-dotenv @ {root:uri}/../../packages/dotenv" => error: Distribution not found at: file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/packages/dotenv
error: could not write production lockfile for workspace

    "askluna-dotenv @ {root:uri}/../packages/dotenv" =>error: Distribution not found at: file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/askluna/apps/packages/dotenv

So for some reason, ../../ seems to traverse by more than 2 folders up instead of exactly 2 folders. And ../ only traverses 1 folder up

related to astral-sh/uv#4321

[ofek]

Does the parent modifier work for you? https://hatch.pypa.io/latest/config/context/#global-fields

[ShravanSunder]

its very interesting. i'm not sure which part of the rye tool chain has an impact

• "askluna-dotenv @ {root:parent:uri}/../packages/dotenv",
  • Works ✅
• "askluna-dotenv @ {root:parent:uri}/packages/dotenv",
  • does not work ❌
  • file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/askluna/%7Broot:parent:uri%7D/packages/dotenv
• "askluna-dotenv @ {root:parent:uri}/./packages/dotenv"
  • does not work ❌
  • file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/askluna/%7Broot:parent:uri%7D/packages/dotenv

So i partly have a solution, but i find this preplexing.

maybe related issues:

• rye add --path failed astral-sh/rye#168
• Enables explicit root setting for [tool.rye.workspace] table astral-sh/rye#1023

[ofek]

Anything to do here or can this be closed?

[ShravanSunder]

Well I’m unsure if this uri feature works as I mentioned above, however perhaps I just don’t understand the behaviour. You can close it if you like.

[ofek]

Does it work for you outside of Rye?

[ShravanSunder]

i actually don't use hatch aside from rye. feel free to close it if you'd like!

[cjames23]

Closing out old issues that have not had any movement. If you still think this should be addressed please create a new issue. We apologize for the churn as we try to get our issues into a cleaner slate state for going forward with development.