Further to our recent discussions of pymol
* I've pushed a couple of changes to git for version 2.2.0+dfsg-1 which I
think is ready to upload to unstable.
On Sunday, 21 October 2018 16:47:12 AEDT Michael Banck wrote:
> On Sun, Oct 21, 2018 at 11:48:42AM +1100, Stuart Prescott wrote:
> > There was also speculation a while back about this being the right time to
> > switch from Python 2 to Python 3 and from tk to Qt.
>
> I'd be fine with that, but I have to say I haven't tested the Qt
> interface a lot and I won't be of much help in case of regressions.
* I've also pushed a debian/experimental branch that uses Python 3 and Qt. I
think it's ready to get uploaded to experimental at least -- it will go
through NEW on the way.
I'll make these two uploads in a few days unless anyone spots problems.
Looking through the build-time and autopkgtest tests, I found a few Python 2→3
problems that I've patched (already merged upstream).
I'm not convinced that the tests we've got actually test the package properly
-- if individual tests fail, the tests are still reported as passed. In
discussing testing with upstream, it seems there is a separate repository of
tests that can be used. Do we add that as an extra tarball for a multi-tarball
source package? Or try to upload it as an extra source package?
https://github.com/schrodinger/pymol-testing
Cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
