Ignoring foo: markers 'bar' don't match your environment
See original GitHub issueIgnoring colorama: markers 'sys_platform == "win32"' don't match your environment
Ignoring configparser: markers 'python_version < "3.2"' don't match your environment
Ignoring enum34: markers 'python_version < "3.4"' don't match your environment
Ignoring funcsigs: markers 'python_version < "3.0"' don't match your environment
I’ve started getting the above errors whenever I install packages with pipenv into a pipenv created virtualenv.
I use the following command to install some base packages into each virtualenv:
❯ pipenv install --dev flake8 jedi importmagic epc autopep8 yapf pytest json-rpc service_factory autoflake hy isort bpython
Everytime I do, I get the warnings. It never used to be like that untill the recent homebrew python/python@2 updates. I don’t know if it’s got anything to do with it.
Expected result
Adding bpython to Pipfile's [dev-packages]…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (e8633e)!
Installing dependencies from Pipfile.lock (e8633e)…
🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 31/31 — 00:00:02
Actual result
Adding bpython to Pipfile's [dev-packages]…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (e8633e)!
Installing dependencies from Pipfile.lock (e8633e)…
Ignoring colorama: markers 'sys_platform == "win32"' don't match your environment
Ignoring configparser: markers 'python_version < "3.2"' don't match your environment
Ignoring enum34: markers 'python_version < "3.4"' don't match your environment
Ignoring funcsigs: markers 'python_version < "3.0"' don't match your environment
🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 31/31 — 00:00:02
Steps to replicate
❯ pipenv install --dev selenium
❯ cat Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
[dev-packages]
"flake8" = "*"
jedi = "*"
importmagic = "*"
epc = "*"
"autopep8" = "*"
yapf = "*"
pytest = "*"
json-rpc = "*"
service-factory = "*"
autoflake = "*"
hy = "*"
isort = "*"
bpython = "*"
selenium = "*"
[requires]
python_version = "3.6"
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Adding a default extra_require environment - Packaging
See the message: Ignoring numpy: markers 'extra != ""' don't match your environment => It's good. But the rest ends up in a...
Read more >Working with custom markers — pytest documentation
In this example the mark “foo” will apply to each of the three tests, whereas the “bar” mark is only applied to the...
Read more >BashPitfalls - Greg's Wiki
In the first form, [ is the command name, and bar, =, the expansion of "$foo", and ] are separate arguments to it....
Read more >Karate | Test Automation Made Simple.
Since these are tests and not production Java code, you don't need to be bound by the com.mycompany.foo.bar convention and the un-necessary explosion...
Read more >The mypy configuration file - mypy 0.991 documentation
matches dotted_module_name and any submodules (so foo.bar. ... Use the MYPY_CONFIG_FILE_DIR environment variable to refer to paths relative to the config ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s fixed in 2018.11.14
Ah ha, no I didn’t, that has fixed the issue! Thanks for the tip.
For anyone else trying to remedy this, make sure you
pip install --upgrade pipenv
outside and inside your project’s virtualenv. I rebuilt my lockfile byrm
ing it and thenpipenv install
ing, but there is probably a better way to do that.