@@ -1438,22 +1438,27 @@ install x y`` in a single command. We would like your thoughts on what
1438
1438
pip's behavior should be; please answer `our survey on upgrades that
1439
1439
create conflicts `_.
1440
1440
1441
- We are also changing our support for :ref: `Constraints Files ` and
1442
- related functionality. We did a fairly comprehensive overhaul and
1443
- stripped constraints files down to being purely a way to specify
1444
- global (version) limits for packages. Specifically:
1441
+ We are also changing our support for :ref: `Constraints Files `,
1442
+ editable installs, and related functionality. We did a fairly
1443
+ comprehensive overhaul and stripped constraints files down to being
1444
+ purely a way to specify global (version) limits for packages, and so
1445
+ some combinations that used to be allowed will now cause
1446
+ errors. Specifically:
1445
1447
1446
1448
* Constraints don't override the existing requirements; they simply
1447
1449
constrain what versions are visible as input to the resolver (see
1448
1450
:issue: `9020 `)
1449
-
1450
1451
* Providing an editable requirement (``-e . ``) does not cause pip to
1451
- ignore version specifiers or constraints (see :issue: `8076 `)
1452
-
1452
+ ignore version specifiers or constraints (see :issue: `8076 `), and if
1453
+ you have a conflict between a pinned requirement and a local
1454
+ directory then pip will indicate that it cannot find a version
1455
+ satisfying both (see :issue: `8307 `)
1453
1456
* Hash-checking mode requires that all requirements are specified as a
1454
- `== ` match on a version and may not work well in combination with
1457
+ `` == ` ` match on a version and may not work well in combination with
1455
1458
constraints (see :issue: `9020 ` and :issue: `8792 `)
1456
-
1459
+ * If necessary to satisfy constraints, pip will happily reinstall
1460
+ packages, upgrading or downgrading, without needing any additional
1461
+ command-line options (see :issue: `8115 ` and :doc: `development/architecture/upgrade-options `)
1457
1462
* Unnamed requirements are not allowed as constraints (see :issue: `6628 ` and :issue: `8210 `)
1458
1463
* Links are not allowed as constraints (see :issue: `8253 `)
1459
1464
* Constraints cannot have extras (see :issue: `6628 `)
0 commit comments