PiPTool | Picture Functionality to YouTube , Netflix , Plex

The error comes from pip-tools trying to access the editable attribute on the class ParsedRequirement, whereas the correct attribute name on that class is is_editable. With previous versions of pip, the object at ireq were of type InstallRequirement, which does have the attribute editable.

Try pip==20.0.2; that seems to be the last version that returned InstallRequirement instead of ParsedRequirement from the relevant method (parse_requirements).

Does your project directory contain a docker-compose.yml, a Dockerfile, and a requirements.txt file? If so, then the following steps might help.

Open your requirements.txt. You should see all of the python project dependencies listed here. For example, it might look like this initially:

This is something I also noticed with the BigSur updates. Although there is an active issue for this on GitHub, a work around for the time being is to run the following command before you attempt to lock your Pipfile or install any packages. Note: this will only be effective in the terminal you run this command in.

you may want to provide more information to make people answer your question easier, and there are some of example and suggestion shown below.

1. The statement "This is likely caused by a bug in google-ads. Report this to its maintainers." is raised by pipenv. It means "please do not report the issue to pipenv development team".

2. Don't rush to claim that you have found a bug: this is a suggestion from "How To Ask Questions The Smart Way" by Eric Steven Raymond. You may check the link for more details about why. Thus, I will suggest you to investigate your operation first instead of contacting with Google Ads.

3. It seems that you are running the command on a mac/OSX. Besides, it seems that your pipenv is installed by brew. If both of the statements are right, then it is very likely that you are mixing your system-wise pip and local-installed pipenv (by brew). This is a very frequent mistake raised by people who are not familiar with how python package management works.

   1. Thus, the first suggestion to find a solution, is to elaborate the python package management related information on your system (mac/OSX) as much as possible. For example, the output message of python --version, which python, which pip, and which pipenv is usually help.

   2. If you want to use brew to manage packages for you, make sure every step you used to install pipenv and your target package does not mix your system-wise python environment and your local(managed by brew or a python virtual environment) when trying to figure out the issue and finding a solution. For example, make sure you are starting your operation from a "clean" and just-re-spawned terminal. If you want to use brew, make sure you are controlling everything via brew. It will be a bad idea to activate a customized python virtual environment (e.g. conda environment) and then using brew.

   3. I expect people could not provide you other more practical solution suggestions until more information is provided. Good luck.

Make sure the version of your pip and setuptools is sufficient for manylinux2014 wheels.

I resolved this using this thread: https://github.com/pypa/pipenv/issues/3468

The general consensus was that pipenv was not supporting 3.8.1, I have since downgraded to 3.7.6 and will use that until support is given.