On Sun, Feb 25, 2018 at 6:18 PM, Mark Hammond <mhamm...@skippinet.com.au> wrote:
> 1) There's a relatively easy fix that can be made to the copy of adodbapi > which is inside pywin32. Right. Basically, I think what needs to happen is for the fork on GitHub to be brought in sync with the working code on SF. I'm going to guess it's not quite as simple as that, because we'd want to be careful to preserve any patches which got applied on GitHub, but didn't make it to the original repo. Don't know for sure that there are any, but we should check. > 2) There's a concern regarding some IronPython bindings for adodbapi which > aren't in pywin32 and Vernon was asking something whether they should also > be included in pywin32. As I understand it, the code to support IronPython is already included in what's on GitHub. I think Vernon's hoping that there's a way to script an export of just the adodbapi portion of your GitHub repo for the use of the IronPython users (who, as you correctly point out, have no use for the pywin32 bits). If that's possible (and I can't see why it wouldn't be, as GitHub is pretty easy to script), he would be able to avoid the tedium and risks involved in having to maintain the same code base in two different places. It would also eliminate the "where am I supposed to file bugs" confusion, as well as make it easier to persuade others to assist with maintenance of the code. Most of the adodbapi code is common for IronPython and CPython users, and I don't see that the presence of "if IronPython: ..." code in the mhammond/pywin32 repo does any harm (after all, it's already there and I'll bet no one has noticed). I hope that makes things a little clearer. But this explanation is speculation on my part, and I should really let Vernon say what he means for #2. Regards, Bob _______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
