-
Notifications
You must be signed in to change notification settings - Fork 4
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
Decimation API changed #90
Comments
Hi @jo-mueller , how about pinning the vedo version? They are breaking the API all the time causing efforts on our side. Or are there any new features in vedo, that we need here? Thanks! Best, |
Hi @haesleinhuepf ,
This would probably work. I would have to go through the past few version though to see which change was introduced when. Would you be ok in fixing the last two changes (this issue and #87 ) and then pinning it? I am now a vedo maintainer so I can hopefully avert these kinds of breaking changes in the future :) |
Awesome! Do you want to take over this repository too? It would be your decision then. |
I wouldn't mind :) Would you then leave it here or would you prefer moving the repository elsewhere? Edit: tag :) @haesleinhuepf |
Hi @haesleinhuepf ,
some of the more recent versions of vedo introduced some more API changes. In particular, the
method
keyword of thedecimate
function doesn't exist anymore - there are now separate functionsdecimate
,decimate_pro
anddecimate_binned
. Will send a PR to fix this and pinpoint vedo to a newer version.Sidenote: This will probably make issue #87 more pressing. There are likely more problems with newer APIs (see also PR #88)
The text was updated successfully, but these errors were encountered: