[issue29276] HTMLParser in Python 2.7 doesn't recognize image tags wrapped up in link tags

2017-01-14 Thread Ari
New submission from Ari: The following code produces incorrect results under Python 2.7.13. One would expect it to print 2 lines, "Encountered a start tag: a" and "Encountered a start tag: img". Yet it prints only "Encountered a start tag: a". from HTML

[issue29276] HTMLParser in Python 2.7 doesn't recognize image tags wrapped up in link tags

2017-01-14 Thread Ari
Ari added the comment: Sorry, it was a false alarm. I had a poorly constructed testcase. I was trying to grab all image links from html markup while simultaneously substituting image links to somesite.com with links to anothersite.com. I had handle_starttag and handle_startendtag defined in

[issue9631] Python 2.7 installation issue for Linux gcc-4.1.0-3 (Fedora Core 5?)

2010-11-21 Thread Ari Consul
Ari Consul added the comment: Similar error on make install. Using Centos 5 /usr/bin/install -c -m 644 ./LICENSE /home/ac927k/local/Python-2.7/lib/python2.7/LICENSE.txt PYTHONPATH=/home/ac927k/local/Python-2.7/lib/python2.7 \ ./python -Wi -tt /home/ac927k/local/Python-2.7

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
New submission from Ari Makela <[EMAIL PROTECTED]>: The base class, ConfigParser.RawConfigParser does not inherit object and therefore it is a classic class. Test script run with my normal python installation: $ /usr/bin/python -V Python 2.5.2 $ /usr/bin/python arska/configparser.py ba

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10711/configparser.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10711/configparser.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10712/configparser.py ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3181] ConfigParsers are classic classes

2008-06-24 Thread Ari Makela
Ari Makela <[EMAIL PROTECTED]> added the comment: New-style classes make object orientated programming considerably more convenient. For example one can use property() instead of __setitem__ et al. There's super(). This is, of course, not a serious problem and one can always

[issue33274] minidom removeAttributeNode returns None

2018-04-13 Thread Ari Krupnik
New submission from Ari Krupnik : W3C DOM Level 1[1] requires removeAttributeNode() to return the removed node: removeAttributeNode: Removes the specified attribute. Return Value: The Attr node that was removed. Minidom implementation returns None. [1]https://www.w3.org/TR/1998/REC-DOM-Level

[issue33274] minidom removeAttributeNode returns None

2018-04-13 Thread Ari Krupnik
Change by Ari Krupnik : -- type: -> behavior ___ Python tracker <https://bugs.python.org/issue33274> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue33274] minidom removeAttributeNode returns None

2018-04-20 Thread Ari Krupnik
Ari Krupnik added the comment: I guess the main question if whether minidom wants to adhere to the standard or be pythonic, and it's not up to me to decide, although personally I like standards. The common use case for DOM functions returning the relevant nodes is for the caller to

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Change by Ari Krupnik : -- keywords: +patch pull_requests: +7086 stage: test needed -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Change by Ari Krupnik : -- pull_requests: +7087 ___ Python tracker <https://bugs.python.org/issue33274> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Ari Krupnik added the comment: I added a test case and a News entry per serhiy.storchaka's request. https://github.com/python/cpython/pull/7465 I agree with fdrake's concerns about DOM's usefulness. DOM is not very Pythonic. I note that as long as Python has a DOM implementat

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Change by Ari Krupnik : -- pull_requests: -7086 ___ Python tracker <https://bugs.python.org/issue33274> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Change by Ari Krupnik : -- pull_requests: +7088 ___ Python tracker <https://bugs.python.org/issue33274> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33274] minidom removeAttributeNode returns None

2018-06-06 Thread Ari Krupnik
Ari Krupnik added the comment: My bad. This issue looks like a simple omission to me--albeit one that's been in the code a long time. My patch simply brings the code into compliance with what the documentation (including in 2.7) already says it

[issue33274] minidom removeAttributeNode returns None

2018-06-07 Thread Ari Krupnik
Ari Krupnik added the comment: I feel a little bit like I wandered into a card game whose rules I didn't understand. I'm just a lay, mortal user. I've been writing Python for 15 years, first time I saw an opportunity to contribute back. I saw what looked to me like a bug tha

[issue33274] minidom removeAttributeNode returns None

2018-06-07 Thread Ari Krupnik
Ari Krupnik added the comment: In retrospect, I wish I had submitted this as a documentation change, simply acknowledging this function's behavior. "In most computer projects there comes a day when it is discovered that the machine and the manual don't agree. When the confro

[issue12954] Multiprocessing logging under Windows

2014-08-12 Thread Ari Koivula
Ari Koivula added the comment: I encountered this problem on Python 3.2.5 on Windows and don't think a vague warning about initializing modules is a proper solution. A better solution would be to simply not add multiple handlers, even if log_to_stderr is called more than

[issue12954] Multiprocessing logging under Windows

2014-08-13 Thread Ari Koivula
Ari Koivula added the comment: Guarding the initialization is indeed correct and works, but log_to_stderr adding the handler multiple times is still annoying. Especially as you probably do want it to be called for child processes (at least on windows) and it might be called during

[issue12954] Multiprocessing logging under Windows

2014-08-13 Thread Ari Koivula
Ari Koivula added the comment: Actually, multiprocessing.forking.prepare does call log_to_stderr on windows. While debugging the double handler issue I somehow came to the conclusion that it didn't, but it seems to work just fine now. I must have been doing something weird like creatin