➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kumaraditya
Recipients Crowthebird, kumaraditya, malin, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-11-30.16:42:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALQaJgnBY7RUQm0=L6SrvMx+ZKEpZXFCsG86_W3Y3OZ6NjKxkA@mail.gmail.com>
In-reply-to <1638286765.57.0.460965629941.issue45816@roundup.psfhosted.org>
Content 
Thanks Steve, installing v142 is indeed my current workaround but would be
great to support v143 as it is the latest version.

On Tue, Nov 30, 2021, 21:09 Steve Dower <report@bugs.python.org> wrote:

>
> Steve Dower <steve.dower@python.org> added the comment:
>
> An easy workaround for people encountering this is to set the
> PlatformToolset environment variable to v143 before building:
>
> $env:PlatformToolset = "v143"
>
> (or in CMD: set PlatformToolset=v143)
>
> Alternatively, you should be able to install the v142 toolset through VS
> 2022. For now, it's still the official toolset, though we'll definitely
> move to v143 before 3.11.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue45816>
> _______________________________________
>
History
Date User Action Args
2021-11-30 16:42:42kumaradityasetrecipients: + kumaraditya, paul.moore, tim.golden, zach.ware, steve.dower, malin, Crowthebird
2021-11-30 16:42:42kumaradityalinkissue45816 messages
2021-11-30 16:42:42kumaradityacreate