Resolve "Time to refactor utils?"

Closes #509 (closed)

added Infrastructure Low priority - looking for volunteers Refactoring Utility functions labels

changed milestone to %1.0.2

added 2 commits

• 3b90e157 - Set up directory structure for new and improved utils
• 6c548e58 - First step at restructuring utils.py

Compare with previous version

added 1 commit

• 3a0b7db9 - Fixed cross imports

Compare with previous version

added 1 commit

• 4d242cab - Fixed cross imports

Compare with previous version

added 1 commit

• 9072f37c - Now uses pathlib for safe directory creation

Compare with previous version

added 1 commit

• f211a388 - some formatting issues resolved

Compare with previous version

added 1 commit

• 6ea4dbcb - Added additional parent directory for searching .version file

Compare with previous version

changed milestone to %1.0.3

mentioned in issue #530 (closed)

Hi @moritz.huebner we decided on today's call that we would rather avoid having large changes to the code used in GW analyses between 1.0.2 and 1.0.3 as one of these versions are likely to be wanted for O3b analyses. Can we therefore push this to 1.0.4?

added 24 commits

• 6ea4dbcb...47dc99b3 - 22 commits from branch master
• 922b09ef - Merge branch 'master' into 509-time-to-refactor-utils
• bb9c673c - merged changes from master

Compare with previous version

changed milestone to %Future

mentioned in merge request !889 (closed)

resolved all threads

closed

reopened

@colm.talbot @gregory.ashton can you have a look and see if we actually want this change? It's been sitting open for a while now and it is a relatively big diff, so we should merge it rather sooner than later because it might hold up other development.

@moritz.huebner it is indeed a big diff. I'm finding it difficult to check that functionality-wise, nothing has changed and that this is a pure refactor. If you can confirm that, I'm happy to approve and merge it.

changed milestone to %1.1.3