ip-tools | ip range , cidr , netmask functions | TCP library

It is a bug, you can downgrade using:

pip install "pip<22"

https://github.com/jazzband/pip-tools/issues/1558

Generally, this kind of error is emitted (as far as I saw it several times) when your setup.cfg or setup.py are broken.

In your case, your extras are not defined properly. You should change your setup.cfg like the following:

Can you check pipenv. pipenv uses Pipfile and Pipfile.lock for dependencies instead of requirements.txt. It has a clear separation between the dependencies you install and the dependencies of the dependencies.

check this sample below it is much clearer:

My workflow avoids pip freeze. It goes:

geopandas 0.10.1

• have noted that your data is on kaggle, so start by sourcing it
• there really is only one issue shapely.geometry.MultiPoint() constructor does not work with a filtered series. Pass it a numpy array instead and it works.
• full code below, have randomly selected a point to serve as gpdPoint

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).

Per https://github.com/dotnet/aspnetcore/issues/6674, there is a bug in MS's Contains implementation for the IPNetwork class. The bug has been fixed, but not yet released. As I read it, it expects the address of the CIDR prefix to be the first address that would come from the CIDR prefix/length.

This means that it doesn't like "10.10.10.1/30" and instead wants "10.10.10.0/30", which does indeed give the expected results.

After digging for a while, I found my answer in another issue:

$ pip-compile --extra testing --extra other

You want to be able to lock down the versions of all of the packages that your Python code depends on in your requirements.txt file. You want this file to include versions for not just the direct dependencies that your code imports directly, but also versions for all of the transitive dependencies as well...that is, the versions of modules that your directly dependent modules themselves depend on.

So the question is...how do you maintain the contents of "requirements.txt"? You can use pip freeze > requirements.txt, but this is messy. It depends not on a clear list of what the direct dependencies of your app are, but rather on what happens to be in your environment at the time of creation. What you really want is to have a file in which you list the direct dependencies of your app, along with versions for each of them, and then somehow produce the appropriate requirements.txt file from that list such that it contains exactly versions for those direct dependencies as well as versions for just the transitive dependencies needed by those direct dependencies.

The requirements.in file and pip-compile together give you this desired behavior. In requirements.in, you list just the direct dependencies of your app. Then you run pip-compile on that file to produce requirements.txt. The compile process will produce what you want...a file that contains both the modules listed in requirements.in and the transitive dependencies of those modules.