We are open to contributions! Specifically:
A release of the library is a copy of the library without the key code that learners must implement.
To generate a release, EduNN’s reference implementation in folder edunn is stripped of """YOUR IMPLEMENTATION START""" and """YOUR IMPLEMENTATION END""" comment pairs, and all the code in between. The resulting code is stored in the generated folder.
Guides can be written for different languages (english, spanish, etc), and are zipped with a release to generate a downloadable guide.
requirements.txt and requirements_dev.txt, also run pre-commit installedit_guides.sh to fire up a jupyter-notebook server that can import edunn correctly (recommended to avoid path issues, but you can do this in other ways if you are knowledgeable in python1)edunn componentclear_notebooks.pyedunn (see next steps)edunn releasesIf you modified the edunn library itself, then:
test folderpytest in the root folder of the projectedunn) by runningexport_code.py. This will copy all code in edunn to generated and remove the reference implementation.If you modified a guide of language <lang>:
zip_guide.py <lang> (ie, zip_guide.py es for spanish)import sys; sys.path.insert(0, "../.."); ↩