Bye-bye @lpl Don’t let the door hit you on the way out.

I have not seen your pull requests or issues on https://github.com/ColdGrub1384/Pyto lxml, openCV, ui are all there now and it would be awesome to get your help on improving the usability.

Pyto is open source so read that source and submit PRs to fix the gaps.

I do not have the sense that Pythonista is dying but... I am very impressed with the consistent progress that Pyto has been making. A UI library, lxml, scipy were all added to Pyto in the past few weeks. It is open source with tests run in Travis-CI so instead of complaining that your favorite feature is missing, you can add it yourself. Instead of posting bugs in a forum, you can demonstrate the problem in a Travis test. Incremental improvement comes from active participation.

from datetime import date
print((date(2020, 1, 1) - date.today()).days,
      'days until Python 2 end of life.')

Yes. And 150 daze left for Python 2.

python interface to GnuCash

Is GnuCash pure Python? https://github.com/Gnucash looks to be ~75% C code.

@ihf This might help with your piecash issues.

Related to https://forum.omz-software.com/topic/5748/stash-pip-on-python-v3-6

Here you are installing into site-packages-2 but piecash no longer supports legacy Python.

https://github.com/sdementen/piecash/blob/master/setup.py#L252-L254

Also see: https://travis-ci.org/sdementen/piecash/jobs/566331812#L225

I find that I create hack,.py, junk.py, scratch.py all the time so that I can have one file that contains my modification/hacks while some other file contains the pristine unmodified original code that I started with. Every once in a while I actually make some useful improvement and then I select all and copy from scratch.py and select all and paste into the original. Life is easier when you get into the git workflow but this approach should be good enough for a start.

To edit the last line typed into the console, hit the ^ button just above the = key at the upper right of the onscreen keyboard.