You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
python3.0 interpreter on Cygwin ignores all arguments #47876
Since the bsddb module has been removed from py3k, the previous patch
addresses the last issue for this ticket.
yselkowitz commented on Sep 21, 2008
yselkowitzmannequin
MannequinAuthor
More actions
3.0rc1 together with the printf patch builds and installs. Some quick
testing seems ok, but idle isn't working:
$ idle3.0
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.0/idlelib/run.py", line 76, in main
sockthread.set_daemon(True)
AttributeError: 'Thread' object has no attribute 'set_daemon'
IDLE appears briefly with a message:
Subprocess Startup Error
IDLE's subprocess didn't make connection. Either IDLE can't start a
subprocess or personal firewall software is blocking the connection.
[OK]
Pushing OK causes idle3.0 to quit. idle 2.5 works fine.
I think cygwin_badprintf.patch needs to consider the case r==PATH_MAX;
this happens when the conversion would need more than PATH_MAX bytes for
the target buffer. In that case, I think it would be good enough to
write "<file name too long>" into cfilename (using cfilename as is will
crash because it's not null-terminated; forcefully null-terminating it
might break the shift state)
Updated patch, which checks the return value of wcstombs.
loewis commented on Oct 17, 2008
loewismannequin
Mannequin
More actions
IIUC, another error return value (besides -1) is PATH_MAX, meaning that
the buffer would overrun; correct me if I'm wrong. If I'm not, I propose
that they get handles similarly.
In addition, it might be safer to compare to (size_t)-1 (I keep
forgetting whether this is the default when comparing signed and
unsigned - some compilers warn about comparisong with mixed signs).
Activity
amauryfa commentedon Sep 20, 2008
This patches corrects the bad printf, when the given filename is only
1-char long.
amauryfa commentedon Sep 20, 2008
Since the bsddb module has been removed from py3k, the previous patch
addresses the last issue for this ticket.
yselkowitz commentedon Sep 21, 2008
3.0rc1 together with the printf patch builds and installs. Some quick
testing seems ok, but idle isn't working:
IDLE appears briefly with a message:
Subprocess Startup Error
IDLE's subprocess didn't make connection. Either IDLE can't start a
subprocess or personal firewall software is blocking the connection.
[OK]
Pushing OK causes idle3.0 to quit. idle 2.5 works fine.
amauryfa commentedon Sep 21, 2008
The IDLE problem is already corrected: see bpo-3628.
yselkowitz commentedon Sep 21, 2008
In that case, then I think this can be closed; if I encounter any
further issues after rc2, I'll open a new bug.
Thank you for all your help.
amauryfa commentedon Sep 21, 2008
Well, after the proposed patch "cygwin_badprintf.patch" is reviewed and
applied...
loewis commentedon Oct 17, 2008
I think cygwin_badprintf.patch needs to consider the case r==PATH_MAX;
this happens when the conversion would need more than PATH_MAX bytes for
the target buffer. In that case, I think it would be good enough to
write "<file name too long>" into cfilename (using cfilename as is will
crash because it's not null-terminated; forcefully null-terminating it
might break the shift state)
amauryfa commentedon Oct 17, 2008
Updated patch, which checks the return value of wcstombs.
loewis commentedon Oct 17, 2008
IIUC, another error return value (besides -1) is PATH_MAX, meaning that
the buffer would overrun; correct me if I'm wrong. If I'm not, I propose
that they get handles similarly.
In addition, it might be safer to compare to (size_t)-1 (I keep
forgetting whether this is the default when comparing signed and
unsigned - some compilers warn about comparisong with mixed signs).
pitrou commentedon Oct 18, 2008
The patch looks sound to me. Someone should probably test it under
Cygwin.
yselkowitz commentedon Oct 20, 2008
3.0rc1 builds and installs fine with the latest patch. Thanks!
tiran commentedon Oct 28, 2008
I can't reproduce the problem with my installation of Cygwin on Windows
XP. However the patch doesn't cause problems so you might apply it.
amauryfa commentedon Oct 30, 2008
Committed the "%ls" fix with r67064.