pip3 install -r requirements.txt fails on v2.1.0

[pjvandehaar]

Here is the output I get:

$ pip3 install -r requirements.txt
Collecting alembic==1.8.0
  Using cached alembic-1.8.0-py3-none-any.whl (209 kB)

...

Collecting typing-extensions
  Using cached typing_extensions-4.5.0-py3-none-any.whl (27 kB)
Collecting rich<13,>=12
  Using cached rich-12.6.0-py3-none-any.whl (237 kB)
ERROR: Could not find a version that satisfies the requirement FlaskBB>=2.1.0 (from flaskbb-plugin-conversations==1.1.1->-r requirements.txt (line 32)) (from versions: 2.0.0.dev0, 2.0.0, 2.0.1, 2.0.2)
ERROR: No matching distribution found for FlaskBB>=2.1.0 (from flaskbb-plugin-conversations==1.1.1->-r requirements.txt (line 32))

I'm running in a py38 virtualenv on Ubuntu 18.04.

It looks like the problem is that the latest version on PyPI is v2.0.2.

Perhaps instead, packages should be installated in 3 steps:

• install deps
• install -e .
• install flaskbb-plugin-*

Or am I doing something wrong?

[pjvandehaar]

I was able to install by doing this:

pip3 install wheel  # makes everything run much faster, and ought to be mentioned on <https://flaskbb.readthedocs.io/en/latest/installation.html>
pip3 install -U setuptools  # improves dependency resolution, without which installation fails
git checkout v2.0.2
pip3 install -r requirements.txt
pip3 install kombu==5.2.4  # prevent a SyntaxError due to keyword "async"
git checkout master
pip3 install -r requirements.txt

[pjvandehaar]

Sorry for re-using one issue, but I've got another problem now. flaskbb makeconfig imports flask_allows, which imports werkzeug.LocalProxy, which doesn't exist. What am I missing here? How does this work for anybody else?

[sh4nks]

Hey, looks like the import changed in werkzeug from werkzeug to werkzeug.local for LocalProxy. This will propably require a change in flask-allows itself. You could try pinning werkzeug to a lower version where the import path is still intact.

[pjvandehaar]

Okay, thanks for responding! Sorry for being grumpy, I was just tired after working spending too long on this, and then seeing that requirements.txt pinned a version of werkzeug that won't work. Thanks for all your work on this project!