MYPY Types added

[gagandeepp]

Brief Summary of Changes

Fixes: cloudinary/pycloudinary#377

What does this PR address?

• GitHub issue (Add reference - #XX)
• Refactoring
• New feature
• Bug fix
• Adds more tests

Are tests included?

• Yes
• No

Reviewer, please note:

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I ran the full test suite before pushing the changes and all the tests pass.

Before :

After: Old screenshot currently on 18 errors are there

[gagandeepp]

@const-cloudinary Does the initial changes looks good?

[gagandeepp]

@const-cloudinary Does the initial changes looks good?

Once you gives go ahead, I will implement the rest of the stubs and also add a precommit hook in the repository

[const-cloudinary]

@gagandeepp , yeah looks great, please go ahead!

[const-cloudinary]

@gagandeepp , this is what I see:

[gagandeepp]

@gagandeepp , this is what I see:

[gagandeepp]

@const-cloudinary Latest status:

[gagandeepp]

@const-cloudinary Can you please take a look at this?

[const-cloudinary]

@gagandeepp , Thank you for your PR!

This looks like a huge overhead of supporting such files, like, for every new option that is added, it needs to be added twice.

For example duplication of all @command definitions, FORMAT_ALIASES, not_callable.

Isn't it better to combine pyi and py files into one?

If no, is there any sort of automation? Like GitHub action? To make sure we don't forget to update pyi files ?

[gagandeepp]

@gagandeepp , Thank you for your PR!

This looks like a huge overhead of supporting such files, like, for every new option that is added, it needs to be added twice.

For example duplication of all @command definitions, FORMAT_ALIASES, not_callable.

Isn't it better to combine pyi and py files into one?

If no, is there any sort of automation? Like GitHub action? To make sure we don't forget to update pyi files ?

Let me take a look of