Issue1362
Created on 2009-05-31.05:22:48 by pjenvey, last changed 2009-05-31.21:42:28 by pjenvey.
|
| msg4768 (view) |
Author: Philip Jenvey (pjenvey) |
Date: 2009-05-31.05:22:40 |
|
This method doesn't seem necessary. If so we should nuke it before 2.5
final. It was added in r5274 for passing underlying unicode Strings to
Normalizer.noramlize but this should 'just work' via __tojava__
In the rare case that pure Python needs the underlying unicode String as
a PyString you can use org.python.core.newString (os.py and pyexpat do
this)
|
| msg4772 (view) |
Author: Jim Baker (zyasoft) |
Date: 2009-05-31.09:24:48 |
|
Correct, this method was exposed as an early - and in fact not so useful
- workaround for to/from wrapping of java.lang.String when they were
mapped to str, not unicode.
I don't currently have a dev env set up here in China - I'm using my
brother-in-law's computer right now - so it might be better if someone
else can handle this removal.
|
| msg4775 (view) |
Author: Philip Jenvey (pjenvey) |
Date: 2009-05-31.21:42:27 |
|
fixed in r6435
|
|
| Date |
User |
Action |
Args |
| 2009-05-31 21:42:28 | pjenvey | set | status: open -> closed
resolution: fixed
messages:
+ msg4775 |
| 2009-05-31 09:24:49 | zyasoft | set | messages:
+ msg4772 |
| 2009-05-31 05:22:50 | pjenvey | create | |
|
