# New py5 release 0.10.7a0!

**URL:** <https://discourse.processing.org/t/new-py5-release-0-10-7a0/47054>\
**Category:** py5\
**Created:** [August 30, 2025, 3:38pm UTC](https://discourse.processing.org/t/new-py5-release-0-10-7a0/47054 "2025-08-30T15:38:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hx2A](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/hx2a/32/14322_2.png) [@hx2A](https://discourse.processing.org/u/hx2A)\
**Post date:** [August 30, 2025, 3:38pm UTC](https://discourse.processing.org/t/new-py5-release-0-10-7a0/47054/1 "2025-08-30T15:38:52Z")

</div>

This release includes the following version updates:

- Minimum Python version is now 3.10 (previously 3.9)

- JPype minimum version is now 1.6 (previously 1.5.2)

- numpy minimum version is now 2.2 (previously 1.26)

Also, this py5 release includes the core jars from the latest Processing release, 4.4.6.

The Py5Image object has a new `resize()` method that works like the `PImage.resize()` method in Processing. See the [Py5Image.resize() documentation](https://py5coding.org/reference/py5image_resize.html) for more information.

This release includes fixes for several issues:

- [#666](https://github.com/py5coding/py5generator/issues/666) was fixed, so py5 should now work with `FX2D` on Windows 11 - many thanks to [vsquared](https://github.com/vsquared) aka @svan for identifying the coding error that caused this problem.

- [#578](https://github.com/py5coding/py5generator/issues/578) has been resolved. The problem here was that py5 could crash on older macOS machines if a particular sequence of events occurred with the default `JAVA2D` renderer and the OpenGL renderer. This issue was a major thorn in my side for a long time, and I’m relieved that it is now closed.

- [#659](https://github.com/py5coding/py5generator/issues/659) has been fixed. This issue caused problems when converting Shapely objects with only two vertices to Py5Shape objects for use in `P3D` mode.

Happy coding!