# Consider downgrading Windows 32-bit from Tier-1 to Tier-2 or Tier-3? (in Python 3.13?)

**URL:** <https://discuss.python.org/t/consider-downgrading-windows-32-bit-from-tier-1-to-tier-2-or-tier-3-in-python-3-13/33719>\
**Category:** Core Development\
**Created:** [September 14, 2023, 10:43am UTC](https://discuss.python.org/t/consider-downgrading-windows-32-bit-from-tier-1-to-tier-2-or-tier-3-in-python-3-13/33719 "2023-09-14T10:43:14Z")\
**Posts on this page:** 1\
**Showing post:** 58

<div class="post-metadata">

**Author:** ![AraHaan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/arahaan/32/14348_2.png) [@AraHaan](https://discuss.python.org/u/AraHaan)\
**Post date:** [June 28, 2024, 2:43pm UTC](https://discuss.python.org/t/consider-downgrading-windows-32-bit-from-tier-1-to-tier-2-or-tier-3-in-python-3-13/33719/58 "2024-06-28T14:43:58Z")

</div>

> [@steve.dower](#):
>
> It follows `PreferredToolArchitecture`, which is also used to select the compilers and other “native” tools required to build. Set this (env var or MSBuild property) to `x64` or `ARM64` and it’ll use the tools for that architecture instead.

Personally I think it should instead follow how all the other projects select the arch by default so then when someone right after cloning the source code would have to run `build.bat` and everything would be in `amd64` folder (`win32` never created if they have `amd64` as main arch on their pc) so then it makes my issues much less of an issue. Also it is easy to forget to set environment variables as well and I honestly prefer as few of them as possible for that exact reason (as sometimes they might not produce reproducible builds).

---

_[View the full topic](https://discuss.python.org/t/consider-downgrading-windows-32-bit-from-tier-1-to-tier-2-or-tier-3-in-python-3-13/33719)._
