That sounds fine to me.
On 5/03/2018 6:53 am, Vernon D. Cole wrote:
Here is what I propose:
1) This time, rather than copy a selected (major) part of the adodbapi
source files over to their pywin32 directory,
I would copy _all_ of the files.
2) Adjust adodbapi/MANIFEST.in and setup.py to create a proper PyPi
submission from that directory.
That sounds good, but could you please tweak setup.py so that it sticks
the files into "../dist", so everything I need to release ends up in the
same dir.
You'll probably also need to tweak adodbapi on pypi so I can upload.
3) Adjust the pywin32 MANIFEST.in to include a subset of adodbapi files
that actually works.
4) Put a simple go/no-go test of adodbapi (perhaps ACCESS database only)
into the pywin32 test suite.
5) document in SourceForge that future updates will take place in the
pywin32 repo.
I guess I'll look forward to a PR :)
Cheers,
Mark
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
