[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-19 Thread Tom Browder
Tom Browder added the comment: I'm getting no interest from the gcc group at the moment. I would like to help track down the bug and will nose around the Python source to zero in on where the problem is for detailed debugging. Can anyone point me to the key files that concern the

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-17 Thread Tom Browder
Tom Browder added the comment: Here is a link to the thread I started on the gcc-help mailing list concerning the issue: http://gcc.gnu.org/ml/gcc-help/2010-09/msg00170.html If I don't get a successful build with the current gcc trunk, I imagine this thread will transfer to the gcc

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-17 Thread Tom Browder
Tom Browder added the comment: Correction on the bad gcc compiler: the actual version was a non-released version off the gcc-4.6 branch: gcc version 4.6.0 20100908 (experimental) (GCC). I'm filing a bug with gcc. Sorry for the wasted

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-17 Thread Tom Browder
Tom Browder added the comment: The build succeeded with the older version of gcc. I either have a mis-compiled gcc-4.5.1 (but the same version on another host worked okay) or gcc has a very subtle bug. I think this issue can be considered closed; however, it may be worth a note in a FAQ or

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-17 Thread Tom Browder
Tom Browder added the comment: I'm using gcc-4.5.1. I'll try an older version: gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3. -- ___ Python tracker <http://bugs.python.

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-16 Thread Tom Browder
Tom Browder added the comment: File attached as requested. -- Added file: http://bugs.python.org/file18905/os.pyc ___ Python tracker <http://bugs.python.org/issue9

[issue9879] Tracker Won't Accept New Bugs

2010-09-16 Thread Tom Browder
Tom Browder added the comment: It looks like the problem was because I was trying to add a complete e-mail address to the "nosy" list. -- ___ Python tracker <http://bugs.python.

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-16 Thread Tom Browder
Changes by Tom Browder : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue9880> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

2010-09-16 Thread Tom Browder
New submission from Tom Browder : I am trying to rebuild the 2.7 maintenance branch and get this error on Ubuntu 10.04.1 LTS: XXX lineno: 743, opcode: 0 Traceback (most recent call last): File "/usr/local/src/python-2.7-maint-svn/Lib/site.py", line 62, in import os File "

[issue9879] Tracker Won't Accept New Bugs

2010-09-16 Thread Tom Browder
Tom Browder added the comment: Since this worked, I tried again to enter the bug with a new process. I have tried changing several selections but I still get the error--very strange! -- ___ Python tracker <http://bugs.python.org/issue9

[issue9879] Tracker Won't Accept New Bugs

2010-09-16 Thread Tom Browder
New submission from Tom Browder : When I attempt to enter a new bug I get: An error has occurred A problem was encountered processing your request. The tracker maintainers have been notified of the problem. -- components: Demos and Tools messages: 116620 nosy: Tom.Browder priority

[issue9652] Tidy argparse default output

2010-08-27 Thread Tom Browder
Tom Browder added the comment: ... > Should this be closed in favor of #9694? (Or vice versa?). Perhaps one of the > issues should be renamed something like "Improve argparse message > customization". That sounds like a winner to me -Tom -- title: Enhance a

[issue9653] New default argparse output to be added

2010-08-24 Thread Tom Browder
Tom Browder added the comment: ... > I see. When there are no arguments you basically want to replace the standard > argparse help entirely with your own > message, with your own capitalization, > etc. > What you're doing now looks like a pretty good approach for this, so

[issue9653] New default argparse output to be added

2010-08-23 Thread Tom Browder
Tom Browder added the comment: On Sun, Aug 22, 2010 at 17:06, Steven Bethard wrote: ... > import argparse > import sys > > parser = argparse.ArgumentParser() > parser.add_argument('--foo') > > if len(sys.argv) == 1: >    parser.print_help() > else: >

[issue9653] New default argparse output to be added

2010-08-22 Thread Tom Browder
Tom Browder added the comment: On Sun, Aug 22, 2010 at 16:01, Steven Bethard wrote: > > Steven Bethard added the comment: > > A simpler approach might be to do this before your call to parse_args: > > if len(sys.argv[0]) == 1: >    parser.print_help() > > Does t

[issue9653] New default argparse output to be added

2010-08-20 Thread Tom Browder
New submission from Tom Browder : When I use the argparse module, and I enter my program name with NO arguments or options, I would like the argparser to output something like: Usage: [options] Use option '-h' for help. I haven't yet found how to do that in the argparse mod

[issue9652] Tidy argparse default output

2010-08-20 Thread Tom Browder
New submission from Tom Browder : I would like to be able to change argparse default strings so the first word is capitalized. In lieu of that, I propose the attached patch to 2.7 which changes them in the source code. -- components: Library (Lib) files: python-v2.7-argparser