I think it is a misinterpretation that this topic goes away with Python3. Both
Python2 and Python3 provide *two* string types. Hence, having a second string
type in IronPython would certainly help Python2 compatibility as well as
Python3 compatibility.
I don't agree with your statement about .
il is strictly forbidden.
From: Ironpython-users
[mailto:ironpython-users-bounces+m.schaber=codesys@python.org] On Behalf Of
Pawel Jasinski
Sent: Saturday, September 17, 2016 12:14 PM
To: ironpython-users@python.org
Subject: [Ironpython-users] string/unicode
hi,
I have noticed that the long
As usual, I agree with you Pawel :)
That said, I don't have a lot of "handcrafted tweaks for str/unicode
aliasing", so it's easy for me to dismiss that negative.
To me, your proposal sounds elegant, but I am open to consensus.
--Tim
On Sat, Sep 17, 2016 at 3:13 AM, Pawel Jasinski
wrote:
> hi,
hi,
I have noticed that the long standing string/unicode subject surfaced again
in chat (#1414)
For long time I was convinced that jython uses the same strategy as
ironpython in regards to str/unicode aliasing. There was hope to get
cpython compatibility at similar level as jython (e.g. django wor
