Skip to content

Unpin pytest #26625

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

Closed
wants to merge 2 commits into from
Closed

Unpin pytest #26625

wants to merge 2 commits into from

Conversation

alimcmaster1
Copy link
Member

Follow up from #26619. Since pytest have just done a point release for 4.6.1 we should be good to remove the pin.

pytest-dev/pytest#5358

cc @simonjayhawkins

@simonjayhawkins simonjayhawkins added Build Library building on various platforms CI Continuous Integration labels Jun 3, 2019
@codecov
Copy link

codecov bot commented Jun 3, 2019

Codecov Report

Merging #26625 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26625      +/-   ##
==========================================
- Coverage   91.87%   91.87%   -0.01%     
==========================================
  Files         174      174              
  Lines       50692    50692              
==========================================
- Hits        46575    46571       -4     
- Misses       4117     4121       +4
Flag Coverage Δ
#multiple 90.41% <ø> (ø) ⬆️
#single 41.78% <ø> (-0.09%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️
pandas/core/frame.py 97% <0%> (-0.12%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6354580...d2beb74. Read the comment docs.

@codecov
Copy link

codecov bot commented Jun 3, 2019

Codecov Report

Merging #26625 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26625      +/-   ##
==========================================
- Coverage   91.88%   91.87%   -0.01%     
==========================================
  Files         174      174              
  Lines       50692    50692              
==========================================
- Hits        46576    46572       -4     
- Misses       4116     4120       +4
Flag Coverage Δ
#multiple 90.41% <ø> (ø) ⬆️
#single 41.8% <ø> (-0.09%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️
pandas/core/frame.py 97% <0%> (-0.12%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6354580...08c8159. Read the comment docs.

@alimcmaster1
Copy link
Member Author

Interestingly I think there still might be an issue with the pytest release based on:

   def manual_compare_stacked(df, df_stacked, lev0, lev1):
>       assert all(df.loc[row, col] ==
                   df_stacked.loc[(row, col[lev0]), col[lev1]]
                   for row in df.index for col in df.columns)
E       NameError: name 'col' is not defined

will take a further look tomorrow

@alimcmaster1
Copy link
Member Author

bumped up to latest pytest release which should fix this - CI running..

@gfyoung
Copy link
Member

gfyoung commented Jun 5, 2019

@jreback : How does it work when it comes to developer dependencies? Should we be bumping version requirements this high to be the latest version?

@jreback
Copy link
Contributor

jreback commented Jun 5, 2019

doesn’t make sense to bump this - we try to move very slowly in things like thus

@jreback jreback closed this Jun 5, 2019
@alimcmaster1
Copy link
Member Author

Given that pandas tests will fail running with pytest version 4.6.0 and 4.6.1 doesn’t it make sense to enforce this in the dependencies? ( yes we could do this by keeping the current pin in place ).

But keeping it pinned means nothing in CI will draw our attention to any future breaking pytest changes? Potentially making it harder to update further down the road. What do you think ?

@jreback
Copy link
Contributor

jreback commented Jun 5, 2019

these are 3.5 builds only - pinning is ok

to be honest could pin them to a much earlier version
say 4.02 would be good (or for that would be ok)

all other builds float to the latest

@alimcmaster1 alimcmaster1 deleted the ali-unpin branch December 25, 2019 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Library building on various platforms CI Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants