-
Notifications
You must be signed in to change notification settings - Fork 12
feat: re-install dev package on setup file changes #187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
This change enables tracking changes in setup files so that the dev package can be re-installed if needed, when the -s option is passed to the run command.
@@ -25,6 +26,7 @@ | |||
|
|||
DEFAULT_RIOT_PATH = ".riot" | |||
DEFAULT_RIOT_ENV_PREFIX = "venv_py" | |||
SETUP_FILES = ["setup.py", "pyproject.toml"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setup.cfg
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I think pip
looks for just setup.py
and/or pyproject.toml
, but setup.cfg
should probably be hashed as well, if present 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to add setup.cfg
here? probably a good idea since it can contain install/build requirements
... would that mean we also care about requirements.txt
? or any variation of those?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we just fail instead if -s
is passed and we noticed a change?
what about c-extensions? we would definitely want to rebuild in those cases?
would this become any easier if we removed -s
and made that the default behavior? e.g. riot run <venv>
would only build the base venv if it doesn't exist, otherwise you use riot generate
or can pass in an explicit option like riot run --rebuild
?
@@ -25,6 +26,7 @@ | |||
|
|||
DEFAULT_RIOT_PATH = ".riot" | |||
DEFAULT_RIOT_ENV_PREFIX = "venv_py" | |||
SETUP_FILES = ["setup.py", "pyproject.toml"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to add setup.cfg
here? probably a good idea since it can contain install/build requirements
... would that mean we also care about requirements.txt
? or any variation of those?
@@ -25,6 +26,7 @@ | |||
|
|||
DEFAULT_RIOT_PATH = ".riot" | |||
DEFAULT_RIOT_ENV_PREFIX = "venv_py" | |||
SETUP_FILES = ["setup.py", "pyproject.toml"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SETUP_FILES = ["setup.py", "pyproject.toml"] | |
SETUP_FILES = ["setup.py", "pyproject.toml", "setup.cfg"] |
This change enables tracking changes in setup files so that the dev package can be re-installed if needed, when the -s option is passed to the run command.