ImportWarning due to ambiguous 'ssl' directory about chargebee-python

[cb-rakesh]

Let me know if the issue persists with the latest version as well. Or else we can close this.

[hheimbuerger]

That was years ago and I'm not anymore involved at that level.

I did a quick code review and I don't see an import ssl anywhere in your code anymore, so it probably should be fine. I still think it's an unfortunate/risky naming choice for a data directory in your Python source tree — why don't you just call it certificates? Less of a risk of a naming conflict, and much more accurate anyway, given that we've phased out the SSL protocol years ago.

If you tested on Python 2.7 and couldn't reproduce this, then go ahead and close my issue.

[cb-rakesh]

We tested the package against python 2.7 and it's working as expected. Hence closing the issue.