Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PYTHON: Fix tox configuration for Python 2.7 #50

Merged
merged 1 commit into from
Mar 20, 2022

Conversation

jenisys
Copy link
Contributor

@jenisys jenisys commented Mar 20, 2022

🤔 What's changed?

⚡️ What's your motivation?

Fix a problem for using tox -e py27 for running test in an isolated virtual-environment for Python 2.7.
This case was disabled during the latest when it was discovered.
The problem is fixed for now (until the real problem is fixed).

🏷️ What kind of change is this?

  • 🐛 Bug fix (non-breaking change which fixes a defect)

♻️ Anything particular you want feedback on?

No.

📋 Checklist:

  • I agree to respect and uphold the Cucumber Community Code of Conduct
  • I've changed the behaviour of the code
    • I have added/updated tests to cover my changes.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • Users should know about my change
    • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

* Fixes a problem in DEVELOPMENT support
* Problem seems to be related to macOS 12 Monterey
  SEE: pypa/virtualenv#2284
* Use special section in "tox.ini" and
  use "pip install --user ..." to fix the problem for now.
* ADDED: "py27" to "envlist" again.
@jenisys jenisys merged commit d7a40e4 into cucumber:main Mar 20, 2022
@jenisys jenisys deleted the python/fix_tox_for_python2.7 branch October 20, 2024 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant