<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">2009/12/4 Martin SCHREIBER <span dir="ltr"><<a href="mailto:schreiberx@googlemail.com">schreiberx@googlemail.com</a>></span><br>
hi!<br><br>
i've got a new point for the wishlist (attached).<br>
has someone time handle this?<br></blockquote><div><br>we've been discussing it on the list :)<br> </div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<br>
the main reason, why i'm writing this email is that i'd like to create a<br>
new debian package with the new changes on the git repos and the python<br>
bindings. how about a new minor release?<br></blockquote><div><br>um ok, I think we just need to apply the python patches and release.<br><br>as for the wishlist, i don't think we should implement that in a minor release, i think it should be done by breaking the API and forcing users to double-check their code to ensure that they are using kdtree the correct way. I suspect a lot of people have assumed that (eg) count_within_range() counts within a radius rather than a box.<br>
<br><br><br><br>so guys, how about a major release too?<br><br> </div>
I would look at using my paulharris/region branch as the next release. It should need only small changes to support the new _radius() methods etc.<br><br>I don't have much time to do all the work myself, so if people can at least try out the branch with their own projects, to check that it works for everyone, that would be good.<br>
<br>And of course, the python bindings will need to be updated, and i need to apply those patches that were sent through by Willi before. Probably better to wait until after the API has been broken before updating the python bindings.<br>
<br>If everyone is happy with my branch, then it can become the next release (0.7.3 or 0.8.0 ? maybe 0.8.0 to indicate a big change like the API change).<br><br>For those that don't know how to get the code, its not hard... assuming you have git installed, do the following:<br>
<br>git clone git://<a href="http://git.debian.org/git/libkdtree/libkdtree.git">git.debian.org/git/libkdtree/libkdtree.git</a><br>cd libkdtree<br>git checkout -b paulharris/region origin/paulharris/region<br><br>and thats it... you have the code!<br>
then when you see new changes applied to that branch, just do <br>git pull<br><br>and that should update the checkout.<br><br>cheers<br>Paul<br><br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
thx,<br>
martin<br>
<font color="#888888"><br>
--<br>
<br>
<a href="http://www.martin-schreiber.info" target="_blank">http://www.martin-schreiber.info</a><br>
<br>
| Martin Schreiber<br>
| Enzianstrasse 7, S 104<br>
| 85748 Garching bei Muenchen<br>
| GERMANY<br>
</font><br><br>---------- Forwarded message ----------<br>From: Yaroslav Halchenko <<a href="mailto:debian@onerussian.com">debian@onerussian.com</a>><br>To: Debian Bug Tracking System <<a href="mailto:submit@bugs.debian.org">submit@bugs.debian.org</a>><br>
Date: Thu, 03 Dec 2009 09:19:26 -0500<br>Subject: Bug#559312: libkdtree++-dev: Please provide C++ implementation of "find_within_radius" exposed in Python interface<br>Package: libkdtree++-dev<br>
Version: 0.7.0-1<br>
Severity: wishlist<br>
<br>
<br>
It is quite a common need to find points within a specified sphere. It would<br>
be great to have such simple addendum (filter) on top of find_within_range<br>
within C++ library exposed in Python. Even a brute force implementation might<br>
be reasonable I guess ;)<br>
<br>
-- System Information:<br>
Debian Release: squeeze/sid<br>
APT prefers unstable<br>
APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental')<br>
Architecture: amd64 (x86_64)<br>
<br>
Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)<br>
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)<br>
Shell: /bin/sh linked to /bin/bash<br>
<br>
-- no debconf information<br>
<br>
<br>
<br>_______________________________________________<br>
libkdtree-devel mailing list<br>
<a href="mailto:libkdtree-devel@lists.alioth.debian.org">libkdtree-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/libkdtree-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/libkdtree-devel</a><br>
<br></blockquote></div><br>