Unai Martinez-Corral
Unai Martinez-Corral
Hi @ktemkin! No more involvement neither now nor in the foreseeable future. As @mithro said, the main target is to bring people from several camps of the open source hardware...
For context: 
@mithro, agree. Is it within the scope of this issue? The description mentions "shell wrappers", not "Python wrappers".
@Pocketkid2, there are five sets of "scripts": - Distributed as part of the arch-defs packages (tarballs): - Lowest abstraction: Python scripts. Some of these do have Python dependencies, which are...
@carlosedp note that the "backend" is nextpnr in this case (VTR is supported as well). Project XRay is the "architecture documentation/database", equivalent to IceStorm, Project Trellis or Project Nexus. See:...
FTR, pytest uses a mechanism to allow "plugins to be installable by others" (https://docs.pytest.org/en/6.2.x/writing_plugins.html#making-your-plugin-installable-by-others) which is based on providing an specific entry_point in the `setup`: > If you want to...
> Given the heavy usage of python in the opensource EDA tooling, using https://www.python.org/dev/peps/pep-0484/, https://www.python.org/dev/peps/pep-0526/ and https://www.python.org/dev/peps/pep-0557/ could be an easier way to describe the format while allowing direct integration...
@proppy, awesome! Thanks a lot for that example!
That seems to be coming from the `tox.ini`: https://github.com/olofk/fusesoc/blob/fa33702625895babde31d32ee84d78ed734bafa3/tox.ini#L16
Overall, I think that testing spaces in paths is important, because that's relatively common on Windows. I would propose creating a feature branch where tests are modified, and use that...