-
Notifications
You must be signed in to change notification settings - Fork 7
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
chore(setup): add python package basic structure #1
Conversation
venv3: ### Creates a virtual environment for this project | ||
test -d $(VENV) || $(PYTHON) -m venv $(VENV) && source $(VENV)/bin/activate | ||
$(PIP) install --upgrade pip | ||
$(PIP) install -e ".[dev,test]" |
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.
honestly, i would kill the venv stuff, personally speaking i'm using conda and i feel more control using conda rather then venv.
for a public, it can feel like we are forcing this.
although, it doesn't hurt anyone 😂 so
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.
up to what the others decide
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.
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.
The problem I see is that venv
is still way more conda
which might make it easier for most people to install the SDK using the makefile.
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.
Yes, I also agree with @aquemy , at least for now
No description provided.