You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that python-daemon is finally py3 compatible should we move stuff over? It'd certainly clean up the command line client a whole lot (Cmd is an old-style class in py2 which makes sub-classing it a pain, and then there's the whole argparse thing). Not a definite thing, but something to consider sometime prior to 1.0.
The text was updated successfully, but these errors were encountered:
I won't be moving the project completely to Python 3 (i.e. I'd like the client library to be accessible from both Python 2 and 3 for the time being), but there are a whole bunch of commits in the recent history for 3.2+ compatibility: 2dfaeda, e4482b6, 6b11255, etc. and I think the master branch is now Python 3.2+ compatible.
At least, the current test suite passes on 3.2+ (though I'll admit the test suite is still far from comprehensive; ignore the coverage stats at the end there - they're only for the modules I'm currently testing which basically excludes everything in the CLI and GUI interfaces!).
In other words, you should be safe using the client library on Python 3 but I make no guarantees about the CLI or GUI interfaces yet!
Now that python-daemon is finally py3 compatible should we move stuff over? It'd certainly clean up the command line client a whole lot (Cmd is an old-style class in py2 which makes sub-classing it a pain, and then there's the whole argparse thing). Not a definite thing, but something to consider sometime prior to 1.0.
The text was updated successfully, but these errors were encountered: