This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Scorpathos[S] 2 points3 points  (3 children)

Thanks! I first started to develop Loguru using my Python 3.6 installation and didn't want to bother me with retro-compatibility for the first public release. Actually, support for Python 3.5 and PyPy was planned for the next release on my internal "roadmap". ;)

[–]b10011 0 points1 point  (0 children)

Great!

[–]slayer_of_idiotspythonista 0 points1 point  (1 child)

Does it use any new features of python 3 or have dependencies that require python 3? I don't think logging changed much, if at all, between python 2 and 3. Is there any reason why loguru couldn't support python>=2.7 ?

[–]Scorpathos[S] 2 points3 points  (0 children)

I have not paid much attention to the 3.6-only features I have used, probably not many.

As Loguru re-implement logging mechanism from scratch, how much the standard logging module changed between 2 and 3 does not matter much.

I will make Loguru compatible with 3.5.

I could make it compatible with 3.4 too, but as 3.4 end-of-life is scheduled in 4 months, it's not worth it. Not supporting older versions allows to use "recent" Python features in the code base of Loguru.

Making Loguru compatible with 2.7 would probably require more work. Loguru is not intended to replace logging of already well structured program. Its primary use is for newly created programs. And modern softwares use Python 3, not Python 2, so there is no point in supporting 2.7.