Albert Zeyer

Yea, this whole issue is mostly not about performance at all, but really about cleaning up code. And for that, using `sorted` might be more annoying. But sure, it's just...

> Maybe we can start by dropping support for python 2.7? But maybe you prefer to do all changes in one go? I think it's easier to do in one...

@mihajenko How can I understand your downvote?

> I.e. finally make rasr compatible with python3 I thought it already is compatible with Python 3? What is the state here? > handle possible incompatibilities of the used pickle...

> There is a version of RASR that uses python3 instead of python2 and I can port it to the public version if there is demand for that. I think...

> Sorry, the issue is too broad. FastAPI is used as a model serving API by a decent number of ML applications; PyTorch barely got support out for Python 3.8,...

> Ah, my bad. Very sorry, my reply was the one not throught through. @mihajenko No problem. I assumed so. Your references to PyTorch / TensorRT are interesting anyway.

From the points raised in the original post, and also a similar discussion in https://github.com/rwth-i6/returnn_common/issues/43, it looks like Python 3.7 is a good minimum version candidate. This is e.g. required...

About RASR interface, specifically full-sum training, seq training or other exotic things, what is the state, is this now all well tested with Python 3? @Marvin84 @michelwi @SimBe195? About Python...

However, as it was argued before, just dropping Python 2 but keeping Python 3.5 or 3.6 compatibility does not really gain us much. We still cannot use type annotations in...