I think it's time to start planning for a ledger 3.2 release. Dimitri John Ledkov has recently completed the port of the Python API to Python 3, which is something Alexis started a long time ago. Python 2 support is ending in 2020, and lack of Python 3 support is already a problem for some distros.
There are still some issues left with Python 3 support (some tests fail). I'd like to start by gathering a list of issues that need to be addressed before 3.2 can be shipped. I added a 3.2 milestone on GitHub and tagged a few issues: https://github.com/ledger/ledger/milestone/3 However, I should note that not all of these are strictly necessary for 3.2. I tagged some issues that would be nice to resolve but that aren't crucial. I might remove the milestone from some again. Some of them are build issues, which may have already been resolved but someone needs to confirm so. Some are (small) licensing issues that would be good to resolve. Anyway, I'm hoping everything can help: - point out issues that should be fixed before 3.2. I'm talking about *critical* stuff - help fix as many things as possible - test Python3 support and report issues Thanks! -- Martin Michlmayr https://www.cyrius.com/ -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/20191210132100.GA14239%40jirafa.cyrius.com.
