search

ELVIS-Project / vis-framework

Thoroughly modern symbolic musical data analysis suite.
http://elvisproject.ca/
31 stars 5 forks source link

Logging #357

Open crantila opened 9 years ago

crantila commented 9 years ago

Inspired by issue #243.

Currently, VIS doesn't do any logging, and doesn't provide any feedback on its progress, or what it's doing. Proper logging would be easy enough to implement, especially in IndexedPiece and the Indexer superclass, and it could be really useful/interesting.

For me at least, whenever I write an analysis script, I end up putting in print() calls all over the place, and I think @alexandermorgan does the same. In this case, we wouldn't have to---the log could be printed out by default. And for when VIS is running on a server, we could have the log point to an actual file.

alexandermorgan commented 9 years ago

For what it's worth, I moved on to pdb in lieu of print statements.

crantila commented 9 years ago

You started using a debugger so you could monitor your program's progress? I'm sure you're using it for other things too (like actual debugging) but for monitoring progress it's overkill, and it suggests this feature really is necessary.

crantila commented 7 years ago

I'm closing this because I don't think anyone cares.

musicus commented 7 years ago

Are you joining us back up?