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

Add a constraint on pyrsistent for Python 2.7 #31

Merged
merged 1 commit into from Sep 12, 2020

Conversation

alalazo
Copy link
Member

@alalazo alalazo commented Sep 12, 2020

Extra safety to avoid Python 2.7 tests failure. See:

tobgu/pyrsistent#205
tobgu/pyrsistent#207
tobgu/pyrsistent#208

@alalazo alalazo added the bug Something isn't working label Sep 12, 2020
@codecov-commenter
Copy link

codecov-commenter commented Sep 12, 2020

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   93.20%   93.20%           
=======================================
  Files           7        7           
  Lines         368      368           
=======================================
  Hits          343      343           
  Misses         25       25           
Flag Coverage Δ
#unittests 93.20% <ø> (ø)

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


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 7a32737...10dea58. Read the comment docs.

@boegel boegel merged commit b221d5d into master Sep 12, 2020
@boegel boegel deleted the qa/constrain_pyrsistent_on_py27 branch September 12, 2020 18:36
alalazo added a commit that referenced this pull request Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants