search

CDAT / cdat

Community Data Analysis Tools
Other
174 stars 68 forks source link

Get rid of install.py.in #882

Open remram44 opened 9 years ago

remram44 commented 9 years ago

Seriously, I have been looking for cdat_info.py for a while, thinking I had missed an External. Then I found this. It's definitely not a priority right now but this needs a major overhaul.

A 36k Python file that gets configured by CMake (to the wrong folder, #629), copied over, and run to generate more Python files? Half of it is commented out, the other half is badly indented quoted code.

I am not sure of all the things that happen in there and it's certainly not maintainable.

doutriaux1 commented 9 years ago

@remram44 thanks for the nice and constructive comments. The uvcdat indeed as many many many many generation of install methods built on top of each others and while the current one is by far the best it has still a lot of left overs... And considering the huge list of priorities these sort of things more often than not falls into the "if it ain't broken why fix it". Again it's is an open source project and if this is harming your work in any way feel free to provide a patch. I doubt @aashish24 has any cycles for this or anybody at Kitware for that matter.

durack1 commented 9 years ago

@remram44 there's an open issue relating to (non-bug/issue) cleanup work #788 that could be undertaken, however as @doutriaux1 noted this doesn't appear to be a priority