Mark:<br>adodbapi.py is now in the pywin32 CVS. It is the version I have been running for a few months, there are differences only in documentation compared to the adodbapi CVS source tree. There are three outstanding issues, very minor, which I will address in the next few weeks, and will update the source here as soon as I have confidence in the newer version.
<i></i> I did not want to miss a release window by trying for a perfect module.<br><br> I made a new sub-tree as you suggested. Unfortunately, I blew my first try and created a tree one level too high. I have sent in a support request for sourceforge to prune off my incorrect entry. Hopefully they will be able to do that before anyone does a check out of the error. Makes me feel really clumsy!
<br><br>I have not made any changes to setup.py -- so nothing will be installed until you add the code to do that. I am loath to mess with the installer myself, especially after having just made such a major foul-up on CVS. (Grrrr!)
<br>--<br>Vernon<br><div class="gmail_quote">----<br>On Aug 24, 2007 7:09 PM, Mark Hammond <<a href="mailto:mhammond@skippinet.com.au">mhammond@skippinet.com.au</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just following up from Roger's comments (which I agree with):<br><div class="Ih2E3d"><br>> The existing directory tree looks like this:<br>> -- adodbapi-2.1<br>> ..--adodbapi<br>> ....--__init__.py<br>> ....--
adodbapi.py<br>> ..--tests<br>> ....--adodbapitest.py<br>> ....--adodbapitestconfig.py<br>> ....--adbapi20.py (and so forth)<br>> ..--license.txt<br>> ..--readme.txt<br>> ..--setup.py<br>><br>
> I understand nothing about the magic whereby the source in the CVS tree<br>> becomes the install file that I run on a target system. So my question<br>> is:<br>> would /pywin32/adodbapi/adodbapy/adodbapi.py be the correct place to
<br><br></div>Did you mean 'adodbapy' there?<br><br>> put the source?<br><br>I'd be inclined to drop a level here by making 'tests' a sub-package. So<br>you would end up with:<br><br>-- adodbapi<br>
<div class="Ih2E3d">..--__init__.py<br>..--adodbapi.py<br>..--tests<br>....--adodbapitest.py<br>....--adodbapitestconfig.py<br>....--adbapi20.py (and so forth)<br>..--license.txt<br>..--readme.txt<br><br></div>and presumably:
<br>..--setup.py<br><br>will no longer be necessary (I don't think its worth still supporting<br>creating a stand-alone package). On the other hand, this may not scale as<br>well for the future (eg, 'docs' would need to be a child of the package too
<br>- but is that really a problem?). I'll leave this as your call though.<br><br>Cheers,<br><font color="#888888"><br>Mark<br><br><br></font></blockquote></div><br>