Issue 1777: ElementTree/cElementTree findtext inconsistency
Created on 2008-01-09 18:58 by gmonroe, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| etree_test.py | gmonroe, 2008-01-09 18:58 | a simple example demonstrating the inconsistency | ||
| Messages (5) | |||
|---|---|---|---|
| msg59618 - (view) | Author: Grant Monroe (gmonroe) | Date: 2008-01-09 18:58 | |
cElementTree findtext seems to return None when it should return a string. |
|||
| msg59620 - (view) | Author: Martin v. Löwis (loewis) * ![]() |
Date: 2008-01-09 19:22 | |
Fredrik, can you take a look? |
|||
| msg59621 - (view) | Author: Fredrik Lundh (effbot) * ![]() |
Date: 2008-01-09 19:35 | |
Looks like the mechanisms used decide when to invoke the full ElementPath machinery differs somewhat. I've added this to the TODO list for ET 1.3; in the meantime, my advice is "don't do that". (adding a check for '.' to the PATHCHAR macro should fix this, I think.) |
|||
| msg79561 - (view) | Author: Fredrik Lundh (effbot) * ![]() |
Date: 2009-01-10 17:43 | |
Forgot to mention that this is fixed in the cElementTree trunk (public as of today's 1.0.6 preview release). Will merge with Python trunk when I find the time... |
|||
| msg99396 - (view) | Author: Florent Xicluna (flox) * ![]() |
Date: 2010-02-16 11:46 | |
Should be fixed with the next upstream merge. See #6472 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:29 | admin | set | github: 46110 |
| 2010-02-16 11:46:13 | flox | set | status: open -> closed nosy:
+ flox superseder: Update ElementTree with upstream changes |
| 2009-01-10 17:43:35 | effbot | set | messages: + msg79561 |
| 2008-01-09 19:35:48 | effbot | set | priority: normal messages: + msg59621 |
| 2008-01-09 19:22:13 | loewis | set | assignee: effbot messages: + msg59620 nosy: + loewis, effbot |
| 2008-01-09 18:58:07 | gmonroe | create | |
