Decouple PDF code from PyLoT #36
Labels
No Label
analysis
bug
documentation
enhancement
feature
incompatibility
management
Priority:0
Priority:1
Priority:2
Priority:3
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
You do not have permission to read 1 dependency
Reference: marcel/pylot#36
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In principle the PDF code is usable independently from PyLoT. This can be achieved by making the PDF code a Python package as obspy and others are and import it into PyLoT where necessary. This also eases the maintainability of the PyLoT code. I would sign repsonsible for the PDF code. This is a major refactoring task and needs planning.
PDF code in this case is considered the files
pick/compare.py
andutils/pdf.py
.Hint: The same might be valuable for other parts of the code.