Mailman 3 April 2013 - docs

Python on Mac OS X
by Barry E Abrahamsen 09 Apr '13

09 Apr '13

Hi, On this page: http://docs.python.org/3.3/using/mac.html in section 4.1.3. Configuration, it says "See Apple’s Technical Document QA1067 for details." If you go to this QA document, you find that Apple has "retired" that document: Retired Document Important: This document may not represent best practices for current development. Links to downloads and other resources may no longer be valid. There is a note on that page referring me to this page: https://developer.apple.com/library/mac/navigation/index.html but that's just a link to the entire developer library. Searching for "environment variables" gets me: https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BP… which isn't really very helpful. Is there any possibility of getting this information updated, at least in the 3.3 documentation? ===== Barry Abrahamsen Seattle, Washington http://www.abrahamsen.com/ http://www.AmericanBamboo.org/

1 0

[issue17674] All examples for concurrent.futures fail with "BrokenProcessPool"
by Brian Curtin 09 Apr '13

09 Apr '13

Brian Curtin added the comment: The example code works for me on 3.3.0 on Windows 8. I'd have to find a VM to try out XP like gjwebber - will look later. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17674> _______________________________________

1 0

[issue17674] All examples for concurrent.futures fail with "BrokenProcessPool"
by Antoine Pitrou 09 Apr '13

09 Apr '13

Antoine Pitrou added the comment: Ok, can someone else confirm the issue on Windows? ---------- nosy: +brian.curtin, sbt, tim.golden _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17674> _______________________________________

1 0

[issue17674] All examples for concurrent.futures fail with "BrokenProcessPool"
by gjwebber 09 Apr '13

09 Apr '13

gjwebber added the comment: Just ran the example code linked here again for my own sanity: http://docs.python.org/dev/library/concurrent.futures.html#processpoolexecu… Exactly the same thing happened. Here is the Traceback: Traceback (most recent call last): File "<string>", line 420, in run_nodebug File "<module1>", line 28, in <module> File "<module1>", line 24, in main File "C:\Python33\lib\concurrent\futures\_base.py", line 546, in result_iterator yield future.result() File "C:\Python33\lib\concurrent\futures\_base.py", line 399, in result return self.__get_result() File "C:\Python33\lib\concurrent\futures\_base.py", line 351, in __get_result raise self._exception concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17674> _______________________________________

1 0

[issue17674] All examples for concurrent.futures fail with "BrokenProcessPool"
by gjwebber 09 Apr '13

09 Apr '13

gjwebber added the comment: As mentioned in the previously linked post, I copy-pasted the example code shown here: http://docs.python.org/dev/library/concurrent.futures.html#processpoolexecu… Which resulted in exactly the same error as the 'more simple' example I provided. There is no mention of anything Windows specific on the documentation page, or any hints as to why this may not be working. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17674> _______________________________________

1 0

[issue17674] All examples for concurrent.futures fail with "BrokenProcessPool"
by Antoine Pitrou 09 Apr '13

09 Apr '13

Antoine Pitrou added the comment: This is not the example code. The example code uses a main() function which is guarded by a "if" block: if __name__ == '__main__': main() See http://docs.python.org/2/library/multiprocessing.html#windows for explanations. Also, perhaps the concurrent.futures docs could point to that paragraph. ---------- assignee: -> docs@python components: +Documentation -Library (Lib), Windows nosy: +docs@python, pitrou type: crash -> behavior versions: +Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17674> _______________________________________

1 0

[issue17668] re.split loses characters matching ungrouped parts of a pattern
by R. David Murray 08 Apr '13

08 Apr '13

R. David Murray added the comment: Only group the stuff you want to see in the result: >>> re.split(r'(^>.*$)', '>Homo sapiens catenin (cadherin-associated)') ['', '>Homo sapiens catenin (cadherin-associated)', ''] >>> re.split(r'^(>.*)$', '>Homo sapiens catenin (cadherin-associated)') ['', '>Homo sapiens catenin (cadherin-associated)', ''] If you are using grouping to get alternatives, you can use a non-capturing group: >>> re.split(r'(ca(?:t|d))', '>Homo sapiens catenin (cadherin-associated)') ['>Homo sapiens ', 'cat', 'enin (', 'cad', 'herin-associated)'] (By the way, I'm a bit confused as to what exactly you are splitting in your original example, since you seem to be matching the whole string, and only if it is the whole string. On the other hand, regular expressions regularly confuse me... :) I indeed do not think it is worth complicating the interface to handle the unusual case of accepting and applying unknown regexes. The one change I could see as a possibility would be to allow all of the groups matched by the split regex to appear as a single sublist. But I'm not the maintainer of this module either :) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17668> _______________________________________

1 0

[issue17668] re.split loses characters matching ungrouped parts of a pattern
by Tomasz J. Kotarba 08 Apr '13

08 Apr '13

Tomasz J. Kotarba added the comment: Hi, I can still see one piece of functionality I have mentioned missing. Using my first example, even when one uses '^(>(.*))$' one cannot get ['', '>Homo sapiens catenin (cadherin-associated)', ''] as one will get a four-element list and need to deal with the third element of the returned list (i.e. the match for a group). Having a parameter I have described before which allows for getting the output similar to what one gets for groups but for the whole pattern (and only that) would be very convenient for some scenarios (like when writing a procedure which processes texts using different (and unknown at the time of writing the procedure) regex patterns which uses a variable number of groups but also the pattern as a whole (also for performing the split operation)). Of course it can be worked around using many different approaches but still, as I said at start, I believe it would be useful (and would not break compatibility). Another possible solution (i.e. different than the one I suggested at start) would be to have a parameter to tell re.split to ignore the groups (or, going even further, to select which groups to ignore). Anyway, I am not the developer of this module so if you feel it would be too much of a bother to add such a parameter just for the sake of convenience then, by all means, please feel free to disregard my comments and just close this report. Cheers, T P.S. It is very late so I can only hope I have been sane enough to properly / clearly express my thoughts. Apologies if not. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17668> _______________________________________

1 0

[issue17668] re.split loses characters matching ungrouped parts of a pattern
by R. David Murray 08 Apr '13

08 Apr '13

R. David Murray added the comment: As you pointed out, you can already get that behavior by enclosing the entire split expression in a group. I don't see that there is any functionality missing here. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17668> _______________________________________

1 0

[issue17668] re.split loses characters matching ungrouped parts of a pattern
by Tomasz J. Kotarba 08 Apr '13

08 Apr '13

Tomasz J. Kotarba added the comment: I agree that introducing an example like that plus making some slight changes in wording would be a welcome change to the docs to clearly explain the current behaviour. Still, I maintain it would be useful to give users the option I described to allow them decide what output they get (i.e. also get texts matching the whole pattern and/or those matching the pattern and groups (e.g. pattern returned as kind of "group 0")). As I said though, I realise that it is not for me to decide so I am just suggesting it to the powers that be. Cheers, T ---------- components: -Documentation _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17668> _______________________________________

1 0