Open brunobord opened 9 hours ago
So, either:
pyyaml
is a runtime requirement, so thepyproject.toml
file should reflect thispyyaml
should not be required to run a severus-based i18n, and importingseverus
objects should be possible without triggering an exception (I admit that this one involves a lot of work to handle conditional imports, etc)
Thank you for reporting this, and sorry for the mess, I probably should've checked this properly once I took this out of Emmett.
As of today, the requirement is actually needed at runtime, so pyproject.toml
should be fixed accordingly. Gonna release a patch version asap.
Probably that requirement can be made optional with some minor effort, and make the yaml loader optional. Gonna probably tackle that in the next minor release.
that's great! many thanks!
Hi,
I was looking to test
severus
as an alternative togettext
in a tiny pet project, and I simply installed it on a virtualenv via:Then I've followed the readme and created a
hello.py
file with the following code:but it raised the following exception:
ModuleNotFoundError: No module named 'yaml'
In the
pyproject.toml
file, I see thatpyyaml
is a "dev" requirement: https://github.com/emmett-framework/severus/blob/master/pyproject.toml#L108But it looks like it's... not.
So, either:
pyyaml
is a runtime requirement, so thepyproject.toml
file should reflect thispyyaml
should not be required to run a severus-based i18n, and importingseverus
objects should be possible without triggering an exception (I admit that this one involves a lot of work to handle conditional imports, etc)