Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New release to update `gherkin`?

Open Beginner friendly
#838 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
release

Research direction

Start by reviewing pytest-bdd pull request 753 and issue 752, then check how the project currently pins gherkin-official. Update the release to pick up the newer version, and confirm that the reported pytest deprecation warning is resolved.

Written by the indexing model from the issue text.

Description

Hi! Getting a warning when using pytest from gherkin, the issue is resolved in gherkin-official 30.0.3 (Nov 2024), but the last pytest-bsdd release was a while ago (Dec 2024) and resolves to gherkin-official==29.0.0, which is resolved in https://github.com/pytest-dev/pytest-bdd/pull/753 / https://github.com/pytest-dev/pytest-bdd/issues/752

Any chance for a new release, to pick up the more recent gherkin?

  ../../blender-5.2.0-linux-x64/5.2/python/lib/python3.13/site-packages/gherkin/gherkin_line.py:79: 40 warnings                                                                                                                               
    /home/runner/work/IfcOpenShell/IfcOpenShell/blender-5.2.0-linux-x64/5.2/python/lib/python3.13/site-packages/gherkin/gherkin_line.py:79: DeprecationWarning: 'maxsplit' is passed as positional argument                                   
      uncommented_line = re.split(r"\s#", self._trimmed_line_text.strip(), 2)[0]                                                                                                                                                              
Dominant language
Python
Stars
1.5k
Forks
252
Avg merge
2h 8m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pytest-dev/pytest-bdd

All issues in pytest-dev/pytest-bdd

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.