pip

Issue description

When the environment variable PIPENV_SITE_PACKAGES is set, pipenv always recreate new virtualenv on each invoke of pipenv even if it is not a pipenv install command.

Expected result

• pipenv run or pipenv shell should use existing virtualenv instead of creating a new one.
• PIPENV_SITE_PACKAGES should only affect pipenv install command.

Actual

Would it make sense to have a logger.debug (or logger.info/warning) call here mentioning that the version couldn't be parsed ?

Originally posted by @xavfernandez in pypa/pip#10117 (comment)

Yes, let's do a warning. :)

This is a Good First Issue to fix the following typos

./video_to_ascii/cli.py:8: usefull ==> useful
./video_to_ascii/render_strategy/ascii_strategy.py:72: correcly ==> correctly
./video_to_ascii/render_strategy/ascii_strategy.py:72: builded ==> built
./video_to_ascii/render_strategy/image_processor.py:1: usefull ==> useful
./video_to_ascii/render_strategy/image_processor.py:14: apropia

pipupgrade --verbose (0|1|2..) for info, warning, error, etc.

@fcakyon I have trained and YOLOV4 model using AlexyAB's repo and I have generated a weight file for my custom dataset which was sliced using your repo. Now I want to check the test results for predicted YOLOV4 results. How can I integrate YOLOV4 weight file to your test folder so that I can use the YOLOV4 like you have used the YOLOV5 model which was from from ultralytics repo.