Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

break biggles.py into separate files for containers vs plot objects? #19

Open
beckermr opened this issue Jun 16, 2014 · 2 comments
Open

Comments

@beckermr
Copy link
Collaborator

Should we break biggles.py into separate files for containers vs plot objects? We would need a utils file as well for common stuff used in both places. The only problem with this proposal I see right now is that it might break the history of a given object in git. (I am not a git ninja, so if there is a clean way to do this, please let me know!) The advantage here is future maintenance of course, as ~2800 line files are hard for humans to parse and maintain.

@nolta
Copy link
Collaborator

nolta commented Jun 18, 2014

There isn't much git history to preserve (i didn't port the sourceforge logs), so that shouldn't be an impediment.

@beckermr
Copy link
Collaborator Author

OK. Then I should do this next before much more new stuff is added. This way as much history as possible is saved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants