Weeble added the comment:
I had a closer look at the cif object in gdb. The ffi_type of the argument in
question has size 16, alignment 1, type FFI_TYPE_STRUCT and elements contains a
single nested ffi_type, of size 8, alignment 8, type FFI_TYPE_POINTER.
I think this pointer type is wrong
New submission from Weeble:
I'm not 100% certain this is a bug yet, but I'm beginning to think it's likely.
On 64-bit Linux, I can't pass a struct like this:
struct S { uint8_t data[16]; };
...to a function declared like this:
void f(struct S);
From experimentation with various
Weeble added the comment:
Ah, sorry for the confusion.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21194
___
___
Python-bugs-list mailing
New submission from Weeble:
The JSON spec (http://www.json.org/) does not allow unescaped control
characters. (See the railroad diagram for strings and the grammar on the
right.) If json.dumps is called with ensure_ascii=False, it fails to escape
control codes in the range U+007F to U+009F
Weeble clockworksa...@gmail.com added the comment:
I'm not sure what rules are used by Windows to process the PATH string, but I
think they are similar to the rules used to parse the command-line into argv in
a C/C++ program: http://msdn.microsoft.com/en-us/library/17w5ykft.aspx
I have tested
New submission from Weeble clockworksa...@gmail.com:
The docs for optparse say this:
OptionParser.get_option_group(opt_str)
Return, if defined, the OptionGroup that has the title or the long
description equals to opt_str
After failing to get this to work at all, I looked
Weeble clockworksa...@gmail.com added the comment:
I think the documentation for get_option_group is not right. I've created a new
bug: http://bugs.python.org/issue11699
--
nosy: +weeble
___
Python tracker rep...@bugs.python.org
http
Weeble clockworksa...@gmail.com added the comment:
Is there any way to write code that's safe with or without this fix? If I have
code that currently does this:
subprocess.check_call('c:\some path with spaces arg1 arg2 a quoted arg',
shell=True)
...will it break when running on a version
New submission from Weeble clockworksa...@gmail.com:
Steps to reproduce:
1. Start IDLE.
2. Enter some text:
spam
eggs
3. Select the first line (spam) and press control+c to copy.
4. Select the second line (eggs) and press control+v to paste.
Expected result:
spam
spam
(With the caret
Weeble clockworksa...@gmail.com added the comment:
You're right: we should find a solution that's safe and supported.
I *think* the primary reason for overriding the home key behaviour was
not for the interactive shell, but to make it easier to edit code. Most
programmer's editors that do
Weeble clockworksa...@gmail.com added the comment:
I can't see any useful reason to go to the absolute start of the line in
the interactive shell. However, it does make sense in the source editor,
and it is consistent with, for example, Visual Studio. The first use-
case off the top of my head
Weeble clockworksa...@gmail.com added the comment:
Just got a chance to test this on a Windows desktop with a proper
keyboard. (My laptop does weird things with num-lock and scroll-lock.) I
got it to crash once, but I have no idea what was special about that
time. Otherwise I can reproduce
Weeble clockworksa...@gmail.com added the comment:
A thought occurs to me: would this patch make it harder to cope with
awkward firewalls that block the connection? Are they more or less
likely to intervene when passing a port of 0 and letting it pick a port
automatically? And if they do
Changes by Weeble clockworksa...@gmail.com:
--
nosy: +weeble
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3068
___
___
Python-bugs-list mailing
Weeble clockworksa...@gmail.com added the comment:
I installed Ubuntu on a laptop at the beginning of January and have
applied the patch I submitted above to IDLE. I've been using it
regularly for the last few weeks and have had no problems
Weeble clockworksa...@gmail.com added the comment:
I have experienced similar problems in Python 2.6.1 on Windows, and
found them to be due to Tk 8.5. I posted my findings here:
http://mail.python.org/pipermail/idle-dev/2009-January/002738.html
In summary, Tk 8.5 changed the name of the anchor
Weeble clockworksa...@gmail.com added the comment:
Another complication. On Windows, this line doesn't do what it claims:
if (event.state 12) != 0 and event.keysym == Home:
# state1==shift, state4==control, state8==alt
return # Modifier-Home; fall back to class binding
The comment
Changes by Weeble [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file12180/IDLE_automatic_ports.diff
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1529142
Weeble [EMAIL PROTECTED] added the comment:
Okay, I've uploaded a patch. As suggested, it passes 0 for the port
number and the port is automatically assigned. It then extracts the port
from the socket and passes it to the subprocess. Note that this means
the subprocess inherits the listening
Weeble [EMAIL PROTECTED] added the comment:
Is this ever likely to make it into IDLE? Running without a subprocess
in Windows appears to interact badly with the multiprocessing library
(attempting to spawn a process just creates a new IDLE window). I
couldn't figure out how to apply the patch
Changes by Weeble [EMAIL PROTECTED]:
--
nosy: +weeble
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1529142
___
___
Python-bugs-list mailing list
21 matches
Mail list logo
