Closed Mattia9875 closed 3 years ago
@Mattia9875 -- Ignore the ImportWarning
for now. Could you include the output of the dockerfile run?
(BTW You want to wrap your output in triple backticks to make github format it correctly.)
I am testing in interactive mode, i have no other output sorry
fasm/__init__.py
has no main method, which is why the import failed. The interactive module of fasm is fasm.tool
, like json.tool
. The error is not causes by a circular import, but instead is caused by setup.py pointing to the wrong entry point, see: https://github.com/SymbiFlow/fasm/blob/8fb1946b73cdb3222877a246a0e032f1b37d754c/setup.py#L253
Is there something i can do to fix it in my installation or is it a general issue?
Is there something i can do to fix it in my installation or is it a general issue?
Nothing is broken per say. None of the downstream tooling depends on the console script. Rather than invoking the fasm tool with fasm
, just invoke python3 -mfasm.tool
. You are welcome to submit a PR changing setup.py
and verifying it addresses your original issue.
@Mattia9875 - A pull request which changes the setup.py
line to fasm=fasm.tool:main
(I think?) and potentially adds a test to the CI would be very welcome!
Thank you,should i submit a issue pointing to this one in symbiflow-examples? beacuse with the current makefile the examples are not buildable
Thank you,should i submit a issue pointing to this one in symbiflow-examples? beacuse with the current makefile the examples are not buildable
I don't believe any of the makefiles in symbiflow-examples depend on the console script being correct. Do you have an example where that is the case?
My bad, i've mistaken the warning for an error, thanks for the support and the kindness!
Should be fixed soon by https://github.com/SymbiFlow/fasm/pull/62
Hi, i'm currently using docker to try and make a container out of symbiflow but i am encountering this issue when i try and call for the fasm command. Here is the dockerfile
Here is the issue
While trying to use the repo in an isolated environment i get the same issue but with a Circular Import warning hence the name of the issue