Hi Ralph
Yes this will be first task for Deborah.
Howard
Am Donnerstag, 12. Mai 2016 schrieb Ralph Castain :
> This looks like the right approach to me: write it as Python 3, but with
> the Python 2 backward compatibility support add-ons.
>
> Howard: let me know if this is something your intern
This looks like the right approach to me: write it as Python 3, but with the
Python 2 backward compatibility support add-ons.
Howard: let me know if this is something your intern could tackle for us.
> On May 12, 2016, at 5:06 AM, Howard Pritchard wrote:
>
> Hi Folks,
>
> I've been asking ar
Hi Folks,
I've been asking around. Its been suggested the route described in this
URL can be taken,
http://python-future.org/imports.html
2016-05-09 10:47 GMT-06:00 Ralph Castain :
> Good question - I'm not sure we can. What happens right now is you get
> syntax errors during the compile. I'
Good question - I'm not sure we can. What happens right now is you get
syntax errors during the compile. I'll have to play and see if we can
generate an error message before we hit that point.
On Mon, May 9, 2016 at 9:38 AM, Jeff Squyres (jsquyres)
wrote:
> Is it possible to give a friendly erro
Is it possible to give a friendly error message at run time if you accidentally
run with Python 3.x?
> On May 9, 2016, at 12:37 PM, Ralph Castain wrote:
>
> Hi folks
>
> As we look at the Python client, there is an issue with the supported Python
> version. There was a significant break in t
Hi folks
As we look at the Python client, there is an issue with the supported
Python version. There was a significant break in the user-level API between
Python 2.x and Python 3. Some of the issues are described here:
https://docs.python.org/2/glossary.html#term-2to3
Noah and I have chatted abo