Skip to content

Releases: IronLanguages/ironpython3

IronPython 3.4.1

12 Jul 14:07
Compare
Choose a tag to compare

On behalf of the IronPython team, I'm very happy to announce the release of IronPython 3.4.0. The runtime targets are .NET Framework 4.6.2, .NET Core 3.1 and .NET 6. The baseline for IronPython 3.4 is Python 3.4.

Changes include UTF-8 mode, a backport of the typing module in the standard library, a newer version of pip (18.1), as well as a number of bug fixes and improvements.

UTF-8 mode can be enabled via the cli using -X utf8 or by using the Utf8Mode option when creating the engine.

Thanks to @arontsang, @BCSharp and @frawst for the contributions!

IronPython 3.4.0

12 Dec 14:08
1196691
Compare
Choose a tag to compare

On behalf of the IronPython team, I'm very happy to announce the release of IronPython 3.4.0. The runtime targets are .NET Framework 4.6.2, .NET Core 3.1 and .NET 6. The baseline for IronPython 3.4 is Python 3.4, although it also includes some syntax and features from newer Python versions, most notably f-string support (from 3.6).

IronPython 3.4 uses Python 3.4 syntax and standard libraries and so your Python code will need to be updated accordingly. For details on upgrading from IronPython 2 to 3 see the Upgrading from IronPython 2 to 3 article.

While compatibility with CPython has been one of our main goals with IronPython 3, there are still some differences that may cause issues, for more information see the Differences from CPython article.

This release brings in numerous bug fixes, improved compatibility with CPython and better test coverage. It also include a new installation method for the .NET version using .NET tools (dotnet tool install -g IronPython.Console).

Special thanks to @BCSharp for the numerous contributions! As well as @LostBenjamin, @timgates42 and @scott-xu for their contributions to this release.

Full Changelog: v3.4.0-beta1...v3.4.0

IronPython 3.4.0-beta1

30 Apr 23:33
35cc227
Compare
Choose a tag to compare
Pre-release

On behalf of the IronPython team, I'm very happy to announce the release of IronPython 3.4.0-beta1. The runtime targets are .NET Framework 4.6, .NET Core 3.1 and .NET 6. The baseline for this release is Python 3.4.

IronPython 3.4 uses Python 3.4 syntax and standard libraries and so your Python code will need to be updated accordingly. For details on upgrading from IronPython 2 to 3 see the Upgrading from IronPython 2 to 3 article.

While compatibility with CPython has been one of our main goals with IronPython 3, there are still some differences that may cause issues, for more information see the Differences from CPython article.

This release brings in numerous bug fixes, improvements and features from newer versions of Python. Notably:

  • int/long unification (thanks @BCSharp )
  • f-string support (from 3.6)
  • % formatting for bytes (from 3.5)
  • improved module support (for example venv, ensurepip on Linux, django, typing)
  • improved test coverage
  • improved compatibility with CPython

Thanks to @BCSharp for the numerous contributions!

IronPython 3.4.0-alpha1

20 Apr 00:03
Compare
Choose a tag to compare
Pre-release

On behalf of the IronPython team, I'm very happy to announce the release of IronPython 3.4.0-alpha1. The runtime targets are .NET Framework 4.6, .NET Core 2.1, .NET Core 3.1 and .NET 5. The baseline for this release is Python 3.4.

IronPython 3.4 uses Python 3.4 syntax and standard libraries and so your Python code will need to be updated accordingly. For details on upgrading from IronPython 2 to 3 see the Upgrading from IronPython 2 to 3 article.

While compatibility with CPython has been one of our main goals with IronPython 3, there are still some differences that may cause issues, for more information see the Differences from CPython article.

Huge thanks to @BCSharp, @slide and other contributors @gpetrou, @jdhardy, @paweljasinski, @gfmcknight, @jameslan, @moto-timo, @rtzoeller, @in-code-i-trust, @hackf5, @dc366, @simplicbe, @AlexKubiesa, @isaiah, @ivanbakel, @syn2083, @komodo472, @yuhan0, @michaelblyons, @simonwyatt, @alanmbarr, @ShahneRodgers.

Edit (2021-04-21): updated the release binaries to resolve an issue with ensurepip.