# Pyxform v1.0 release **URL:** \ **Category:** Development\ **Created:** [November 6, 2019, 4:45pm UTC](https://forum.getodk.org/t/pyxform-v1-0-release/23163 "2019-11-06T16:45:20Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![LN](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ln/32/1605_2.png) [@LN](https://forum.getodk.org/u/LN)\ **Post date:** [February 7, 2020, 12:35am UTC](https://forum.getodk.org/t/pyxform-v1-0-release/23163/10 "2020-02-07T00:35:06Z")
The release is [now out](https://github.com/XLSForm/pyxform/releases) and [XLSForm Online has been updated](https://forum.getodk.org/t/odk-xlsform-online-v2-0-0/24730)! Thanks to all who have participated in this big lift. As I was verifying the release, I noticed another change that I had not explicitly thought about. As described above, the XLSForm filename is no longer used as the root node name. However, it is used as the default form title and `form_id` but it is no longer validated to ensure that it is a valid XML element name. That means that `form_id`s with spaces or special characters are now possible. I have verified that Collect, Central, Aggregate and Enketo can all properly handle `form_id`s with spaces and special characters. I can't see any limitations on the instance `id` element described in [the ODK XForms spec](https://opendatakit.github.io/xforms-spec/#primary-instance) or in any other documentation so I believe that this is ok but I wanted to flag it in case anyone has concerns. --- _[View the full topic](https://forum.getodk.org/t/pyxform-v1-0-release/23163)._