Python-2.x "from future import unicode_literals" brings BAD_PARAM

Jim Bell via omniORB-list <[email protected]> Sun, 10 Nov 2019 09:35:48 -0600

Newsgroups	gmane.comp.corba.omniorb.user
Organization	J. C. Bell & Associates, Inc.
Message-ID	<[email protected]>

omniORBpy-4.2.3.

I found that using "from __future__ import unicode_literals" wreaks 
havoc on my app code, with every string parameter or field value giving 
CORBA.BAD_PARAM/omniORB.BAD_PARAM_WrongPythonType.

Littering the code either with str(x) conversions, or obsessing about 
disallowing unicode_literals--both seem uncool.

Is there a single hook I can use? I think even a monkey-patch would be 
preferable.  Am I missing something obvious?  Py-3.x I'm sure will be fine.

Thanks,

-Jim



_______________________________________________
omniORB-list mailing list
[email protected]
http://www.omniorb-support.com/mailman/listinfo/omniorb-list