Closed littlewhitecloud closed 1 year ago
I'm wondering though, whether we need requiremente.txt
at all.
LOL I forget pygments too.
I'm wondering though, whether we need
requirements.txt
at all.
requirements.txt
is in need, for someone who wants to make a contribution.
And then can do
pip install -r requirements.txt
To quick install the require libs in need.
For development I recommend this
python3 -m venv env
source env/bin/activate
pip install -e .
(it's a bit different on Windows)
This will install chlorophyll as editable using the setup.py
, so there's no need for the requirements.txt
That's fine, but I prefer to execute pip install -r requirements.txt
and edit on the current path.
(Maybe someone who like me never hear about pip install -e .
will use pip install -r requirements.txt
.)
So we don't need requirements.txt
now?
I honestly do it the same way as white cloud. Not my repo though :).
I honestly do it the same way as white cloud. Not my repo though :).
LOL I was afraid only I didn’t know the command.
@rdbende Whether to delete or not, it's up to you to decide
I honestly do it the same way as white cloud. Not my repo though :).
But in a venv?
So we don't need requirements.txt now?
Let's keep it
Really a good project, but it seems that the
requirements.txt
losttoml
. @rdbende Can you check it out?