Ummm ... "I'm buried under a project right now, and I won't be able to get back to you until next Friday." My day job has been burning up a lot of time, and we had an important Family Occasion on Saturday that ate the entire weekend. Sorry. I will try to do better at context switching.
You are heading in exactly the correct direction with the test suite. As for a single copy of the source -- would it work to keep the stand-alone (Iron Python) distribution in the /adodbapi directory on GitHub, and just ignore the extra files (for the big distribution) by not putting them in the main manifest? @Mark -- please chime in here... > On Mon, Feb 19, 2018 at 11:59 AM, Bob Kline <bkl...@rksystems.com> wrote: > >> On Mon, Feb 19, 2018 at 11:18 AM, Vernon D. Cole <vernondc...@gmail.com> > wrote: > >> > >>> Sounds like a good plan. > >> > >> As in, "yes, let's consolidate the project in one place (under pywin > >> on GitHub)"? Or did you mean "yes, I agree we should have the > >> discussion about whether we have to maintain the package in more than > >> one place"? If the former, I'll be happy to get the ball rolling by > >> starting the analysis for topping up the GitHub repo from the > >> SourceForge oledbapi repo. If the latter, I guess the first step in > >> that discussion would be for you to lay out the reason(s) why it > >> wouldn't work to maintain the project just on GitHub (under pywin). Or > >> perhaps you intended some third interpretation of "good plan." > >> > >> Cheers, > >> Bob > >> >
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
