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 segyio #815

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Add segyio #815

wants to merge 3 commits into from

Conversation

jtpio
Copy link
Contributor

@jtpio jtpio commented Feb 26, 2024

try without cross-python
@jtpio
Copy link
Contributor Author

jtpio commented Mar 21, 2024

Thanks @DerThorsten !

Do you know what may be causing the CI failure?

@DerThorsten
Copy link
Contributor

Thanks @DerThorsten !

Do you know what may be causing the CI failure?

So initially it says that cross python is leaking some stuff outside the cross-python env...this is why I tried without cross env.
But that did not work out.

If segyio is important I can put more serious effort in it and try a local build of it (debugging trough the CI is never a good idea)

@jtpio
Copy link
Contributor Author

jtpio commented Mar 21, 2024

If segyio is important

The main motivation was to maybe document how folks could make their repos compatible with repo2jupyterlite as an alternative to Binder, in the context of jupyterlite/repo2jupyterlite#9. Because it started from a real world use case with this repo: https://github.com/stevejpurves/seg_tutorial

I was thinking that this could serve as an example where a package can't be installed automatically with repo2jupyterlite / jupyterlite-xeus, and needs to be packages for emscripten-forge.

But we could use another package as an example.

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.

2 participants