I would be just fine making 2017 the target for 3.0 and some level of API 
breaks and cleanups. There are already a pile of methods marked “deprecated” in 
the code.

I don’t think it’s worth changing atom indexing - but anything else should be 
on the table.

-Geoff

> This is an API breakage, but only because these internal
> implementation functions were exposed. I think the time might be ripe
> for a couple of API cleanups, not for the sake of it, but where they
> limit or affect the toolkit's usage.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel

Reply via email to