You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware of PEP-8, and I sympathize. The camel-case names do stick out in Python.
However, the names come from the underlying C++ library, for which camel case is idiomatic, so those are not going to change. It would be possible to rename the methods when wrapping the library for Python (while leaving them unchanged when wrapping for other languages), but I see two objections.
The library has been around for 17 years now, and a number of users have written code that depend on it. Renaming the methods would break their code. I'm not willing to do that.
Even if we were willing to break things, this project is run on volunteer time (and not a lot of it), and I feel that the time required to make and maintain the changes would be better spent on other features.
Please follow PEP-8, don't write camel case method names. Also use the same signature for Date constructor as in stdlib!
The text was updated successfully, but these errors were encountered: