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