pkg_resources.extern.packaging.markers.UndefinedEnvironmentName Exception

[willypuzzle]

When I try the command:

$pybabel extract -F babel.cfg -o messages.pot .

I receive this output:

...
extracting messages from app/templates/auth/login.html (extensions="jinja2.ext.autoescape,jinja2.ext.with_")
Traceback (most recent call last):
File "/var/www/python/flask-foundation/env/bin/pybabel", line 11, in
sys.exit(main())
...
pkg_resources.extern.packaging.markers.UndefinedEnvironmentName: 'extra' does not exist in evaluation environment.

Why? I read it can depend from pip but I have the last upgraded version. This is my babel.cfg file:

[python: **.py]
[jinja2: **/templates/**.html]
extensions=jinja2.ext.autoescape,jinja2.ext.with_

I use python 3.

[halfnibble]

I'm having this issue now. Latest Ubuntu LTS and its latest Python3 and pip.

[benselme]

Could it be the same problem as in this issue ?
getsentry/sentry#3143

[Mark-Wellings]

I'm afraid it's not the same issue. Just tried downgrading and it didnt work. If you dont reference jinja2 it does run, but for me creates an empty messages.pot
babel.cfg

[python: **/FlaskApp/**.py]

encoding = utf-8
extensions=jinja2.ext.autoescape,jinja2.ext.with_,webassets.ext.jinja2.AssetsExtension
silent=False

[akx]

@Mark-Wellings Could you create a repo with a minimal test case that exhibits this problem?

[Mark-Wellings]

I think my issue was related to how my app is organized. Reading all *.py files on the server gave me an error. Now I've got it set up so that it only reads init.py, that's the babel.cfg

[python: **__.py]
[jinja2: **.html]
encoding = utf-8
extensions=jinja2.ext.autoescape,jinja2.ext.with_
silent=False

[guoweikuang]

After upgrading setuptools (pip install --upgrade setuptools) from 20.7.0 to 35.0.1 it works now.

[akx]

Closing this as it seems upgrading setuptools will fix this issue. :)

[horejsek]

It happens again with setuptools 39.2.0, works until 39.1.0.

[JimmyTheNerd]

It happens again with setuptools 39.2.0, works until 39.1.0.

Works with setuptools 40.5.0.

[trideceth12]

It happens again with setuptools 39.2.0, works until 39.1.0.

Works with setuptools 40.5.0.

Not for me.. I had to pip install setuptools==39.1.0 to fix this ( I was on 40.5.0 before)