Address RATS Report about podaacpy HOT 5 CLOSED

@lewismc I am checking out the files and will identify the issues. Thanks.

from podaacpy.

@lewismc the first error is for the remove statements, remember we were cleaning up the data downloaded by the test cases? using os.remove().

Coming to the second and third errors, they are on file open and read used in setu.py and mcc.py, I can't find the vulnerability here, but we can discuss on this. Thanks.

from podaacpy.

@lewismc the first error is for the remove statements, remember we were cleaning up the data downloaded by the test cases? using os.remove().
Yes but 'maybe' there is a better way to do it! Honestly, right now I don't know. I think we need a GHangout to decide.

Coming to the second and third errors, they are on file open and read used in setu.py and mcc.py, I can't find the vulnerability here, but we can discuss on this. Thanks.

OK, well the difference between 'our' current checks and 'their's is important. If possible we should address. ... Only if possible. possibly via unit tests. OK

Anyway's, please just tell me how and if you were able to address. This is NOT a major deal, your branch needs to be addressed, updated and smartened up in order for it to be useful.

Please, please, please, can you write some unit tests. Can you log the issues you find at the OCW Issue tracker and please keep the way you are going.

OCW will benefit VERY well from having a PO.DAAC data source. Please take the above as positive criticisms and I will work with you ofline to resolve theh @Omkar20895

Thank you

from podaacpy.

@lewismc shall we discuss this??

from podaacpy.

Based on the fact that the API is essentially changing, I am closing this off.

from podaacpy.