After running config.py to configure the curves you want to use, if you want to build a module that relies on any of the curves and then write any code depending on that module, the dependencies are currently a little clunky.
In my case, I ended up copying each of the curve directories created by config.py to my project and put an __init__.py file inside each of the folders so that I could install each curve as a Python module. I also had to copy the constants.py file to any folder with code that relied on any of the configured elliptic curves. The example structure below is what I used. In the example, assume that module_code.py depends on bn254 and that test.py relies on module_code.py.
project
| bn254
| | __init__.py
| | big.py
...
| module
| | __init__.py
| | module_code.py
...
| test
| | constants.py
| | test.py
If config.py could allow you to install the curves and any necessary constants as modules, it would be much easier to use in combination with other projects.
After running
config.pyto configure the curves you want to use, if you want to build a module that relies on any of the curves and then write any code depending on that module, the dependencies are currently a little clunky.In my case, I ended up copying each of the curve directories created by
config.pyto my project and put an__init__.pyfile inside each of the folders so that I could install each curve as a Python module. I also had to copy theconstants.pyfile to any folder with code that relied on any of the configured elliptic curves. The example structure below is what I used. In the example, assume thatmodule_code.pydepends onbn254and thattest.pyrelies onmodule_code.py.If
config.pycould allow you to install the curves and any necessary constants as modules, it would be much easier to use in combination with other projects.