-
-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* LGTM warning: Unguarded next in generator Call to next() in a generator Additionnlly, dicom_file cannot be None: • os.path.splitext(dicom_file) would raise TypeException • In the case of a ZIP file, which I believe is the one the existing code was trying to address, we continue on StopIteration if the ZIP file is empty. * LGTM recommendation: Unused import Import of 'Sequence' is not used. Import of 'remove_sequences' is not used. Import of 'os' is not used. Import of 'read_json' is not used. Import of 'DeidRecipe' is not used. Import of 'get_private' is not used. Import of 'remove_sequences' is not used. Import of 'extract_fields_list' is not used. Import of 'extract_values_list' is not used. Import of 'get_fields' is not used. Import of 'DataElement' is not used. Import of 'operator' is not used. Import of 'get_installdir' is not used. Import of 'os' is not used. mport of 'read_file' is not used. Import of 'os' is not used. * LGTM recommendation: Except block handles 'BaseException' Except block directly handles BaseException. Function dateutil.parser.parse() raises the following exceptions: • ParserError – Raised for invalid or unknown string formats, if the provided tzinfo is not in a valid format, or if an invalid date would be created. • OverflowError – Raised if the parsed date exceeds the largest valid C integer on your system.
- Loading branch information
1 parent
54c8f68
commit 18f5b45
Showing
9 changed files
with
19 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters