You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relative imports are discouraged for clearness, and a proper textiles Python package didn't exist. The most obvious solution was then to add a textiles package to the repo instead of using the whole repo as a package (this wasn't even recognized by PyCharm). The only thing left, as @jgvictores stated, is to integrate CMake and setuptools to have textiles installed in the system (see issue #38).
Note that the changes done to solve this issue will probably break any hardcoded paths present in the code, but those shouldn't exist to start with, so it's ok.
When importing modules from the textiles package (e.g. common, ironing, etc) outside PyCharm an import error is raised.
This might be due to Pycharm including textiles submodules in the Python path, but needs to be fixed so that it can be run also outside PyCharm.
The text was updated successfully, but these errors were encountered: