David Gidwani

were you able to resolve this? the second error is probably because you installed libhs from a package manager rather than building from source. Debian/Ubuntu have

I'm using 3.9 on my personal machine, and the wheels are built on each cpython version currently supported, and you can see a [successful run here](https://github.com/darvid/python-hyperscan/runs/1551614164?check_suite_focus=true). so 3.9 is supported...

did you install hyperscan to `/usr` or `/usr/local`? make sure it's in your `LD_LIBRARY_PATH` if it's not in `/usr`.

ah, you need to build Hyperscan with `BUILD_SHARED_LIBS` set to ON. This is already documented [here](https://python-hyperscan.readthedocs.io/en/latest/), but it probably would help to have some checking in the build script.

@yiwiz-sai use ``python3 -m pip install hyperscan`` rather than ``pip`` and note that all those build requirements and libhyperscan are no longer needed, this package is linked statically now so...

ah looks like ``pip`` needs to be updated in the container first ``` RUN python3 -m pip install -UI pip RUN python3 -m pip install hyperscan ```

I currently don't have the bandwidth to look into this right now, apologies (#44) all I will add, and I know this isn't the ideal fix, but you should be...

they should be set to 1, see https://wiki.bash-hackers.org/syntax/pe#use_a_default_value

```python @rbac.set_user_loader def get_current_user(): return flask_login.current_user._get_current_object() ``` See maxcountryman/flask-login#9. Would be nice if this was done automatically if Flask-Login is installed.

i can disable fat runtime and set march to core2 for just the musl wheels, but that would mean applications running on alpine on hosts that support AVX2 would still...