[issue1159] os.getenv() not updated after external module uses C putenv()

Changes by Raghuram Devarakonda: -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1159> __ ___ Python-bugs-list mailing list Unsubs

[issue1159] os.getenv() not updated after external module uses C putenv()

Raghuram Devarakonda added the comment: On 9/13/07, Robert Ancell <[EMAIL PROTECTED]> wrote: > The Python os.getenv() function accesses an Python dictionary which is > mirroring the process environment. This dictionary is populated when the > interpreter starts and updated

[issue1159] os.getenv() not updated after external module uses C putenv()

Raghuram Devarakonda added the comment: > Stefan Sonnenberg-Carstens added the comment: > > > As per the document and my simple test (on Linux), os.putenv() does > > not update os.environ. I think, it should update it. > What would be the benefit ? Symmetrical beha

[issue1159] os.getenv() not updated after external module uses C putenv()

Raghuram Devarakonda added the comment: > Robert Ancell added the comment: > > draghuram, unfortunately while os.putenv() can be fixed to be > symmetrical any putenv call from a C module cannot, for example: Hi Robert, I understood the problem from your very first report. I broug

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Changes by Raghuram Devarakonda: -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1181> __ ___ Python-bugs-list mailing list Unsubs

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Raghuram Devarakonda added the comment: Shouldn't the first clear() in the patch say "del self.data[key.upper()]" instead of "del self.data[key]"? I also think the patch should include doc change. __ Tracker <[EMAIL PROTECTED]> &l

[issue1210] imaplib does not run under Python 3

Changes by Raghuram Devarakonda: -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1210> __ ___ Python-bugs-list mailing list Unsubs

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: Just to further understand the issue, I added "imaplib.Debug=5" and here is the output preceding the exception stack trace(I replaced the real IMAP server name) *** 20:19.52 imaplib version 2.58 20:19.52 new IMAP4 connection, tag

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: I have gone through the python-3000 discussions about similar problems in other stdlib modules (email, imghdr, sndhdr etc) and found PEP 3137 (Immutable Bytes and Mutable Buffer). Since that work is in progress, I don't think it is worthwhile to fix

[issue1231] PEPs 344 and 3134 contain incorrect hyperlinks.

New submission from Raghuram Devarakonda: http://www.python.org/dev/peps/pep-0344/ http://www.python.org/dev/peps/pep-3134/ Check both the PEPs and grep for the first occurrence of "RFC 88" which is a link. The target of the link is http://www.faqs.org/rfcs/rfc88.html which is

[issue1243] option.dest not set when callback called with optparse

Raghuram Devarakonda added the comment: I have never used callbacks but went through the docs/code and I am not sure if there is a bug here. _check_dest() creates 'dest' only if 'type' is specified for the 'callback' option. With callbacks, it can not guess

[issue1243] option.dest not set when callback called with optparse

Raghuram Devarakonda added the comment: > > But what type should I specify? > > I was using a callback to get a datetime object as an option... > If you are looking for a new type of option than what are already supported (string, int, long, choice, float and complex), you

[issue1713041] fix for 1712742: corrects pprint's handling of 'depth'

Raghuram Devarakonda added the comment: I was just searching for all my issues and found this one. Can some one please apply pprint.patch? Thanks. _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/iss

[issue1287] os.environ.pop doesn't work

Raghuram Devarakonda added the comment: The following patch solves the problem (with the latest from trunk). I only tested on Linux. I couldn't reproduce the problem with latest py3k (again, on Linux). === --- Lib/os.py (rev

[issue1290] xml.dom.minidom not able to handle utf-8 data

Raghuram Devarakonda added the comment: I forgot to show dom.py source. marvin:cpython$ cat dom.py import xml.dom.minidom as dom data = open('testdata.txt','r').read() mydom = dom.parseString(data) mydom.firstChild.childNodes __ Track

[issue1290] xml.dom.minidom not able to handle utf-8 data

Raghuram Devarakonda added the comment: When I run the code in a script, I don't get the error. *** marvin:cpython$ python Python 2.5 (r25:51908, Jan 24 2007, 12:48:15) [GCC 4.1.0 (SUSE Linux)] on linux2 Type "help", "copyright", "credits"

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: I tested cmd.py on Linux and two things (including the one reported by OP) looked odd to me. 1) CTRL-D produces a message "*** Unknown syntax: EOF". 2) CTRL-C produces a KeyboardInterrupt exception and the session terminates. I am attaching a

[issue1290] xml.dom.minidom not able to handle utf-8 data

Raghuram Devarakonda added the comment: The fact that the problem occurs only from the command line and not when run from a script indicates that the real issue is in trying to print the object. Sure enough, if you modify the script to do repr(mydom.firstChild.childNodes), it gets the same

[issue1256] subprocess Popen wait() function hangs when stdout is > 20480

Raghuram Devarakonda added the comment: PIPE on POSIX are implemented using pipe system call so it will have all the limitations of the system buffering that is used for implementing pipes. The buffer size is system dependent. For example, on my Linux, I hit the hang condition at 64K and not

[issue1287] os.environ.pop doesn't work

Raghuram Devarakonda added the comment: After reading the change, I think one more small change may be required. Index: Lib/os.py === --- Lib/os.py (revision 58654) +++ Lib/os.py (working copy) @@ -452,7 +452,7

[issue1322] platform.dist() has unpredictable result under Linux

Raghuram Devarakonda added the comment: I think it is safe to ignore lsb-release. In fact, there seems to be a command "lsb_release" that gives information about distribution. On my SuSE box, this is what I get: marvin:~# lsb_release -i Distributor ID: SUSE LINUX marvin:~# lsb_

[issue1322] platform.dist() has unpredictable result under Linux

Raghuram Devarakonda added the comment: On 10/25/07, Yann Cointepas <[EMAIL PROTECTED]> wrote: > I can easily do the patch to ignore symlinks and /etc/lsb-release but I am > not sure of the appropriate way to look for lsb_update command, is > distutils.spawn.find_executable( &#x

[issue1322] platform.dist() has unpredictable result under Linux

Raghuram Devarakonda added the comment: > Ony my Ubuntu box lsb_release is just a small Python script that parses > /etc/lsb-release. I suggest that your read the LSB standards about the > file and use the information to parse it instead of invoking a program. Can you please ch

[issue1354] windows installer problem

Raghuram Devarakonda added the comment: I installed python 2.5 on multiple windows machines and had no problem. How ever, this doesn't look like it belongs in bug tracker. You will have better chance if you post to comp.lang.python. -- nosy: +drag

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: I think the solution is to do the translation on a bigger chunk than on the string being returned in each read call. For example, the following patch correctly returns "a" and "\n" (instead of "a" and

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: I am attaching the patch io.diff that does the following: - If a chunk ends in "\r", read the next chunk to check if it starts with "\n". This is obviously a very simplified solution that can be optimized. - invoke _replacenl on the

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: On 11/6/07, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote: > - it reads a complete chunk for just one more byte > - the re-read should be disabled when lineends are not translated > these two are minor annoyance and can be e

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: Hi Amaury and Christian, io3.diff does replacenl() in adjust_chunk() (trying Amaury's suggestion). Can you see if it fixes test_mailbox failures? Added file: http://bugs.python.org/file8708/io3.diff __ Tracker &l

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: I am attaching another patch (io2.diff). Please review. I am not sure whether _adjust_chunk() should also adjust "readahead". BTW, PEP 3116 says: "If universal newlines without translation are requested on input (i.e. newline='

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: > The new patch fixes test_netrc for me but test_csv and test_mailbox are > still broken. Unfortunately, I am not able to build python on windows so I can not test there. Can you post the exact errors? You can send me private email as well if you

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: I will see what I can do but it may take a while. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1210> __ ___ Python-bugs-

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: Considering that test_csv is failing on windows even without any changes related to this issue, I looked at it and came up with this patch: - Index: Lib/test/test_csv.py

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: On 11/8/07, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote: > OK, I have taken another approach which seems to work (see io4.diff): > It uses an IncrementalNewlineDecoder, which wraps the initial (e.g. > utf-8) decoder. I like this ap

[issue1395] py3k: duplicated line endings when using read(1)

Raghuram Devarakonda added the comment: On 11/8/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > I do think there is something iffy here -- the 2.x version of this > test opens the files in binary mode. I wonder what end users are > supposed to do. I think that requirement (

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: Index: Lib/imaplib.py === --- Lib/imaplib.py (revision 58956) +++ Lib/imaplib.py (working copy) @@ -228,7 +228,7 @@ self.port = port self.sock = socket.socket

[issue1429] FD leak in SocketServer

Raghuram Devarakonda added the comment: Please provide a small test code that manifests the problem. It is always the best way to get quick response. -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1466] Special reporting of NotImplementedError in unittest

Raghuram Devarakonda added the comment: I don't think unittest automatically treats all exceptions as failures. Failures are those that are explicitly flagged with assert* and fail* methods. All other exceptions result in "errors". I think what you are asking for is to specia

[issue1466] Special reporting of NotImplementedError in unittest

Raghuram Devarakonda added the comment: > Possible, but cumbersome. You have to analyze each case and see if it Have you tried to write a Test Runner that ignores NotImplementedError? You may have to override TestResult.addError. __ Tracker <[EMAIL PRO

[issue1467] error in TestResult.addError and TestResult.addFailure

New submission from Raghuram Devarakonda: The page at http://docs.python.org/dev/library/unittest.html#module-unittest says: - TestResult.addError(test, err) Called when the test case test raises an unexpected exception err is a tuple of the form returned by sys.exc_info

[issue9857] SkipTest in tearDown is reported an as an error

Changes by Raghuram Devarakonda : -- nosy: +draghuram ___ Python tracker <http://bugs.python.org/issue9857> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3002] shutil.copyfile blocks indefinitely on named pipes

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: I am not sure if copyfile() should be trying to copy named pipes (or any other special files for that matter). The best way is perhaps to check and skip such files. -- nosy: +dra

[issue3053] test_shutil fails under AIX

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: Is there any particular reason to assert for failed function at all? This test seems to be for 'onerror' function and the test would be valid even without asserting whether the failed API is 'remove'

[issue3058] Let SimpleXMLRPCServer pass client_address to called functions.

Changes by Raghuram Devarakonda <[EMAIL PROTECTED]>: -- nosy: +draghuram ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3058> ___ _

[issue3115] os.listdir randomly fails on occasions when it shouldn't

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: Isn't this similar to #1608818? -- nosy: +draghuram ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.

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

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: Richard, I see the following very clearly mentioned in the doc: "If you want a given stdin to be used, make sure to set the instance’s use_rawinput attribute to False, otherwise stdin will be ignored." Even though

[issue3134] shutil references undefined WindowsError symbol

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: This is same as #2549 which also reported the same problem. In fact, the problem was originally found in #1545. As I said there, the proposed patch has a very small problem. Can you please take a look? -- nosy: +dra

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

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: On Wed, Jun 18, 2008 at 9:28 PM, Richard King <[EMAIL PROTECTED]> wrote: > > Richard King <[EMAIL PROTECTED]> added the comment: > > There were some other things I wanted too so I just made my own cmd.py.

[issue3134] shutil references undefined WindowsError symbol

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: I submitted a patch at http://codereview.appspot.com/2384. Please take a look. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: I have submitted a patch (http://codereview.appspot.com/2384) for WindowsError issue as it is reported in two other bugs #3134 and #2549. I have only tested on Linux so I would appreciate if some one who have access to windows ca

[issue2549] shutil: NameError (WindowsError) when moving from ext3 to fat32 under linux

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: This is duplicate of 3134. I posted a patch there. -- resolution: -> duplicate status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs

[issue3134] shutil references undefined WindowsError symbol

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: > Patch works under Windows. Thanks. Can you please commit the change? ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: WindowsError issue is now fixed in r65644. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3580] failures in test_os

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: > The other failure is trivial, I've fixed it in r65780. #1709112 has been reported earlier in relation to pagefile.sys. Your patch addresses at least part of the problem there. I wonder if that issue can be closed. -

[issue3580] failures in test_os

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: On Mon, Aug 18, 2008 at 10:28 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > Since the purpose of the test is, allegedly, to "Verify that an open > file can be stat'ed", it may be simpler to c

[issue3728] imaplib module broken by str to unicode conversion

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: This seems to be duplicate of #1210. -- nosy: +draghuram resolution: -> duplicate status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs

[issue3937] platform.dist(): detect Linux distribution version in a robust, standard way

Raghuram Devarakonda <[EMAIL PROTECTED]> added the comment: Please take a look at #1322 for some discussion on this topic. -- nosy: +draghuram ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3187] os.listdir can return byte strings

Changes by Raghuram Devarakonda <[EMAIL PROTECTED]>: -- nosy: +draghuram ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3187> ___ _

[issue8692] Use divide-and-conquer for faster factorials

Changes by Raghuram Devarakonda : -- nosy: +draghuram ___ Python tracker <http://bugs.python.org/issue8692> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: I agree with Facundo that it is not good to hide the error. It should be up to the caller to ignore the error. -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1706039] Added clearerr() to clear EOF state

Raghuram Devarakonda added the comment: I get an error when I try to read 1523853. Is this not moved to the new tracker or others are able to access it? -- nosy: +draghuram _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/iss

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: > try: > > except os.error, err: > if WindowsError is not None or not isinstance(err, WindowsError): > raise # Pretend we didn't catch it > pass # Ignore it All the double negations are hurting when I try to unde

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: > You're right, my code was wrong. Yours will be be correct if you add > "else:" in front of the raise. I also still prefer "WindowsError is Yeah. I was just about to correct my code when I saw your response. I should not post ju

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: My patch adds very sensible default behaviour when Ctrl-C or Ctrl-D are entered. It follows the tradition of many unix programs such as bash and bc which exit on Ctrl-D and ignore Ctrl-c in one way or another. Most importantly, a user can always override

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: > I will look into this for 2.6. No promises. Somebody ought to check > whether this does not cause problems for pdb. Thanks. I will check about pdb tomorrow. __ Tracker <[EMAIL PROTECTED]> <http://

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: The change looks fine as per yesterday's discussion. Can you submit the actual patch? it needs to include check for WindowsError name. BTW, I would put a comment when the exception is being ignored on windows. __ Tr

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: Some comments about shutil.diff: 1) This seems to be against 2.5. You would be better off submitting a patch against trunk. In case of bug fixes, it will usually be back ported. This particular change is not a bug fix though. 2) patches should be either

[issue1545] shutil fails when copying to NTFS in Linux

Raghuram Devarakonda added the comment: There is a mistake in the patch. The line "if WindowsError is not None and isinstance(err, WindowsError):" in copytree() should use the name 'why' and not 'err'. Unfortunately I can't test on windows, but you didn'

[issue1577] shutil.move() does not use os.rename() if dst is a directory

Raghuram Devarakonda added the comment: Since we already have os.rename, wouldn't it be better for shutil.move() to be closer to command line 'mv'? I think Facundo's approach should work. -- nosy: +draghuram __ Tracker <[

[issue1577] shutil.move() does not use os.rename() if dst is a directory

Raghuram Devarakonda added the comment: Then, a small change in the doc might clarify the usage (as OP suggested); "If the destination is on our current filesystem, then simply use rename." can be replaced with: "If the destination is a fiile and is on same filesystem as th

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: "Tomorrow" took a while to come by :-) With out the patch, pdb prints this on Ctrl-C: "KeyboardInterrupt Uncaught exception. Entering post mortem debugging Running 'cont' or 'step' will restart the program" With t

[issue1606] Doc: subprocess wait() may lead to dead lock

Raghuram Devarakonda added the comment: Look at #1256 for similar report. A doc change was suggested there as well. -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1669] shutil.rmtree fails on symlink, after deleting contents

Raghuram Devarakonda added the comment: Please try to include stack trace in bug reports. I reproduced the error on my Linux (SuSE 10). marvin:tmp$ ls -l dirlink testdir lrwxrwxrwx 1 raghu users7 2007-12-20 10:10 dirlink -> testdir/ testdir: total 0 -rw-r--r-- 1 raghu users 0 2007-12

[issue1669] shutil.rmtree fails on symlink, after deleting contents

Raghuram Devarakonda added the comment: I am ok with disallowing symlinks in rmtree() because if it were to be allowed, the semantics are not clear. In addition, neither 'rmdir' nor 'rm -rf' delete the target directory. The attached patch would raise error if symbolic link

[issue1669] shutil.rmtree fails on symlink, after deleting contents

Raghuram Devarakonda added the comment: Index: Lib/shutil.py === --- Lib/shutil.py (revision 59581) +++ Lib/shutil.py (working copy) @@ -156,6 +156,16 @@ elif onerror is None: def onerror(*args

[issue1675] Race condition in os.makedirs

Raghuram Devarakonda added the comment: I don't think os.makedirs() can do anything here. It should be caller's responsibility to check for this kind of issues. -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1728] distutils.cmd breaks inspect

Raghuram Devarakonda added the comment: I can't reproduce it with 2.5.1 on SuSE 10. Can you please report the exact traceback you see? -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1728] distutils.cmd breaks inspect

Raghuram Devarakonda added the comment: When I printed the file name that is being passed to linecache.getlines() by findsource(), the file name is absolute path. So there may be nothing wrong with linecache itself. Can you see what is the name being passed in your case? We still need to trace

[issue1243] option.dest not set when callback called with optparse

Raghuram Devarakonda added the comment: I was under the impression that no change is necessary but I will take a closer look and will see if something needs to be done. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1243] option.dest not set when callback called with optparse

Raghuram Devarakonda added the comment: > Hm, perhaps I misinterpreted the discussion. If no patch is necessary, > please close as won't fix or invalid. I spent some time looking at optparse code and OP's request. _check_dest has a clear comment that says "dest" will b

[issue1243] option.dest not set when callback called with optparse

Raghuram Devarakonda added the comment: FWIW, the change to _check_dest to always set 'dest' breaks quite a few tests. __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1763] Winpath module - easy access to Windows directories like My Documents

Raghuram Devarakonda added the comment: The current 'path' modules such as posixpath and ntpath have functions that operate on a file path. But I see this module more as a way of getting information related to one's profile. So the name 'winpath' may not be a good

[issue1784] Error with OptionParser.parse_args()

New submission from Raghuram Devarakonda: Sorry for the generic title but I couldn't think of a better one. My attempt to do "svn up && make" failed with the following exception from setup.py: -- File "./setup.py", line 314, in d

[issue1784] Error with OptionParser.parse_args()

Raghuram Devarakonda added the comment: It is my mistake. I modified optparse.py for an earlier issue and that change is the cause of the problem reported here. Please close it as invalid. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1781] ConfigParser: add_section('DEFAULT') causes duplicate sections.

Raghuram Devarakonda added the comment: Please see cfgparser.diff for the fix. It has tests and doc change. -- nosy: +draghuram Added file: http://bugs.python.org/file9118/cfgparser.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1781] ConfigParser: add_section('DEFAULT') causes duplicate sections.

Raghuram Devarakonda added the comment: I should add that the patch disallows not only 'DEFAULT' but all other variants such as "Default" and "default". I am not entirely sure if my description of this behaviour as "DEFAULT or an

[issue1725737] Distutils default exclude doesn't match top level .svn

Raghuram Devarakonda added the comment: I suggest this bug be closed as invalid. _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1725737> _ ___ Python-bugs-

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: bugday task? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1294> __ ___ Python-bugs-list mailing list Unsubs

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: Ok. BTW, can I get tracker permissions? I will try to check old bugs to update their information and if required, close them. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: > I've added developer status to your username. Let me know if it doesn't > work. It does. Thanks. __ Tracker <[EMAIL PROTECTED]> <http://

[issue1781] ConfigParser: add_section('DEFAULT') causes duplicate sections.

Changes by Raghuram Devarakonda: -- keywords: +easy, patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1781> __ ___ Python-bugs-list mailing list

[issue1693149] patch to make 'trace.py --ignore-module' accept module name list.

Raghuram Devarakonda added the comment: The patch trace.diff contains the code and doc change. -- keywords: +easy severity: normal -> title: trace.py --ignore-module should accept module name list. -> patch to make 'trace.py --ignore-module' accept module name lis

[issue1693149] trace.py --ignore-module should accept module name list.

Changes by Raghuram Devarakonda: Removed file: http://bugs.python.org/file7923/trace_patch.diff _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1693149> _ __

[issue1183712] package_data chops off first char of default package

Raghuram Devarakonda added the comment: Closing this as the required code change is committed (as part of #1720897). -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1669] shutil.rmtree fails on symlink, after deleting contents

Raghuram Devarakonda added the comment: If rmtree() always returns in case of symbolic links (as it is checked-in), wouldn't it be much simpler to totally do away with 'onerror' handling? I thought 'onerror' gives the user the option how to proceed (whic

[issue1577] shutil.move() does not use os.rename() if dst is a directory

Changes by Raghuram Devarakonda: -- components: +Documentation -Library (Lib) __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1577> __ ___ Python-bugs-

[issue1669] shutil.rmtree fails on symlink, after deleting contents

Raghuram Devarakonda added the comment: > and it should use the onerror() handling used for all other errors" > which makes sense for me too. Sure. I am ok with using 'onerror'. The point I am trying to make is that there is slight difference between 'onerror'

[issue1706039] Added clearerr() to clear EOF state

Changes by Raghuram Devarakonda: -- nosy: -draghuram _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1706039> _ ___ Python-bugs-list mailing list

[issue479195] Put Demo/rpc/rpc.py into standard lib

Raghuram Devarakonda added the comment: I started looking at the bugs in chronological order in the hope that I can close some issues that don't make sense any more. Can I close this one? I am almost sure that this module is not going to be included in stdlib (I myself haven't used t

[issue479195] Put Demo/rpc/rpc.py into standard lib

Raghuram Devarakonda added the comment: Closing as there is no activity for long time and the request is unlikely to be accepted, anyway. -- resolution: -> rejected status: open -> closed Tracker <[EMAIL PROTECTED]> <http://

[issue491331] request sys.required_version

Raghuram Devarakonda added the comment: should have been closed long time back :-). -- nosy: +draghuram resolution: -> rejected status: open -> closed Tracker <[EMAIL PROTECTED]> <http://bugs.python.

  1   2   >