04/03/2014 00:20, Uwe Stöhr:
No. There is still too much to do and the translators also need time. I will see what I can do this week. Is it really that pressing? I mean I will for sure find further issues while updating the docs and I think we should take the time to fix as many bugs as possible.
I think that the docs can continue to be updated after 2.1.0 is released. Concerning bugs, the best way to find out about them is to make a release.
But the most important issue is that LyX does still require Python 2.7. This limitation is kind of a nightmare for me because more and more PCs come with a pre-installed Python 3.x which will of course interfere with Python 2.7.x so that LyX 2.1beta2 was not configurable for some users. Or do I missed something and LyX is now Python 3.x-ready? If so I will stress-test that.
I am surprised that there is no way to ensure that LyX finds its own python before the system one. In autoconf we have tests to make sure that we use the right python, I am sure this can be done in the windows installer and is less intrusive than updating and testing _all_ of our python scripts.
How come that 2.1.0beta2 was not configurable for some users but 2.0.x works fine?
I am not against moving to python 3.0, but there are better time for asking for that than when somebody says "OK let's release this month".
JMarc
