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

separate executable scripts factoring out common code into modules #15

Open
jack-oquin opened this issue Apr 10, 2013 · 2 comments
Open

Comments

@jack-oquin
Copy link
Member

Make modules in src/ with code common to the various nodes.

Move the nodes themselves into scripts/ (standard location). Each one should just import and then invoke an appropriate module function.

@jack-oquin
Copy link
Member Author

I recommend that the documented node names not end in ".py". The fact that they are written in Python is an implementation detail. Users should not care.

That change (if accepted) should be made with "tick-tock" backwards compatibility. For one release we would support the old names, issuing a deprecation warning if they are invoked. In the following release the old names would be removed.

@jack-oquin
Copy link
Member Author

Having most of the logic in Python modules generally makes it easier to write unit tests (see issue #16).

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

1 participant