[issue7120] logging depends on multiprocessing

Amaury Forgeot d'Arc added the comment: Whatever the value of logMultiprocessing is, I suggest to not import the multiprocessing module if the application did not import it before: something like: if "multiprocessing" in sys.modules: from multiprocessing import current_process

[issue7111] core dump when stderr is moved

Amaury Forgeot d'Arc added the comment: > 3.1 exits silently. Did you use "print"? pythonw.exe 3.1 sets sys.stdout to None. if you use sys.stdout.write, you get an exception. But print() silently does nothing if the file is None. -- nosy: +amaury.forgeotdarc ___

[issue5985] Implement os.path.samefile and os.path.sameopenfile on Windows

Hirokazu Yamamoto added the comment: Here is my experimental patch. -- keywords: +patch nosy: +ocean-city Added file: http://bugs.python.org/file15122/samefile.patch ___ Python tracker _

[issue7111] core dump when stderr is moved

Peter Eisentraut added the comment: For what it's worth, the code in question is used here (using "import distutils" instead of "pass"): http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/python.m4?rev=1.15;content-type=text%2Fx-cvsweb-markup This is obviously a completely gratuitous varian

[issue7120] logging depends on multiprocessing

Vinay Sajip added the comment: > Whatever the value of logMultiprocessing is, I suggest to not import the > multiprocessing module if the application did not import it before: > something like: > > if "multiprocessing" in sys.modules: > from multiprocessing import current_process >

[issue5985] Implement os.path.samefile and os.path.sameopenfile on Windows

Erik Sandberg added the comment: An alternative solution which I would have considered, is to extend stat/fstat on Windows to set st_dev and st_ino to sensible values (based on dwVolumeSerialNumber and nFileIndexLow/High), and then use the POSIX implementations of samefile/sameopenfile. There m

[issue7069] inspect.isabstract to return boolean values only

chuck added the comment: That's fine with me. Looks like nobody wants to check it in anyways. -- ___ Python tracker ___ ___ Python-bug

[issue7122] multiprocessing.Pool() problem in windows

New submission from Alex : Maybe I didn't understand how multiprocessing works but when running the test code below I get 200+ processes in Windows and it never finishes. It works fine on Linux. -- components: Library (Lib) files: prueba.py messages: 93975 nosy: SirLalala severity: norma

[issue7120] logging depends on multiprocessing

Antoine Pitrou added the comment: `self.processName` could be a lazily computed property, since it doesn't seem to be used anywhere by default. Something like: _processName = None @property def processName(self): n = self._processName if n is not None: r

[issue7122] multiprocessing.Pool() problem in windows

Amaury Forgeot d'Arc added the comment: This difference between Unix and Windows is documented there: http://docs.python.org/library/multiprocessing.html#windows Please carefully read the paragraph named "Safe importing of main module". You will certainly need to add a condition like if __na

[issue7123] Multiprocess Process does not always exit when run from a thread.

New submission from Peter Saunders : I have an example code that works fine on Python 2.6.3, but when run in Python 3.1.1 - after a very short period of time, will go wrong. Summary: We have a queue, and when the queue has something in it (a list), we start a thread to deal with that entry. Th

[issue5985] Implement os.path.samefile and os.path.sameopenfile on Windows

Hirokazu Yamamoto added the comment: > extend stat/fstat on Windows to set st_dev and st_ino to sensible > values (based on dwVolumeSerialNumber and nFileIndexLow/High) Once I considered this approach, but problems was that nFileIndexLow/High can change every time file handle is opened, so it's

[issue7124] idle.py -n : help() doesn't work in a reopened shell window

New submission from Gregor Lingl : The following procedure reveals a problem with help: 1) Start IDLE with -n option (no subprocess) 2) Create a script (e. g. helloworld one-liner 3) Run script 4) Close Shell Window 5) Via Menu: Run | Python Shell reopen Shell window 6) >>> help(print) Help on .

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: Further information: it doesn't fail everytime in Python 3.1 - usually 1 in 4, or 1 in 5 times. It never fails with Python 2.6.3 Example output from the script when its failing (python 3.1): Starting data1 Starting data2 Started subproc: PID: 20209 : args: dat

[issue7058] Add some test execution environment protection to regrtest

Changes by R. David Murray : Removed file: http://bugs.python.org/file15107/refactored_environment_checking.patch ___ Python tracker ___ ___ P

[issue7058] Add some test execution environment protection to regrtest

R. David Murray added the comment: Here is an updated patch that doesn't break -j. -- Added file: http://bugs.python.org/file15125/refactored_environment_checking.patch ___ Python tracker _

[issue7058] Add some test execution environment protection to regrtest

Antoine Pitrou added the comment: Looks good to me. Not sure it should be backported though, the patch has become really sizeable. -- ___ Python tracker ___ _

[issue7058] Add some test execution environment protection to regrtest

R. David Murray added the comment: I agree about not backporting the new patch. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue1104249] configure doesn't set up CFLAGS properly

M Joonas Pihlaja added the comment: Here's a test case: $ CFLAGS="--haflkhlaiuhfnafkghnaf" ./configure; make [... configure does its thing... ] [... make does its thing and completes successfully ...] Expected result: The build fails due to an unknown flag in CFLAGS. Witnessed result: CFLAG

[issue7123] Multiprocess Process does not always exit when run from a thread.

Changes by Antoine Pitrou : -- assignee: -> jnoller components: +Library (Lib) nosy: +jnoller priority: -> normal type: -> behavior versions: +Python 3.2 ___ Python tracker ___

[issue5985] Implement os.path.samefile and os.path.sameopenfile on Windows

Erik Carstensen added the comment: > Once I considered this approach, but problems was that > nFileIndexLow/High can change every time file handle is opened, so > it's not unique. Ah, I see, then your approach makes sense. There's another part of your patch that I don't understand: +except Im

[issue7123] Multiprocess Process does not always exit when run from a thread.

Antoine Pitrou added the comment: Acccording to http://blogs.sun.com/chrisg/entry/lwp_park_and_lwp_unpark, the lwp_park() call could point to a mutex which is waiting to be acquired. -- nosy: +pitrou ___ Python tracker

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: Well, if it helps, here is the output of the dtrace script from starting of a loop with the failure, and stopping during the failure. -- Added file: http://bugs.python.org/file15126/dtrace.txt ___ Python tracker

[issue7125] typo (English) in threading.py

New submission from Yinon Ehrlich : threading.py line 122: "cannot release un-aquired lock" --> "cannot release un-acquired lock" -- components: Library (Lib) messages: 93989 nosy: Yinon severity: normal status: open title: typo (English) in threading.py versions: Python 2.4, Python 2.5,

[issue7123] Multiprocess Process does not always exit when run from a thread.

Antoine Pitrou added the comment: Does it not happen if you call your checkAlive() function directly from your main() function? -- ___ Python tracker ___

[issue5596] memory leaks in py3k

Antoine Pitrou added the comment: With r75397: test___all__ leaked [1, 1] references, sum=2 test_asyncore leaked [1, 0] references, sum=1 test_distutils leaked [0, 2] references, sum=2 test_httpservers leaked [-259, 0] references, sum=-259 test_os leaked [-23, 23] references, sum=0 test_pydoc l

[issue7125] typo (English) in threading.py

Yinon Ehrlich added the comment: just saw now that the word 'un-aquired' is repeated several times in the threading module... -- ___ Python tracker ___ __

[issue5985] Implement os.path.samefile and os.path.sameopenfile on Windows

Hirokazu Yamamoto added the comment: I'm not sure about this neither. So, XXX is in comment. ;-) On abspath() above, it also tries to import native method _getfullpathname(), and when it fails alternative implementation runs. (probably when someone calls ntpath.abspath from linux or somewhere..

[issue7126] Contradictory documentation for os.putenv and os.system

New submission from Daniel Stutzbach : The documentation for os.putenv states that "changes to the environment affect subprocesses started with os.system(), popen() or fork() and execv()" and "assignments to items in os.environ are automatically translated into corresponding calls to putenv()".

[issue7123] Multiprocess Process does not always exit when run from a thread.

Antoine Pitrou added the comment: As for the dtrace output: I'm not a Solaris expert unfortunately, I was just trying to suggest a possible direction for diagnosing this problem. -- ___ Python tracker _

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: If you mean, in main() instead of doing: while True: q.put(["data1", "data2"]) t = Process(target=popJobs, args=(q, )) t.start() t.join() and doing: while True: q.put(["data1", "data2"]) popJobs(q) instead. Then, the bug does indeed o

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: Same thing occurs, as you would expect, when I do: while True: fail=failureObject() tlist = [] for x in ["data1", "data2"]: t = threading.Thread(target=checkAlive, args = (fail, x), name=x) t.start() tlist.append(t) for

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: Further oddness: When running the script (i've reduced its size further now, see attached): I get the following output: Reaping PID: 23215 True Started subproc: PID: 23216 : args: data1 Started subproc: PID: 23216 : args: data1 Started subproc: PID: 23217 : a

[issue7125] typo (English) in threading.py

Georg Brandl added the comment: Fixed in r75402. Not backporting, since an exception message is changed. Thanks! -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker _

[issue7123] Multiprocess Process does not always exit when run from a thread.

Antoine Pitrou added the comment: > Notice the Started subprod of the SAME PID and the Same args twice, yet > this print only occurs once in the code, and I can't see how this should > happen? This is a thread-safety issue in sys.stdout/stderr, it will be fixed in 3.1.2 (see issue6750). --

[issue7126] Contradictory documentation for os.putenv and os.system

Georg Brandl added the comment: Thanks, fixed in r75403. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7123] Multiprocess Process does not always exit when run from a thread.

Peter Saunders added the comment: Sorry for the spam on the updates :) - but, its the same thread printing this out too. I changed the print line to: curThread = threading.current_thread() print("Started subproc: PID: %d : args: %s Thread ID: %s" %(newJob.pid, str(args), str(curThread.ident)))

[issue7127] regrtest -j fails when tests write to stderr

New submission from R. David Murray : If a test writes to stderr, then the -j (multiprocessing) support in regrtest fails to correctly extract the JSON data from the test output, resulting in a JSON traceback followed by a failure of the worker thread. Antoine has suggested tagging the JSON resu

[issue7128] cPickle looking for non-existent package copyreg

New submission from Joseph C Wang : When running cPickle in restricted mode, the module tries to import copyreg which does not appear to exist anywhere. The problem is in cPickle.c 2980 if (PyEval_GetRestricted()) { 2981 /* Restricted execution, get private tables */ 2982

[issue7091] Distutils build ignores the --compiler command line option

Tarek Ziadé added the comment: Duplicate of #7068 -- resolution: -> duplicate status: open -> closed superseder: -> 2.6.3 does not use specified compiler ___ Python tracker ___

[issue7112] unicodetype_db.h warning: integer constant is too large for 'long'

Changes by Amaury Forgeot d'Arc : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue7065] bytes.maketrans segfaults

Antoine Pitrou added the comment: Patch committed in r75404 and r75406. Thanks! -- nosy: +pitrou resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue7069] inspect.isabstract to return boolean values only

Changes by Benjamin Peterson : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list

[issue7129] 'filling' missing in __all__

New submission from Gregor Lingl : By oversight the turtle graphics function filling is missing in the __all__ list which is composed by several parts, among them _tg_turtle_functions. So 'filling' has to be added to _tg_turtle_functions a path is attached -- components: Library (Lib)

[issue7129] 'filling' missing in __all__ ot turtle.py

Changes by Gregor Lingl : -- title: 'filling' missing in __all__ -> 'filling' missing in __all__ ot turtle.py ___ Python tracker ___ __

[issue7129] 'filling' missing in __all__ ot turtle.py

Georg Brandl added the comment: Fixed in r75416. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue7116] str.join() should be documented as taking an iterable

Georg Brandl added the comment: Thanks, fixed in r75418. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7130] json uses sre_* modules which may not work on alternate implemenations

New submission from Dino Viehland : Currently the json module is using the sre_* modules to construct it's regular expressions instead of just using the re module directly. Because of this it's taking a dependency on what would appear to be CPython specific implementation details (sre_* appe

[issue4610] Unicode case mappings are incorrect

Jeff Senn added the comment: > Feel free to upload it here. I'm fairly skeptical that it is > possible to implement casing "correctly" in a locale-independent > way. Ok. I will try to find time to complete it enough to be readable. Unicode (see sec 3.13) specifies the casing of unicode strings

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Antoine Pitrou added the comment: I've fixed a bunch of them: aifc (r75407), test_atexit (r75408), bsddb (r75409), test_calendar (r75410), StringIO (r75411), socket (r75412), sndhdr (r75413), test_memoryio (r75415), test_profilehooks (r75417), test_random (r75419), httplib (r75420), uuid (r75421

[issue1754094] Tighter co_stacksize computation in stackdepth_walk

Neil Schemenauer added the comment: Committed to the Python 2.x and 3.x trunks. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ _

[issue7131] Extension module build fails for MinGW: missing vcvarsall.bat

New submission from Dieter Verfaillie : Using Python 2.6.3 on Windows XP, distutils fails building an extension module when mingw32 is specified as the compiler. Distutils fails with the error message "Unable to find vcvarsall.bat". Looking back in the subversion history for the distutils build_

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Antoine Pitrou added the comment: Here is a record of stderr after a new regrtest run. -- Added file: http://bugs.python.org/file15129/stderr.log ___ Python tracker ___ _

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Antoine Pitrou added the comment: (interestingly, one of the culprits for py3k warnings is lib2to3) -- ___ Python tracker ___ ___ Pyth

[issue7110] Output test failures on stderr in regrtest.py

Changes by Ezio Melotti : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue4610] Unicode case mappings are incorrect

Jeff Senn added the comment: Yikes! I just noticed that u''.title() is really broken! It doesn't really pay attention to word breaks -- only characters that "have case". Therefore when there are (caseless) combining characters in a word it's really broken e.g. >>> u'n\u0303on\u0303e'.title

[issue6855] ihooks support for relative imports

Neil Schemenauer added the comment: I've been using this version of ihooks for some time and it seems to work fine. Committing the patch. -- resolution: -> accepted stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue4152] ihooks module cannot handle absolute imports

Neil Schemenauer added the comment: Fixed in SVN rev 75423. -- nosy: +nascheme resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue1101399] dict subclass breaks cPickle noload()

Neil Schemenauer added the comment: Applied to 2.x trunk. The 3.x version _pickle.c doesn't have the noload method. -- resolution: -> accepted status: open -> closed ___ Python tracker

[issue7120] logging depends on multiprocessing

Vinay Sajip added the comment: Fix checked into release26-maint (r75425). Please verify in GAE environment, will make same fix in trunk and py3k once verified. Fixed based on Antoine's message, though not identical to his posted code. -- resolution: -> fixed status: open -> pending _

[issue7132] Regexp: capturing groups in repetitions

New submission from Philippe Verdy : For now, when capturing groups are used within repetitions, it is impossible to capure what they match individually within the list of matched repetitions. E.g. the following regular expression: (0|1[0-9]{0,2}|2(?:[0-4][0-9]?|5[0-5]?)?)(?:\.(0|1[0-9]{0,2}|

[issue4610] Unicode case mappings are incorrect

Marc-Andre Lemburg added the comment: Jeff Senn wrote: > > Jeff Senn added the comment: > > Yikes! I just noticed that u''.title() is really broken! > > It doesn't really pay attention to word breaks -- > only characters that "have case". > Therefore when there are (caseless) > combining

[issue4610] Unicode case mappings are incorrect

Marc-Andre Lemburg added the comment: Jeff Senn wrote: > However .capitalize() is a bit weird; and I'm not sure it isn't > incorrectly implemented now: > > It UPPERCASES the first character, rather than TITLECASING, which is > probably wrong in the very few cases where it makes a difference:

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: I'd like to add that the same behavior should also affect the span(index) method of MatchObject, that should also not just return a single (start, end) pair, but that should in this case return a list of pairs, one for each occurence, when the "R" compilation

[issue4610] Unicode case mappings are incorrect

Raymond Hettinger added the comment: > .swapcase() is just ...err... dumb^h^h^h^h questionably useful. FWIW, it appears that the original use case (as an Emacs macro) was to correct blocks of text where touch typists had accidentally left the CapsLocks key turned on: tHE qUICK bROWN fOX jUMPE

[issue812369] module shutdown procedure based on GC

Alexander Belopolsky added the comment: Does this patch fix issue1545463 by any chance? I am away from a development box ATM and cannot test the patch myself. -- nosy: +belopolsky ___ Python tracker ___

[issue812369] module shutdown procedure based on GC

Changes by Gregory P. Smith : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mai

[issue6855] ihooks support for relative imports

Brett Cannon added the comment: Sorry I didn't get to this, Neil. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: Rationale for the compilation flag: You could think that the compilation flag should not be needed. However, not using it would mean that a LOT of existing regular expressions that already contain capturing groups in repetitions, and for which the caputiring

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: Implementation details: Currently, the capturing groups behave quite randomly in the values returned by MachedObject, when backtracking occurs in a repetition. This proposal will help fix the behavior, because it will also be much easier to backtrack cleanly

[issue7132] Regexp: capturing groups in repetitions

Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue7120] logging depends on multiprocessing

Guido van Rossum added the comment: Confirmed, the stack limit error is gone now. Thanks!! (There's another error, the import of _scproxy from urllib, but that's easily added to the App Engine SDK's whitelist. I am still concerned about the amount of change in the 2.6 branch, but the cat is o

[issue7120] logging depends on multiprocessing

Guido van Rossum added the comment: (I don't know why the tracker reopened the issue when I added a comment. Anyway, is the fix going into 2.6.4 or will it have to wait for 2.6.5?) -- ___ Python tracker __

[issue812369] module shutdown procedure based on GC

Neil Schemenauer added the comment: It should fix issue1545463 and running a quick test seems to show that it does. -- ___ Python tracker ___ __

[issue7132] Regexp: capturing groups in repetitions

Ezio Melotti added the comment: I'm skeptical about what you are proposing for the following reasons: 1) it doesn't exist in any other implementation that I know; 2) if implemented as default behavior: * it won't be backward-compatible; * it will increase the complexity; 3) it will be a pr

[issue7120] logging depends on multiprocessing

Vinay Sajip added the comment: > Guido van Rossum added the comment: > > (I don't know why the tracker reopened the issue when I added a comment. > Anyway, is the fix going into 2.6.4 or will it have to wait for 2.6.5?) That's OK, I'll close it once I've made the same changes in trunk and p

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Jeff Senn added the comment: Referred to this from issue 4610... anyone following this might want to look there as well. -- nosy: +senn ___ Python tracker ___ __

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Jeff Senn added the comment: So, is it not considered a bug that: >>> "This isn't right".title() "This Isn'T Right" !?!?!? -- ___ Python tracker ___ ___

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Marc-Andre Lemburg added the comment: Jeff Senn wrote: > > Jeff Senn added the comment: > > So, is it not considered a bug that: > "This isn't right".title() > "This Isn'T Right" > > !?!?!? That's http://bugs.python.org/issue7008 and is fixed as part of http://bugs.python.org/issue641

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: Note that I used the IPv4 address format only as an example. There are plenty of other more complex cases for which we really need to capture the multiple occurences of a capturing group within a repetition. I'm NOT asking you how to parse it using MULTIPLE r

[issue7130] json uses sre_* modules which may not work on alternate implemenations

Antoine Pitrou added the comment: This doesn't seem true on trunk/py3k (2.7, 3.2) anymore. Please reopen if I'm wrong. -- nosy: +bob.ippolito, pitrou resolution: -> out of date status: open -> closed versions: +Python 2.7, Python 3.2 ___ Python trac

[issue7128] cPickle looking for non-existent package copyreg

Changes by Antoine Pitrou : -- keywords: +easy priority: -> high stage: -> needs patch versions: +Python 2.7 ___ Python tracker ___ _

[issue7120] logging depends on multiprocessing

R. David Murray added the comment: On Wed, 14 Oct 2009 at 21:46, Vinay Sajip wrote: > Vinay Sajip added the comment: >> Guido van Rossum added the comment: >> >> (I don't know why the tracker reopened the issue when I added a comment. >> Anyway, is the fix going into 2.6.4 or will it have to w

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: In addition, your suggested regexp for IPv4: '^(\d{1,3})(?:\.(\d{1,3})){3}$' is completely WRONG ! It will match INVALID IPv4 address formats like "000.000.000.000". Reread the RFCs... because "000.000.000.000" is CERTAINLY NOT an IPv4 address (if it is foun

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: You're wrong, it WILL be compatible, because it is only conditioned by a FLAG. The flag is there specifically for instructing the parser to generate lists of values rather than single values. Without the regular compilation flag set, as I said, there will be

[issue7133] test_ssl failure

New submission from Antoine Pitrou : This is due to r75412 (yes, mine). The proper fix would be to add support for the new buffer API to the _ssl module. testSocketServer (test.test_ssl.ThreadedTests) ... server (('127.0.0.1', 52011):52011 ('AES256-SHA', 'TLSv1/SSLv3', 256)): [15/Oct/2009

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: Summary of your points with my responses : > 1) it doesn't exist in any other implementation that I know; That's exactly why I proposed to discuss it with the developers of other implementations (I cited PCRE, Perl and PHP developers, there are others). >

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: And anyway, my suggestion is certainly much more useful than atomic groups and possessive groups that have much lower use, and which are already being tested in Perl but that Python (or PCRE, PHP, and most implementations of 'vi'/'ed', or 'sed') still does no

[issue7132] Regexp: capturing groups in repetitions

R. David Murray added the comment: If you read what Ezio wrote carefully you will see that he addressed both of your points: he acknowledged that a flag would solve (2) (but disagreed that it was worth it), and he said you could use the first expression to validate the string before using the sp

[issue7133] test_ssl failure

Antoine Pitrou added the comment: Here is a possible patch. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file15130/ssl_newbuf.patch ___ Python tracker __

[issue7132] Regexp: capturing groups in repetitions

R. David Murray added the comment: Just to clarify, when I said "in most cases such an issue would need to include a proposed patch", I mean that even if everyone agrees it is a good idea it isn't likely to happen unless there is a proposed patch :) -- _

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: I had read carefully ALL what ezio said, this is clear in the fact that I have summarized my responses to ALL the 4 points given by ezio. Capturing groups is a VERY useful feature of regular expressions, but they currently DON'T work as expected (in a useful

[issue7132] Regexp: capturing groups in repetitions

Ezio Melotti added the comment: > You're wrong, it WILL be compatible, because it is only conditioned > by a FLAG. Sorry, I missed that you mentioned the flag already in the first message, but what I said in 1), 3) and 4) is still valid. > There are plenty of other more complex cases for which

[issue7134] Add looping capability to regrtest

New submission from Jesse Noller : We should add "loop this test" capabilities to regrtest - running tests in a tight loop can help debug issues which don't appear with a one-off run. See: http://mail.python.org/pipermail/python-dev/2009-June/090238.html -- assignee: jnoller components

[issue7134] Add looping capability to regrtest

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: ezio said: >>> re.match('^(\d{1,3})(?:\.(\d{1,3})){3}$', '192.168.0.1').groups() ('192', '1') > If I understood correctly what you are proposing, you would like it to return (['192'], ['168', '0', '1']) instead. Yes, exactly ! That's the correct answer that sho

[issue7120] logging depends on multiprocessing

Jesse Noller added the comment: >The addition of multiprocessing support to logging seems to have happened > in 2.6.2; bad timing for a feature. :-( Just in minor self-defense, this wasn't a feature, it was a bug fix. The original multiprocessing code base relied on some unfortunate monkey-

[issue7135] AttributeError: 'module' object has no attribute 'HTTPSConnection'

New submission from Andi Welch : I received a working script created with Active Python 2.6.2 for Windows 32 bit. I downloaded the Active Python 64 bit Windows version for my 64 bit Windows Vista OS and have attempted to run the script. I get the following error: Traceback (most recent call

[issue7132] Regexp: capturing groups in repetitions

Philippe Verdy added the comment: > That's why I wrote 'without checking if they are in range(256)'; the fact that this regex matches invalid digits was not relevant in my example (and it's usually easier to convert the digits to int and check if 0 <= digits <= 255). :) NO ! You have to check a

[issue7135] AttributeError: 'module' object has no attribute 'HTTPSConnection'

Changes by A Welch : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

  1   2   >