Update the version of PyAssimp on PyPI

[JerzySpendel]

Current version of PyAssimp on the PyPI doesn't work. It throws errors, because looks like at some point you try to access aketrans attribute of bytes (I guess typo from maketrans method of bytes class) object which is no longer an issue if I install package from setup.py.

So simply realeasing new version should fix this.

[umlaeute]

i think this requires attention.
there have been a couple of bug-reports that i think all boil down to people installing an outdated and broken version of pyassimp from pypi:

• Bug: pyassimp.load(<path_to_file>) causes ValueError: invalid string pointer <some_address> in core.py, line 134, in _init obj = getarr(self,m) #5143
• PyAssimp cannot load PLY #3887
• pyassimp got SIGSEGV when loading simple fbx file #3220
• Pyassimp crash on PyPy #2824
• Assimp 5 crash on pyassimp.load function #2788
• Segmentation fault while import stl file pyassimp 4.1.4 #2343
• PyAssimp can't load simple OBJ #2339

(some of these bugs are open, but i have the gut feeling, that they are actually fixed with current versions of assimp/pyassimp).

i think the native pypi home for the pyassimp package is https://pypi.org/project/pyassimp/ owned by @severin-lemaignan and @rspencer01 (it's the only one of the various assimp bindings you find on pypi, that is directly built from the bindings found in this repository)

i propose to reactive this pypi package (possibly adding the assimp maintainers (@kimkulling , ...) to the pypi team), and using some github action to automatically upload new packages to pypi whenever there's a new assimp release.

see https://github.com/marketplace/actions/pypi-publish

[severin-lemaignan]

hi! I've just re-uploaded pyassimp to pypi: https://pypi.org/project/pyassimp/5.2.5/

Very happy to hand-over the maintenance of the pypi project to someone more active in the project, though!

[severin-lemaignan]

FYI, #5151

[umlaeute]

thanks for anybody involved.

now comes the time to reveal that i am just bigmouthing, and don't have any actual powers to proceed.

afaict, we have two offers to use an existing PyPi project to directly push the pyassimp package on release.
in general i would very much welcome it, if some members of the Assimp team had write access to the "canonical" PyPi project (bus factor, and things)

should we take this opportunity? how does automatic pushing to pypi (via a github action) sound? (i don't have any practical experience with pushing to pypi (neither manually nor via gh-actions) but I assume it is straight-forward)

is this of interest to the assimp team? (ping @dnadlinger , @turol , @acgessler , @kimkulling , @Schrompf )