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.

Sign up for GitHub

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

Jump to bottom

Decide what we want to do with scalloc #96

Open
jvoisin opened this issue Dec 23, 2021 · 1 comment
Open

Decide what we want to do with scalloc #96

jvoisin opened this issue Dec 23, 2021 · 1 comment
Assignees
@mjp41 @daanx
Labels
question Further information is requested

Comments

@jvoisin
Copy link
Collaborator

jvoisin commented Dec 23, 2021

scalloc hasn't been updated since 2016, and uses the gyp build system which is broken with python3.10.

What we keep it, even if it's not building in the CI?
If so, shall we spend time trying to fix its build system working with upstream?
@jvoisin jvoisin added the question Further information is requested label Jan 2, 2022
@daanx
Copy link
Owner

daanx commented Feb 5, 2022

I think it is fine to leave it in "as is" since it is not build or used by default (right?). That may help in case it gets revived

@jvoisin jvoisin mentioned this issue Feb 5, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mjp41 mjp41

@daanx daanx

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mjp41 @jvoisin @daanx