On Aug 3, 2005, at 3:38 PM, Jon A. Lambert indited:
Stein Somers wrote:
In short, cygwin 1.5.17-1 good, 1.5.18-1 bad. As Gerrit wrote from
the
start.
Just as a point of strange coincidence, cygwin 1.5.17-1 good,
1.5.18-1 bad seems to be the case with the recent Python and
Postgres
On Jul 28, 2005, at 8:48 AM, Jason Tishler wrote:
Doug,
I don't know. When I saw the Python message it seemed plausible.
The real issue is that Python broke with 1.5.18, either because of
the pthread change or not.
Be that as it may, should I report this bug in another forum?
No, this is
On Jul 28, 2005, at 9:49 AM, Igor Pechtchanski wrote:
That's why I culled down my large application to a small Python
script
which exhibited the bug and which I submitted to the list, along
with my
cygcheck -srv and the error messages that Python gave me.
So your test case is currently a
On Jul 28, 2005, at 6:02 PM, Williams, Gerald S (Jerry) wrote:
On the other hand, I verified at the time that the semaphore
solution worked under Cygwin Python, so I wouldn't expect it
to be a problem even if the change just took place. However,
it could potentially help in isolating the
On Jul 27, 2005, at 7:29 PM, Christopher Faylor wrote:
So far, I found from stracing the following:
7743 884473 [main] python2.4 3916 __set_errno: int
semaphore::_trywait():1761 val 11
Unfortunately, I won't have the time to debug further for a
while. And,
to be honest, I'm lacking
Attached find a cut-n-paste'd error from python being temporarily
unable to allocate a lock:
$ python tbp.py
each test group is testing 1 items
sem_init: Resource temporarily unavailable
Exception in thread Thread-3:
Traceback (most recent call last):
File
While trying to solve my Python 2.4.1-1 problem under cygwin 1.5.18
it was suggested that rebaseall might solve my problem. Unfortunately
it didn't. However, rebase all didn't work either. Here is result:
$ /bin/rebaseall
ReBaseImage (/usr/bin/cygiconv-2.dll) failed with last error = 6
7 matches
Mail list logo
