Poetry: Poetry UserWarning: warn_ungrouped_named_tokens_in_collection

Created on 23 Jul 2019  路  15Comments  路  Source: python-poetry/poetry

  • [x] I have searched the issues of this repo and believe that this is not a duplicate.
  • [x] I have searched the documentation and believe that my question is not covered.

Question

/home/zach/project/.venv/lib/python3.7/site-packages/poetry/version/requirements.py:170: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'specifier' on And expression collides with '_original_end' on contained expression
  VERSION_SPEC = originalTextFor(_VERSION_SPEC)("specifier")
/home/zach/project/.venv/lib/python3.7/site-packages/poetry/version/requirements.py:173: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'marker' on And expression collides with '_original_end' on contained expression
  MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")

I've been seeing the above warning messages while using poetry commands such as

poetry install
poetry run
poetry shell

I pip installed poetry 0.12.17 in my Python 3.7.0 virtual environment.

Most helpful comment

Pyparsing 2.4.2 (pushed to PyPI this evening) disables these warnings by default

All 15 comments

I saw this in a completely different package build

/usr/local/lib/python3.6/dist-packages/packaging/requirements.py:57: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'specifier' on And expression collides with '_original_end' on contained expression
  VERSION_SPEC = originalTextFor(_VERSION_SPEC)("specifier")
/usr/local/lib/python3.6/dist-packages/packaging/requirements.py:60: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'marker' on And expression collides with '_original_end' on contained expression
  MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")

But i'm not using poetry

py3-test installed: alabaster==0.7.12,appdirs==1.4.3,asn1crypto==0.24.0,astroid==2.2.5,atomicwrites==1.3.0,attrs==19.1.0,Babel==2.7.0,bcrypt==3.1.7,black==19.3b0,certifi==2018.1.18,cffi==1.12.3,chardet==3.0.4,Click==7.0,coverage==4.5.3,cryptography==2.7,docutils==0.15,filelock==3.0.12,idna==2.6,imagesize==1.1.0,importlib-metadata==0.18,isort==4.3.21,Jinja2==2.10.1,keyring==10.6.0,keyrings.alt==3.0,lazy-object-proxy==1.4.1,lxml==4.3.4,MarkupSafe==1.1.1,mccabe==0.6.1,more-itertools==7.2.0,packaging==19.0,paramiko==2.6.0,pluggy==0.12.0,py==1.8.0,pycodestyle==2.5.0,pycparser==2.19,pycrypto==2.6.1,pydocstyle==4.0.0,pyflakes==2.1.1,Pygments==2.4.2,pygobject==3.26.1,pylama==7.7.1,pylama-pylint==3.1.1,pylint==2.3.1,PyNaCl==1.3.0,pyparsing==2.4.1,pytest==5.0.1,pytest-cov==2.7.1,python-distutils-extra==2.39,pytz==2019.1,pyxdg==0.25,requests==2.18.4,SecretStorage==2.3.1,six==1.12.0,snowballstemmer==1.9.0,Sphinx==2.1.2,sphinxcontrib-applehelp==1.0.1,sphinxcontrib-devhelp==1.0.1,sphinxcontrib-htmlhelp==1.0.2,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.2,sphinxcontrib-serializinghtml==1.1.3,ssh-import-id==5.7,toml==0.10.0,tox==3.13.2,typed-ast==1.4.0,urllib3==1.22,virtualenv==16.7.0,wcwidth==0.1.7,wrapt==1.11.2,zipp==0.5.2

Seems to be an issue with pyparsing 2.4.1, as reverting it to 2.4.0 no longer shows the warning.

@amarshall Confirmed! Reverted to pyparsing==2.4.0 the warning messages disappeared. Now the question is why :thinking:

Got the same issue, but there isn't pyparsing in dependencies. Here is my pyproject.toml
```
[tool.poetry.dependencies]
python = "^3.7.0"
asyncio = "^3.4"
aiohttp = "^3.4"
motor = "^2.0"
umongo = "^1.0"
pyyaml = "^3.13"

[tool.poetry.dev-dependencies]
pytest = "^3.4"
black = {version = "^18.3-alpha.0",allows-prereleases = true}
mypy = "^0.650.0"
wemake-python-styleguide = "^0.5.1"
pytest-mock = "^1.10"
pytest-asyncio = "^0.9.0"
pytest-aiohttp = "^0.3.0"

@Skufler Could you double check your poetry.lock file?

Just ran some tests, it seems like doing pip install poetry==0.12.16 installs pyparsing==2.4.1. I'd guess it installs the same version with poetry==0.12.17

@zachliu
Yes, you can check by yourself
lock.txt

pyparsing 2.4.1 has been removed from pypi :laughing:

pyparsing 2.4.1 has been removed from pypi laughing

Yeah :) 2.4.1.1 is 2.4.1, see https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.1.1

pyparsing 2.4.1 has been removed from pypi laughing

Yeah :) 2.4.1.1 is 2.4.1, see https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.1.1

pyparsing 2.4.1.1 still causes this warning :man_facepalming:

Can also confirm. Due to how my project's CI pipelines work, I am getting about thirty of these mangled with my other output each time my pipelines run :sweat_smile:

/code/hikari/.nox/format_check/lib/python3.7/site-packages/poetry/version/requirements.py:170: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'specifier' on And expression collides with '_original_end' on contained expression
  VERSION_SPEC = originalTextFor(_VERSION_SPEC)("specifier")
/code/hikari/.nox/format_check/lib/python3.7/site-packages/poetry/version/requirements.py:173: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'marker' on And expression collides with '_original_end' on contained expression
  MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")

Pyparsing 2.4.2 (pushed to PyPI this evening) disables these warnings by default

Pinned Pyparsing to 2.4.2 in my lock file. Everything is hunky-dory. Thank you guys.

Pyparsing 2.4.2 is not solving this problem for me:

/usr/local/lib/python3.6/dist-packages/poetry/version/requirements.py:170: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'specifier' on And expression collides with '_original_end' on contained expression
VERSION_SPEC = originalTextFor(_VERSION_SPEC)("specifier")
/usr/local/lib/python3.6/dist-packages/poetry/version/requirements.py:173: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'marker' on And expression collides with '_original_end' on contained expression

Here's my pyproject.toml:

[tool.poetry.dependencies]
python = ">=2.7, != 3.0.*, != 3.1.*, != 3.2.*, != 3.3.*"
selenium = "^3.14"
future = "^0.16.0"

[tool.poetry.dev-dependencies]
pytest = "^3.0.6"
pylama = {version = "^7.6", python = ">= 3.4" }
pylint = { version = "^2.2", python = ">= 3.4" }
pytest-cov = "^2.6"
black = { version = "18.9b0", python = ">= 3.6" }
sphinx = { version = "^2.0", python = ">= 3.5" }
mock = "^1.3.0"

This is in my poetry.lock:

[[package]]
category = "dev"
description = "Python parsing module"
marker = "python_version >= \"3.5\""
name = "pyparsing"
optional = false
python-versions = ">=2.6, !=3.0.*, !=3.1.*, !=3.2.*"
version = "2.4.2"

Pyparsing 2.4.2 is not solving this problem for me:

/usr/local/lib/python3.6/dist-packages/poetry/version/requirements.py:170: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'specifier' on And expression collides with '_original_end' on contained expression
VERSION_SPEC = originalTextFor(_VERSION_SPEC)("specifier")
/usr/local/lib/python3.6/dist-packages/poetry/version/requirements.py:173: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'marker' on And expression collides with '_original_end' on contained expression

Here's my pyproject.toml:

[tool.poetry.dependencies]
python = ">=2.7, != 3.0.*, != 3.1.*, != 3.2.*, != 3.3.*"
selenium = "^3.14"
future = "^0.16.0"

[tool.poetry.dev-dependencies]
pytest = "^3.0.6"
pylama = {version = "^7.6", python = ">= 3.4" }
pylint = { version = "^2.2", python = ">= 3.4" }
pytest-cov = "^2.6"
black = { version = "18.9b0", python = ">= 3.6" }
sphinx = { version = "^2.0", python = ">= 3.5" }
mock = "^1.3.0"

This is in my poetry.lock:

[[package]]
category = "dev"
description = "Python parsing module"
marker = "python_version >= \"3.5\""
name = "pyparsing"
optional = false
python-versions = ">=2.6, !=3.0.*, !=3.1.*, !=3.2.*"
version = "2.4.2"

What about pyparsing 2.4.0?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sobolevn picture sobolevn  路  3Comments

probablykasper picture probablykasper  路  3Comments

alexlatchford picture alexlatchford  路  3Comments

jbarlow83 picture jbarlow83  路  3Comments

jeremy886 picture jeremy886  路  3Comments