Eryk Sun <eryk...@gmail.com> added the comment:
> For this issue, the PATH conflict would be that "pip" and "python" > refer to different Python installs. I'm aware of the problem for a per-user installation prior to 3.10. However, none of the install commands use the "--user" option, else I would have suggested it. That said, it wouldn't surprise me that I overlooked something, or multiple things, since packaging is my weakest area. > Visual Studio Developer Console, which overrides pip's platform > detection making it think that it's a 32-bit runtime Why did you change the issue status back to "open"? By marking it as pending, I was trying to encourage getting help on forums first. If the "more likely" explanation that you suggest is the case, then the problem likely would have been recognized in forums, or probably referred to pip's issue tracker. The first impulse shouldn't be to create an issue on CPython's issue tracker to "solve this problem" for a configuration or coding problem that can't be resolved on one's own. I see novices doing this occasionally because they aren't aware yet of the other support channels that are available to them. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44147> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
