[issue1180] Option to ignore ~/.pydistutils.cfg

Changes by Michael Hoffman: -- components: Distutils severity: normal status: open title: Option to ignore ~/.pydistutils.cfg type: rfe versions: Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

Changes by Michael Hoffman: -- title: Option to ignore ~/.pydistutils.cfg -> Option to ignore or substitute ~/.pydistutils.cfg __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1643369] function breakpoints in pdb

Michael Hoffman added the comment: Agree with isandler. This is not a bug. -- nosy: +hoffman _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/iss

[issue1180] Option to ignore ~/.pydistutils.cfg

New submission from Michael Hoffman: It would be useful if setup.py instances had an option to ignore ~/.pydistutils.cfg or substitute it with another file. For example, this would be highly useful to people who maintain a system site-packages directory along with one in their own home directory

[issue1186] optparse documentation: -- being collapsed to - in HTML

New submission from Michael Hoffman: See <http://docs.python.org/lib/optparse-callback-example-6.html> where it says 'either "-" or "-" can be option arguments'. One of these should be --. The same error occurs several times on the same page. Not

[issue1186] optparse documentation: -- being collapsed to - in HTML

Michael Hoffman added the comment: At the very least could you change the "--" to be the verbatim class that shows up properly beneath? There has to be another solution that would result in the docs at least being correct even if we can't get LaTeX to do exact

[issue1186] optparse documentation: -- being collapsed to - in HTML

Michael Hoffman added the comment: Also, see http://bugs.python.org/issue798006 which shows how to fix a similar problem elsewhere in the docs. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue10396] stdin argument to pdb.Pdb doesn't work unless you also set Pdb.use_rawinput = False

New submission from Michael Hoffman : If you create a Pdb instance with an stdin argument, the default behavior is for commands to be retrieved using raw_input(), which uses sys.stdin instead, thereby causing the stdin argument to be without effect. You can work around this by setting the

[issue10396] stdin argument to pdb.Pdb doesn't work unless you also set Pdb.use_rawinput = False

Changes by Michael Hoffman : Added file: http://bugs.python.org/file19581/expected_behavior.py ___ Python tracker <http://bugs.python.org/issue10396> ___ ___ Python-bug

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

Changes by Michael Hoffman : -- nosy: +hoffman ___ Python tracker <http://bugs.python.org/issue2571> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10396] stdin argument to pdb.Pdb doesn't work unless you also set Pdb.use_rawinput = False

Michael Hoffman added the comment: As always, it seems a bit more complicated than I originally expected. Since it's too late for a Python 2.x feature addition, I'll wait until I upgrade to 3.x to work on that. You are correct, technically this is not a docs bug but I think the

[issue2155] optparse.OptionGroup with_statement context handling

New submission from Michael Hoffman: Adding these four lines to optparse.OptionGroup makes using option groups vastly easier: def __enter__(self): return self def __exit__(self, *exc_info): self.parser.add_option_group(self) You can then do things like: with

[issue2130] [feature-request] Please add bool data type to "optparse" module

Michael Hoffman added the comment: As gpolo points out, this facility already exists. This RFE should be closed. -- nosy: +hoffman __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

Michael Hoffman <[EMAIL PROTECTED]> added the comment: That is up to you of course, and being able to ignore is better than nothing. But creating a new account is not really an option for everyone. On the system I would like to use this feature the most, I am not a system administrator

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

Michael Hoffman <[EMAIL PROTECTED]> added the comment: Here's an example of a configuration file I use: [build_ext] include_dirs = /nfs/acari/mh5/include/python2.5:/nfs/acari/mh5/include [install] prefix = ~ exec_prefix = ~/arch/$ARCH install_platlib = $platbase

[issue4245] threading documentation: reorder sections

New submission from Michael Hoffman <[EMAIL PROTECTED]>: It is somewhat confusing that the meat of the threading module, the Thread object itself, is so far down in the documentation. It should be the first section after the module functions and objects. http://docs.python.org/l

[issue2155] optparse.OptionGroup with_statement context handling

Michael Hoffman added the comment: Is there anything I can do to get this feature request considered earlier? I can generate a real patch, but I figured that wouldn't necessary for something so simple. This has the advantage that it can probably be cut/pasted into any version of the

[issue1154351] add get_current_dir_name() to os module

Michael Hoffman added the comment: glibc `getcwd()` and `get_current_dir_name()` are not the same. glibc `get_current_dir_name()` does, in fact, check the `PWD` environment variable. https://www.gnu.org/software/libc/manual/html_node/Working-Directory.html The get_current_dir_name function

[issue1154351] add get_current_dir_name() to os module

Michael Hoffman added the comment: > * For some libc functions we add options to existing functions rather of > duplicating the number of names in the os module. For example the dir_fd > option instead of *at() functions. Wouldn't be better to add a buulean > paramet

[issue1154351] add get_current_dir_name() to os module

Michael Hoffman added the comment: `getcwd()` in many ways serves the purpose that a `lget_current_dir_name()` might. -- ___ Python tracker <https://bugs.python.org/issue1154