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

chore(deps): remove seaborn upper limit #1570

Merged
merged 4 commits into from
Apr 9, 2024

Conversation

ggydush
Copy link
Contributor

@ggydush ggydush commented Apr 3, 2024

Seaborn 0.13 fixes an issue with annotating heatmaps and I'd like to be able to use ydata-profiling in a repository that needs this fix.

I checked git blame and didn't see a reason for the upper-bound pin. I tested on 0.13.2 with Python 3.10 and all unit tests passed.

Signed-off-by: ggydush <greggydush@gmail.com>
@ggydush ggydush changed the title build: Update seaborn upper limit build: Remove seaborn upper limit Apr 3, 2024
@fabclmnt fabclmnt self-requested a review April 4, 2024 16:03
Copy link
Contributor

@fabclmnt fabclmnt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ggydush ,

thank you for your contribution. Nevertheless, and due to past experiences where new minor releases from packages like numpy, seaborn or matplotlib have broken the functionality of ydata-profiling we have decided to analyze case by case the versions that we support.

We can consider upgrading seaborn, but we will need to define an upper version.

@ggydush
Copy link
Contributor Author

ggydush commented Apr 5, 2024

Would you be okay with upper pin on latest (0.13.2) provided tests pass?

Signed-off-by: ggydush <greggydush@gmail.com>
@ggydush ggydush requested a review from fabclmnt April 5, 2024 18:29
ggydush and others added 2 commits April 5, 2024 11:29
@fabclmnt
Copy link
Contributor

fabclmnt commented Apr 5, 2024

Yes totally! That would do.

Tests are now running.

@fabclmnt fabclmnt changed the title build: Remove seaborn upper limit feat: Remove seaborn upper limit Apr 5, 2024
@fabclmnt fabclmnt changed the title feat: Remove seaborn upper limit chore(deps): remove seaborn upper limit Apr 5, 2024
Copy link

codecov bot commented Apr 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.19%. Comparing base (28ee3da) to head (15a8426).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1570   +/-   ##
========================================
  Coverage    90.19%   90.19%           
========================================
  Files          195      195           
  Lines         6394     6394           
========================================
  Hits          5767     5767           
  Misses         627      627           
Flag Coverage Δ
py3.8-ubuntu-22.04-pandas 90.19% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ggydush
Copy link
Contributor Author

ggydush commented Apr 5, 2024

Thank you for approving! Is there any chance this could be included in the next release?

@alexbarros
Copy link
Contributor

alexbarros commented Apr 8, 2024

@fabclmnt you can merge, the lint error is a problem in the actions itself, that is already fixed in dev

@fabclmnt fabclmnt merged commit 245ca1b into ydataai:develop Apr 9, 2024
15 of 17 checks passed
@fabclmnt
Copy link
Contributor

fabclmnt commented Apr 9, 2024

@ggydush yes this will be included for the next release. Probably either this week or beginning of the next.

Thank you for your contribution.

@ggydush
Copy link
Contributor Author

ggydush commented Apr 23, 2024

Any chance this could be released?

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.

3 participants