Context Navigation

Changes between Initial Version and Version 1 of Ticket #68218, comment 4

initial	v1
3	3	I looked into how Pre-commit uses it and it seems like it's a gray area. They do only use it as a CLI tool, but they take pains to ensure that it always runs with the same Python executable as Pre-commit itself: https://github.com/pre-commit/pre-commit/blob/84f91646bbfb38cd58d56a0f192a05d42b9cdab5/pre_commit/languages/node.py#L86
4	4
5		Therefore Nodeenv itself is only ever used as a CLI tool, but the way they're using it, it does look like you do need the version-specific subports. So yes, it sounds like my request isn't actually a good idea.
	5	Therefore Nodeenv itself is only ever used as a CLI tool, but the way they're using it, it does look like you do need the version-specific subports. So yes, it sounds like my request isn't actually a good idea. I don't know if there's a Trac feature to mark this ticket as closed/wontfix, but feel free to do so.
6	6
7	7	However, a nodeenv_select package might be nice to provide a plain `nodeenv` executable without the version suffix.