Re: [python-win32] Bug reporting

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

Re: [python-win32] Bug reporting

I decided to meditate for a few days rather than answer immediately and poorly. After I took over maintenance of adodbapi in about 2003, I was struggling with how to properly document that most users (CPython) had to install pywin32 as a prerequisite. At that time the odbc sub-module had a couple

Re: [python-win32] Bug reporting

On 27/02/2018 5:40 am, Vernon D. Cole wrote: Second: the effective "bus size" of the adodbapi repo is *one*. The other three authorized maintainers are inactive.  Indeed, the way I got approved as a maintainer 15 years ago (has it really been that long?) was to document to SourceForge that the

Re: [python-win32] Bug reporting

There are two problems with the existing SourceForge repo of adodbapi. First, the manual copy of updates to the pywin32 code base can easily fail -- as it did several years ago and I missed the resulting error which remained unfixed for several releases of pywin32. That problem was exacerbated by

Re: [python-win32] Bug reporting

On Sun, Feb 25, 2018 at 6:18 PM, Mark Hammond 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

Re: [python-win32] Bug reporting

On 26/02/2018 1:12 am, Bob Kline wrote: On Sun, Feb 25, 2018 at 12:31 AM, Mark Hammond wrote: I'm afraid Bob is going to get quite frustrated if he gets upset about responses taking more than a few days to come in. I'm going to assume you hadn't yet read the

Re: [python-win32] Bug reporting

On Sun, Feb 25, 2018 at 12:04 PM, Preston Landers wrote: > Is there [any] reason you can't use PyODBC? A reasonable question. This is not for a new project. When it was first started the analysis of the available options for database connection libraries came to the

Re: [python-win32] Bug reporting

Bob, Is there are reason you can't use PyODBC? https://github.com/mkleehammer/pyodbc/wiki It is more actively maintained and I've used it successfully for years. I'm curious what adodbapi is doing for you that PyODBC can't? Are you using non-SQL data sources? thanks, Preston

Re: [python-win32] Bug reporting

On Sun, Feb 25, 2018 at 12:31 AM, Mark Hammond wrote: > I'm afraid Bob is going to get quite frustrated if he gets upset about > responses taking more than a few days to come in. I'm going to assume you hadn't yet read the thread leading up to Vernon's last message.

Re: [python-win32] Bug reporting

On 22/02/2018 4:04 am, Vernon D. Cole wrote: Ummm ... "I'm buried under a project right now, and I won't be able to get back to you until next Friday." I'm afraid Bob is going to get quite frustrated if he gets upset about responses taking more than a few days to come in. While pywin32 has

Re: [python-win32] Bug reporting

On Wed, Feb 21, 2018 at 10:26 AM, Bob Kline wrote: > Without the patch, SQL Server is unable to store a NULL value or an > empty string properly using placeholders. So we need to find out why > that is, and come up with a version of the patch which fixes the > second

Re: [python-win32] Bug reporting

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

Re: [python-win32] Bug reporting

[ Having a conversation with myself again :-) ] It looks as if the second problem I reported with the Access suite is a result of one of my patches. Apparently with the patch Access (but not SQL Server) treats binary values incorrectly (at least sometimes). Without the patch, SQL Server is unable

Re: [python-win32] Bug reporting

Hi, Vernon. I'm afraid I'm going to start sounding like an annoying nag. :-) If you really want help with this project, you need to meet me half way. If you're swamped with work right now, please at least write back and say something like "I'm buried under a project right now, and I won't be able

Re: [python-win32] Bug reporting

On Mon, Feb 19, 2018 at 11:18 AM, Vernon D. Cole 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

Re: [python-win32] Bug reporting

Sounds like a good plan. On Feb 19, 2018 04:57, "Bob Kline" wrote: > On Mon, Feb 19, 2018 at 2:25 AM, Vernon D. Cole > wrote: > > > I will try to clear this up as much as I can... > > Thanks very much for your reply, Vernon. > > > Adodbapi lives in

Re: [python-win32] Bug reporting

So, could someone clear up a couple of odd little puzzles for me? If the adodbapi project has really moved to GitHub, (1) why does the readme file for the package on GitHub still point back to the SourceForge page, which still tells people to file bug reports there? and (2) why is the apibase.py

Re: [python-win32] Bug reporting

Thanks for the tip, Max. I added a review to the SourceForge page so I could help others avoid wasting time there (I didn't find any other clues on the page about the move), and I submitted the patch I had posted there as a pull request on GitHub. Cheers, Bob On Sat, Feb 17, 2018 at 2:29 PM, Max

[python-win32] Bug reporting

Bob, I'm pretty sure adodbapi is now part of the pywin32 project. And pywin32 moved to github a little bit ago. Maybe Vernon can confirm or deny but I think submitting issues there is the preferred route. --Max III On Sat, Feb 17, 2018 at 9:00 AM,