We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I suggest to don't use this syntax :
from . import SpriteRef from .config import CSSConfig from .css import split_declaration
but use this syntax :
from spritemapper import SpriteRef from spritemapper.config import CSSConfig from spritemapper.css import split_declaration
Generally, I don't see and I don't use relative import. Usual python project convention don't use relative import.
Lately, I've executed this command :
$ python ../Spritemapper/spritecss/finder.py mime.css Traceback (most recent call last): File "../Spritemapper/spritecss/finder.py", line 7, in <module> from . import SpriteRef ValueError: Attempted relative import in non-package
If the project don't use relative import, I would not get this error.
What do you think about this suggestion ?
I can fix it if you want ?
Regards, Stéphane
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I suggest to don't use this syntax :
but use this syntax :
Generally, I don't see and I don't use relative import.
Usual python project convention don't use relative import.
Lately, I've executed this command :
If the project don't use relative import, I would not get this error.
What do you think about this suggestion ?
I can fix it if you want ?
Regards,
Stéphane
The text was updated successfully, but these errors were encountered: