Hi Billy
I like the idea of using something on GitHub to track ideas for modernisation & also the idea of going through the codebase and removing unused code / cruft is appealing.
If you intend to move to a more standard template for program structure, I wonder if it is also worth asking about using more standard test frameworks too i.e. Python unittest - would make the refactoring somewhat safer...
Anyhow, endorse the idea of gathering thoughts somewhere on GitHub - I will keep an eye out for this
Thanks Graeme
________________________________
From: [email protected] [[email protected]] on behalf of Billy Poon [[email protected]]
Sent: 16 June 2017 18:14
To: cctbx mailing list
Subject: Re: [cctbxbb] Housekeeping / roadmap for future
Hi Graeme,
I can provide a more concrete list after the Phenix release, but generally, the migration to Python 3 in 2020 (exact date for Python 2 end-of-life is unclear, https://www.python.org/dev/peps/pep-0373/) will require checking through the existing codebase, so we would like to clean things up by removing unused code and consolidating any duplicate functionality.
I would also like to introduce a more standard template for programs so that the non-science stuff is more consistent among all programs. For example, file I/O (with more automatic handling of compressed files) can be isolated at the beginning with proper sanity checks on the data. Command-line flags, like an option for showing citations for the algorithms in the program, can also be more standardized.
The standard program template will also help in migrating the GUI away from wxPython. The replacement package for the GUI will most likely be PyQt5.
To help track progress and keep everyone up to date, we can use the "Projects" feature on GitHub.
--
Billy K. Poon
Research Scientist, Molecular Biophysics and Integrated Bioimaging
Lawrence Berkeley National Laboratory
1 Cyclotron Road, M/S 33R0345
Berkeley, CA 94720
Tel: (510) 486-5709
Fax: (510) 486-5909
Web: https://phenix-online.org
On Fri, Jun 16, 2017 at 5:05 AM,