Some advice about license compliance

[Ashley123456789]

Hello, such a nice repository benefits me a lot and so kind of you to make it open source!

Question
There’s some possible legal issues on the license of your repository when you combine numerous third-party packages.
For instance, argparse, numpy and datetime you imported are licensed with Python Software Foundation License, BSD License and Zope Public License, respectively.
However, the MIT license of your repository are less strict than above package licenses, which has violated the whole license compatibility in your repository and may bring legal and financial risks.

Advice
You can select another proper license for your repository, or write a custom license with license exception if some license terms couldn’t be summed up consistently.

Best wishes!

[Hiroshiba]

Hi!!!

I am distributing code that only imports those libraries.
Where might there be licensing issues?

[Ashley123456789]

Thanks for your response!
More developers (including the Free Software Foundation) consider imports as one of the styles of making derivative works, thus involving license issues. So the license compatibility here is also of concern.
Some helpful links:
https://opensource.stackexchange.com/questions/2139/can-i-license-python-project-under-3-clause-bsd-while-it-has-gpl-based-dependenc
https://stackoverflow.com/questions/999468/question-on-importing-a-gpled-python-library-in-commercial-code