[issue32198] \b reports false-positives in Indic strings involving combining marks

2017-12-02 Thread Shriramana Sharma
New submission from Shriramana Sharma <samj...@gmail.com>: Code: import re cons_taml = "[கஙசஞடணதநபமயரலவழளறன]" print(re.findall("\\b" + cons_taml + "ை|ஐ", "ஐவர் பையன் இசை சிவிகை இல்லை இவ்ஐ")) cons_deva = "[कखगघङचछजझञटठडढणतथदधनपफबभमयरलवशषसह]

[issue10984] argparse add_mutually_exclusive_group should accept existing arguments to register conflicts

2014-02-28 Thread Shriramana Sharma
Changes by Shriramana Sharma samj...@gmail.com: -- nosy: +jamadagni ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10984 ___ ___ Python-bugs-list

[issue10984] argparse add_mutually_exclusive_group should accept existing arguments to register conflicts

2014-02-28 Thread Shriramana Sharma
Shriramana Sharma added the comment: I also wish to see argparse allowing me to define a group of arguments that conflict with another argument or another group of arguments and FWIW I feel the help output should be like: prog [ --conflicter | [ --opt1 ] [ --opt2 ] ] where --conflicter

[issue20433] add aliasedname() and namedaliases() methods to unicodedata module

2014-01-28 Thread Shriramana Sharma
New submission from Shriramana Sharma: Currently we have unicodedata.name() which returns the formal character name of the character chr as per the second column in UnicodeData.txt from http://www.unicode.org/Public/UNIDATA/. However, there are a few characters where the formal character name

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-06-02 Thread Shriramana Sharma
Shriramana Sharma added the comment: I came upon this too. In Python 2 it used to expect a one character string. Apparently the same error message has been carried forward to Python 3 too, though now the actual expected input is either a one character bytes type and not a str type, or an int

[issue6386] importing yields unexpected results when initial script is a symbolic link

2013-05-27 Thread Shriramana Sharma
Shriramana Sharma added the comment: I'm sorry but I don't get why this is a WONTFIX. I reported what is (now) apparently a dup: issue 18067. Just like the OP of this bug, I feel that in doing testing and such, one would naturally symlink and expect the library in the *current* directory

[issue6386] importing yields unexpected results when initial script is a symbolic link

2013-05-27 Thread Shriramana Sharma
Shriramana Sharma added the comment: The current behaviour is also needed to sanely support Python scripts symlinked from Linux /bin directories. OK that clinched it for me -- I can't argue against that! And obviously it is not meaningful to copy/symlink *all* the current-directory modules

[issue18067] In considering the current directory for importing modules, Python does not honour the output of os.getcwd()

2013-05-26 Thread Shriramana Sharma
New submission from Shriramana Sharma: Hello. I first asked about this at https://groups.google.com/d/topic/comp.lang.python/ZOGwXGU_TV0/discussion and am only posting this issue due to no reply there. I am using Python 2.7.4 and Python 3.3.1 (default packages) on Kubuntu Raring. On both I

[issue6294] Improve shutdown exception ignored message

2013-05-19 Thread Shriramana Sharma
Changes by Shriramana Sharma samj...@gmail.com: -- nosy: +jamadagni ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6294 ___ ___ Python-bugs-list