-
Notifications
You must be signed in to change notification settings - Fork 27
[updates] specify python version #2933
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: main
Are you sure you want to change the base?
Conversation
|
@arc64 this about the python version, btw |
fc5ebad to
ce4216b
Compare
hom3mad3
left a comment
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.
Nice!
m4ra
left a comment
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.
I would argue for writing a project.toml in the adhocracy-4 library and define the python version there, instead of constraining how developers should setup their virtualenv. Having a project.toml is also the standard fashion of publishing packages.
| @@ -0,0 +1 @@ | |||
| 3.11.6 No newline at end of file | |||
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.
Personally I use pyenv for versions, and pyenv for virtualenv, so this file points to the name of my pyenv's virtualenv, e.g named root which is located in .pyenv/versions/(venv) and that's why cannot be deleted with the make clean command. Hence, I don't think the solution here is inclusive enough approach.
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.
Could you say a little more? The make install command uses python3 -m venv $(VIRTUAL_ENV); so our clean script deletes this venv. What additional behavior would you expect?
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.
I create virtuanvs with pyenv virtualenv <name-of-venv> for all my projects, which places venvs in the home directory of /home/<user>/.pyenv/versions/<name-of-venv>
you bring some good points and i haven't really tried it myself. .python-version defaults my version in case i forget, so that is already quite helpful. |
|
with a docker build this should also be fixed tbh 🙈 |
If a developer is using pyenv, a new
.python-versionfile will force them onto the latest supported version.If not, they can now see in the README the supported version. Additionally, if they are on a non-supported version, when running
make installan warning will be printed to the console.@m4ra you mentioned
make cleandoesn't remove the venv directory when using pyenv, but it seems to be. Maybe this is no longer happening. If there are other issues with pyenv we could smooth out, maybe now would be a good time though, so let me know.edit: also added a note in README that macOS users will need to install libmagic