Are you a .NET developer?¶
We’re happy you decided to try Fable Python, which is F# fully transpiled to Python.
Fable Python brings some .NET familiarity¶
Since it’s F# you probably wonder how Fable interacts with your .NET environment.
For starters, using F# for fable apps is very similar to using F# for .NET apps:
Fable projects use standard
.fsprojproject files (which can also be part of
You can use well-known .NET/F# tools like NuGet, Paket or Fake to manage dependencies or your build
You can use any F# editor like Visual Studio, Ionide or Rider
Many common classes and routines from the System namespace have been mapped to Fable to provide a familiar interface for very common things, such as
Most of FSharp.Core is also supported. Check the “.NET and F# Compatibility” section.
Fable is Python¶
Although Fable brings a lot of familiarity for F# and .NET developers, the target runtime is Python. This difference impacts several important areas:
Your dependencies will be Python (e.g PyPI) dependencies, not .NET dependencies
Runtime behavior will be based on Python semantics, not .NET semantics
There are some NuGet packages you can add into an F# project, but these packages have to also target Fable Python. Otherwise, your dependencies will directly be Python dependencies. Please check the “Author a Fable library” section to learn more, especially if you are a library author and would like to make your package compatible with Fable Python.
These differences may seem like a lot to take in at once, but they’re important for building robust applications. There have been efforts in the past to try and “magically” turn .NET code into JS, and these all tend to fail. The reality is that your target runtime environment will affect how your app runs and how you build it. However, once you internalize this, you’ll find that using F# for web apps with Fable is incredibly productive, making web programming a lot more joyful than just using Python!