pip: 22.1.2 -> pip-22.2.1

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?

[groodt]

Updates pip from 22.1.2 to 22.2.1. See Changelog. This version is backwards compatible and no new functionality is introduced to the rules.

---

Something to keep an eye on is that an experimental feature has been added to prepare an "installation report".
pip install --dry-run --ignore-installed --report

This approximates lock-file-like functionality, however, the maintainers explicitly mention that it is not intended to be a lock-file and it is experimental functionality. Even so, it may enable us to remove a dependency on pip-tools at some stage. This would be nice because it could eventually strip the rules back to only the Python standard library and pip. Or it could become the bones of a custom resolver.

[alexeagle]

Sure, I think we should periodically bump our dependencies to latest.

FWIW if we did go down the path of a custom resolver, I'd hope we could re-use someone elses (like the one in Pants) rather than actually write one

[hrfuller]

(like the one in Pants)

Which resolver are you referring to? AFAIK PEX is used to build python distributions in pants, and PEX subprocesses out to pip to do resolves. Is there another place where python resolves are done in a custom way?