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

Why does seleniumbase rely on outdated iniconfig and pytest-html? #3619

Closed
kwilsonmg opened this issue Mar 20, 2025 · 1 comment
Closed

Why does seleniumbase rely on outdated iniconfig and pytest-html? #3619

kwilsonmg opened this issue Mar 20, 2025 · 1 comment
Labels
question Someone is looking for answers

Comments

@kwilsonmg
Copy link

Is there a specific reason as to why this requires specifically pytest-html==4.0.2 and iniconfig==2.0.0? pytest-html is now up to version 4.1.1 and iniconfig version 2.1.0. I wonder if it might be possible to have looser versioning rather than tying it to a specific sub-version release? In larger projects with other dependencies this can cause a version conflict.

In my example:

seleniumbase 4.35.7 requires iniconfig==2.0.0, but you have iniconfig 2.1.0 which is incompatible.
seleniumbase 4.35.7 requires pytest-html==4.0.2, but you have pytest-html 4.1.1 which is incompatible.
@mdmintz mdmintz added the question Someone is looking for answers label Mar 20, 2025
@mdmintz
Copy link
Member

mdmintz commented Mar 20, 2025

Dependencies get updated regularly whenever there's a release.
These ones are already set to be upgraded at the next one:

Image

As for pytest-html==4.0.2, that's going to stay where it is because there's a bug in the latest version: #3318

@mdmintz mdmintz closed this as completed Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Someone is looking for answers
Projects
None yet
Development

No branches or pull requests

2 participants