[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] converting old signal/slot to new signal/slot
From:       Florian Bruhin <me () the-compiler ! org>
Date:       2015-05-29 11:54:48
Message-ID: 20150529115448.GU469 () tonks
[Download RAW message or body]

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

[Attachment #2 (multipart/signed)]
This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.


* c c <coastalchaos@hotmail.co.uk> [2015-05-28 07:50:14 +0100]:
> Yes I agree the new style is cleaner, I'm just trying to understand
> the code as it was so I can refactor it to the new style to move
> forward with pyqt5/qt5 now and not have to worry in the future.

I suggest writing some unit tests[1]. I use py.test[2] and
pytest-qt[3] which makes this a lot easier.

[1] http://nedbatchelder.com/text/test0.html
[2] http://pytest.org/
[3] https://pytest-qt.readthedocs.org/

You'll get more familiar with Python, with the application you're
porting, and - most importantly - if you have good test coverage
([4] helps), you'll instantly know what works and what doesn't.

Also, seeing the number of successful tests go up while you're working
is satisfying! :)

[4] http://nedbatchelder.com/code/coverage/

Florian

--=20
http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

[Attachment #5 (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread]