by groodt on 11/30/20, 12:53 PM with 223 comments
by dalemyers on 11/30/20, 4:23 PM
by st1x7 on 11/30/20, 1:46 PM
by tgb on 11/30/20, 1:37 PM
> The new resolver now resolves packages in a deterministic order. (https://github.com/pypa/pip/pull/9100)
by muglug on 11/30/20, 2:04 PM
by Chico75 on 11/30/20, 2:13 PM
I'm surprised I never ran into the issue, but I suppose it mainly show up if you have a large number of dependencies?
by cosmic_quanta on 11/30/20, 2:16 PM
https://github.com/pypa/pip/blob/master/.azure-pipelines/scr...
I'm very surprised. Is this common?
by mhxion on 11/30/20, 4:46 PM
by colechristensen on 11/30/20, 4:21 PM
by misnome on 11/30/20, 1:37 PM
by groodt on 11/30/20, 8:17 PM
by Mlller on 11/30/20, 4:01 PM
by devy on 12/1/20, 12:16 AM
by jdeibele on 11/30/20, 8:33 PM
https://pypi.org/project/pip-review/
> pip-review Faker==4.18.0 is available (you have 4.17.1) pip==20.3 is available (you have 20.2.4)
> pip-review --auto --verbose Collecting Faker==4.18.0 Downloading Faker-4.18.0-py3-none-any.whl (1.1 MB) || 1.1 MB 730 kB/s Collecting pip==20.3 Downloading pip-20.3-py2.py3-none-any.whl (1.5 MB) || 1.5 MB 2.0 MB/s Requirement already satisfied: python-dateutil>=2.4 in /usr/local/lib/python3.8/site-packages (from Faker==4.18.0) (2.8.1) Requirement already satisfied: text-unidecode==1.3 in /usr/local/lib/python3.8/site-packages (from Faker==4.18.0) (1.3) Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.8/site-packages (from python-dateutil>=2.4->Faker==4.18.0) (1.15.0) Installing collected packages: Faker, pip Attempting uninstall: Faker Found existing installation: Faker 4.17.1 Uninstalling Faker-4.17.1: Successfully uninstalled Faker-4.17.1 Attempting uninstall: pip Found existing installation: pip 20.2.4 Uninstalling pip-20.2.4: Successfully uninstalled pip-20.2.4 ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
lektor 3.2.0 requires Werkzeug<1, but you'll have werkzeug 1.0.1 which is incompatible. Successfully installed Faker-4.18.0 pip-20.3
by wokwokwok on 11/30/20, 2:40 PM
me: ooo... new shiny toys.
new version of pip comes out. again.
me: :( this will probably break something. again.
I now just tell people to use conda.
by thijsvandien on 11/30/20, 4:55 PM
With this, it's a lot easier to upgrade everything without getting conflicts: pip freeze | cut -d= -f1 | xargs pip install --upgrade.
by dang on 11/30/20, 6:56 PM
by iverjo on 12/4/20, 10:24 AM
by zests on 11/30/20, 3:33 PM
by economusty on 11/30/20, 9:20 PM
by saiadarsh99 on 11/30/20, 5:41 PM
by optimalsolver on 11/30/20, 6:10 PM
Most Python devs don't seem to realize that the packaging problem is now solved: