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

zlib + pytables 3.4.2 + matplotlib = segfault on savefig when tables imported first #126

Closed
jeanconn opened this issue Apr 4, 2019 · 7 comments
Labels

Comments

@jeanconn
Copy link
Contributor

jeanconn commented Apr 4, 2019

zlib + pytables 3.4.2 + matplotlib = segfault on savefig when tables imported first (zlib does not need to be imported for things to go wrong).

It looks like the workarounds are to import matplotlib before tables or import zlib before matplotlib. Looks like this is fixed in newer versions of pytables and/or zlib.

@jeanconn jeanconn added the bug label Apr 4, 2019
@jeanconn
Copy link
Contributor Author

jeanconn commented Apr 4, 2019

@taldcroft I'm not sure if there is a more useful place to put this as a "gotcha" with our current ska3-flight.

@taldcroft
Copy link
Member

Can we upgrade to the newer version(s) without the problem?

@jeanconn
Copy link
Contributor Author

jeanconn commented Apr 4, 2019

I think we have the last pytables before everything breaks, but I also confess I don't remember where things were with pytables issues.

@jeanconn
Copy link
Contributor Author

jeanconn commented Apr 4, 2019

Yeah, pytables 3.4.2 is the last one available for our old versions of things. Else we would have updated already to try to fix #84 . I can look again at our own source-built conda package #127 or we can let the versions of things start to differ much more significantly between 32bit and 64bit.

@javierggt
Copy link
Contributor

This issue becomes irrelevant after shiny, so will close.

No idea if this was ever fixed, but does somebody care now?

@jeanconn
Copy link
Contributor Author

Similar to the other issues you are closing (thanks!) I think it makes sense to assume these are fixed and we can always open new issues. This one is the kind of thing that was order dependent and weird... but apparently I didn't write up a test and there also isn't enough here to really help us if it turns up again.

@javierggt
Copy link
Contributor

yes, I figure these things could "in principle" happen, but might be unlikely considering so much changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants