I knew from the start that Microsoft’s Visual C Runtime Library (MSVCRT) would not be natively available on macOS, so I wasn’t surprised when I realized it wouldn’t install. Because I don’t often rely on MSVCRT, it didn’t feel like a critical loss—until a coworker asked me to make a shared Python script run smoothly on both Windows and macOS. That prompted me to explore the most effective way to achieve cross-platform functionality without expecting MSVCRT to somehow appear on a Mac.
Thank me by sharing on Twitter 🙏
To solve this challenge, I set out to find a macOS-friendly alternative that could replicate the core tasks I needed. My main concern was handling user input in a way that would feel just as natural on Windows as it does on macOS. It wasn’t enough for the script to work; it had to work well for anyone who ran it. After some research, I discovered that there are Python libraries designed to replace MSVCRT-specific calls and provide the same functionality regardless of the operating system.
Why MSVCRT Isn’t Mac-Friendly
While MSVCRT is integral to Windows, it relies on native Windows APIs that macOS simply does not have. Essentially, these calls interface with the deeper layers of the Windows operating system. Attempting to bring that functionality over to macOS feels like forcing two puzzle pieces together when they clearly don’t match. The macOS environment uses its own C runtime, and the system calls differ enough to make direct MSVCRT support unfeasible.
I realized that if my script only contained MSVCRT calls, anyone using macOS would be stuck or would need to tweak the code each time. Because I wanted a single script that worked everywhere, I had to respect the boundaries between these operating systems and look for solutions built with cross-platform compatibility in mind.
Exploring Cross-Platform Python Alternatives
I decided to tackle the issue by examining what I actually needed from MSVCRT. Most of my scripts used it for console I/O, particularly functions like getch() to capture user input in real time. Fortunately, the Python community has developed packages that accomplish similar tasks on multiple operating systems. One such package is getch, which provides a unified interface. That meant I could write code that behaves similarly on Windows, macOS, and Linux without platform-specific hacks.
Highwings 8K 10K 4K HDMI Cable 48Gbps 6.6FT/2M, Certified Ultra High Speed HDMI Cable Braided Cord-4K@120Hz 8K@60Hz, DTS:X, HDCP 2.2 & 2.3, HDR 10 Compatible with Roku TV/PS5/HDTV/Blu-ray
$9.99 (as of February 25, 2025 13:13 GMT +00:00 - More infoProduct prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on [relevant Amazon Site(s), as applicable] at the time of purchase will apply to the purchase of this product.)
Co-Intelligence: Living and Working with AI
$17.79 (as of February 25, 2025 13:13 GMT +00:00 - More infoProduct prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on [relevant Amazon Site(s), as applicable] at the time of purchase will apply to the purchase of this product.)
Apple USB-C Woven Charge Cable (1 m)
$15.00 (as of February 25, 2025 13:13 GMT +00:00 - More infoProduct prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on [relevant Amazon Site(s), as applicable] at the time of purchase will apply to the purchase of this product.)To implement this, I wrote something like:
import sys
if sys.platform.startswith('win'):
import msvcrt
else:
import getch
def read_single_key():
if sys.platform.startswith('win'):
return msvcrt.getch().decode('utf-8')
else:
return getch.getch()
This approach has given me the flexibility to distribute my Python scripts to colleagues, regardless of whether they’re using Windows or macOS.
When Windows is Truly Required
There are times when one might truly need Windows functionality. In such cases, I’ve relied on virtual machines or emulators. Installing a Windows virtual machine on my Mac allowed me to run software that specifically demands Windows libraries. On another occasion, I tested Wine for simpler applications. These methods let me keep my Mac environment intact while still enjoying access to Windows-exclusive tools. Although I prefer native solutions, these workarounds have proven invaluable when Windows-specific behavior is unavoidable.
My Final Thoughts
After navigating the MSVCRT question on macOS, I’ve gained a renewed appreciation for how operating systems are purpose-built with their own internal logic. No single environment can do everything flawlessly, and part of being efficient is choosing the right tool for the task. By embracing cross-platform Python packages or, if necessary, employing a virtual machine, I’ve managed to create smooth workflows that accommodate multiple operating systems. I trust this experience will resonate with anyone who has ever tried to bring Windows-centric tools into the macOS world.
