Open ommr101 opened 5 years ago
Hi @ommr101 ,
Yes, the code here was developed using our own internal standard, which isn't PEP8.
PEP8 is most certainly a good standard to follow, but we don't consider it a necessity that warrants updating the code at the present time. Also, there are a fair number of users currently using the project, and we wouldn't want to cause syntactical discrepancies by updating the current versions.
However, if you're interested in contributing a PEP8 compliant pull request for the project, that would be super kind of you and we'd give you full credit via our user and social channels! :)
If you do so, please create a copy of the contents of v2.0.2/ in a new directory within your fork called v2.0.2-PEP8, and make modifications there, prior to submitting your pull request.
Thanks!
HI @ommr101 ,
Happy to announce that for our next version, we are rewriting everything from scratch for PEP8 compliance 🙂
Stay tuned.
I will be more than happy to help with this issue.
There are a few PEP8 violations in 'DWX_ZeroMQ_Connector_v2_0_1_RC8.py' file.
Such as:
There are two reasons it needs to be fixed (in my opinion):
If I fixed it only on my end, each file update on the repository will overwrite my fix in case I would want to use the latest version.
Almost all methods are named with a '_' as a prefix and Pycharm hides those methods as they are marked as private which is pretty uncomfortable.
Can I open a pull request and change this?