Can we get a new release?

[TimSchneider42]

Hi,

Pyrender is currently broken on Python 3.12 and 3.13 because of an issue with OpenGL 3.1.0, which got solved in some version up to 3.1.9. Commit 7c613e relaxes the version requirement and, thus, fixes this issue. Could we get a new release, so the fix is available on PyPi?

Best, Tim

[Jiaviz]

Waiting for this great work to be updated.

[jasper-tms]

I suspect we won't hear back. I'm happy to push my fork (https://github.com/jasper-tms/pyrender) to pypi as pyrender2 if people want.

[TimSchneider42]

I think this would great! Out of curiosity, are you generally interested in continuing to maintain pyrender?

[jasper-tms]

Well this is the second time I've found myself being asked this sort of question recently, so I'll link to my previous answer which applies here too ;) https://github.com/ramonhagenaars/nptyping/issues/125#issuecomment-2632311249

[iory]

Hello,

I am the developer of a Python library for robotics called scikit-robot (https://github.com/iory/scikit-robot), and I have been using pyrender for its visualization features.

I believe that continuous testing and maintenance through GitHub Actions are crucial for the reliability of such libraries. For this reason, I've created a repository named scikit-robot-pyrender specifically to test and release a version of pyrender that is continuously verified via GitHub Actions. I've also added tests for recent Python versions, including 3.13. https://github.com/iory/scikit-robot-pyrender/blob/main/.github/workflows/test.yml

If you are interested, please feel free to take a look. You can find it here: https://github.com/iory/scikit-robot-pyrender.

[TimSchneider42]

Thanks a lot for taking care of this @jasper-tms and @iory!