RE: requirements.txt

Hey I just figured it out. I ran requirements.txt before running "pip freeze > requirements.txt"

 

 

Sent from Mail for Windows 10

 

From: Mike Dewhirst
Sent: Thursday, 25 February 2021 23:21
To: django-users@googlegroups.com
Subject: Re: requirements.txt

 

On 25/02/2021 8:38 pm, Spence Buzz wrote:

> Hello

> I'm new to django and I've just finished my first website.

> After pushing my project to github, I decided to take it live through

> my host's cpanel.

> At the "Run Pip Install" button I encounter the below error:

> 

> Error

> ERROR: Could not install packages due to an OSError: [Errno 2] No such

> file or directory: '/tmp/build/80754af9/attrs_1604765588209/work'

 

Pip is clever enough to install from many places but when using the

requirements.txt approach, the named items must exist in the PyPI

ecosystem or in a named local file.

 

I have never used attrs @

file:///tmp/build/80754af9/attrs_1604765588209/work in a requirements

file because I didn't know about @ semantics in pip. It is new. To me.

 

If I encountered that problem I would replace such lines with just the

name of the package and let pip go find them.

 

> 

> my requirements.txt file looks like this:

> 

> asgiref==3.3.1

> atomicwrites==1.4.0

> attrs @ file:///tmp/build/80754af9/attrs_1604765588209/work

> certifi==2020.12.5

> chardet==4.0.0

> colorama @ file:///tmp/build/80754af9/colorama_1607707115595/work

> Django==3.1.5

> djangorestframework==3.12.2

> idna==2.10

> importlib-metadata @

> file:///tmp/build/80754af9/importlib-metadata_1602276842396/work

> iniconfig @ file:///home/linux1/recipes/ci/iniconfig_1610983019677/work

> more-itertools @

> file:///tmp/build/80754af9/more-itertools_1613676688952/work

> packaging @ file:///tmp/build/80754af9/packaging_1611952188834/work

> pluggy==0.12.0

> py @ file:///tmp/build/80754af9/py_1607971587848/work

> pyparsing @ file:///home/linux1/recipes/ci/pyparsing_1610983426697/work

> pytest==6.2.2

> pytz==2020.5

> requests==2.25.1

> six @ file:///C:/ci/six_1605205404068/work

> sqlparse==0.4.1

> toml @ file:///tmp/build/80754af9/toml_1592853716807/work

> urllib3==1.26.3

> wincertstore==0.2

> zipp @ file:///tmp/build/80754af9/zipp_1604001098328/work

> 

> 

> 

> Please help

> 

> 

> --

> You received this message because you are subscribed to the Google

> Groups "Django users" group.

> To unsubscribe from this group and stop receiving emails from it, send

> an email to django-users+unsubscribe@googlegroups.com

> <mailto:django-users+unsubscribe@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/django-users/721f8f00-f630-4495-8e07-35da0de6292bn%40googlegroups.com

> <https://groups.google.com/d/msgid/django-users/721f8f00-f630-4495-8e07-35da0de6292bn%40googlegroups.com?utm_medium=email&utm_source=footer>.

 

 

--

Signed email is an absolute defence against phishing. This email has

been signed with my private key. If you import my public key you can

automatically decrypt my signature and be sure it came from me. Just

ask and I'll send it to you. Your email software can handle signing.

 

 

--

You received this message because you are subscribed to a topic in the Google Groups "Django users" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/1w5ITzne2FA/unsubscribe.

To unsubscribe from this group and all its topics, send an email to django-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/784ced4f-d1b1-a51e-2cba-5b8a11b87ea6%40dewhirst.com.au.