Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API hard to read #4

Open
carterbox opened this issue Mar 11, 2019 · 1 comment
Open

API hard to read #4

carterbox opened this issue Mar 11, 2019 · 1 comment

Comments

@carterbox
Copy link

carterbox commented Mar 11, 2019

Generally, we follow the PEP8 convention for naming things in Python.

For example:

an_object_instance = ClassName()
a_function_name(foo, bar)

By pyctest doesn't seem to follow any convention. The functions and classes are all randomly either CamelCase or lower_with_underscores. This makes reading calls to the API difficult to read.

@jrmadsen
Copy link
Owner

Anything with a direct corollary to CMake/CTest follows CamelCase. If not, lower with underscores. I'm hesitant to change the API but I'll take that into consideration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants