#i'm having some trouble with

1 messages · Page 1 of 1 (latest)

wind fox
#

probably not, re-create the environment and try again

#

metadata is not dynamic so updates wouldn't be picked up automatically

fluid sun
#

is there another way to reset envs?

wind fox
#

hatch env prune

fluid sun
#

that did it, thanks

wind fox
#

np

fluid sun
#

is there a way to tell the env to clean before running any scripts? it's a bit inconvenient to have to execute hatch env prune after making any change

wind fox
#

to be clear, what do you mean by scripts?

warm wren
#

i believe the ask is to have tox-alike behaviour of reinstall before run

fluid sun
#

i'm using the scikit-build-core plugin, so i can't use editable installs

wind fox
#

when you say scripts do you mean project metadata or environment scripts? just to confirm

fluid sun
wind fox
#

those are always available and reflect changes you have made

fluid sun
#

you have to hatch env prune first

wind fox
#

okay then you aren't talking about environment scripts but rather project.scripts

fluid sun
#

i'm using the hatch-test env

#

is there something blatantly wrong with this configuration?

[envs.hatch-test]
features = ["full"]
dev-mode = false
dependencies = [
    "coverage",
    "pytest",
    "pytest-memray",
    "pytest-asyncio",
]
platforms = ["linux", "macos"]

[envs.hatch-test.overrides]
platform.windows.dependencies = [
    "coverage",
    "pytest",
    "pytest-asyncio",
]
wind fox
#

also note that, as Ronny mentioned, what you actually want is an option to reinstall every time

#

the dev-mode actually even if true is not updating your extension

fluid sun
#

ok, what should i do?

wind fox
#

I suppose you could add a script that invokes pip install and then does whatever you actually want

fluid sun
#

i'll try that. could a reinstall feature be added in future?

wind fox
#

there is an open request for that

fluid sun
#

can you link the issue, so i can watch it :)