From: "Peter J. Holzer"
From: "Peter J. Holzer"
--prnws536gtytpj5v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2018-06-22 17:20:29 -0700, denis.akhiya...@gmail.com wrote:
> Either wait for IronPython 3.6, use COM intero
To: Steven D'Aprano
From: "wxjmfauth"
To: Steven D'Aprano
From: wxjmfa...@gmail.com
Le vendredi 22 juin 2018 11:07:15 UTC+2, Steven D'Aprano a ─CcritΓ :
>
> C# <--> IronPython 2.7 <--> CPython 3.6
>
C# <--> IronPython 2.7.
It will not work. Coding of characters ! Try with IronPython 2.7.8.
To: Schachner, Joseph
From: "denis akhiyarov"
To: Schachner, Joseph
From: denis.akhiya...@gmail.com
Either wait for IronPython 3.6, use COM interop, pythonnet, subprocess, or
things like gRPC. Based on PyPy experience, it is probably 1-2 years of
sponsored development to get a working IronPy
From: "Peter J. Holzer"
--prnws536gtytpj5v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2018-06-22 17:20:29 -0700, denis.akhiya...@gmail.com wrote:
> Either wait for IronPython 3.6, use COM interop, pythonnet,
> subprocess
To: Steven D'Aprano
From: wxjmfa...@gmail.com
Le vendredi 22 juin 2018 11:07:15 UTC+2, Steven D'Aprano a ─CcritΓ :
>
> C# <--> IronPython 2.7 <--> CPython 3.6
>
C# <--> IronPython 2.7.
It will not work. Coding of characters ! Try with IronPython 2.7.8.
PS Yes, I know, it is based on .NET !!!
To: Schachner, Joseph
From: denis.akhiya...@gmail.com
Either wait for IronPython 3.6, use COM interop, pythonnet, subprocess, or
things like gRPC. Based on PyPy experience, it is probably 1-2 years of
sponsored development to get a working IronPython 3.6.
--- BBBS/Li6 v4.10 Toy-3
* Origin: Pri
On 2018-06-22 17:20:29 -0700, denis.akhiya...@gmail.com wrote:
> Either wait for IronPython 3.6, use COM interop, pythonnet,
> subprocess, or things like gRPC. Based on PyPy experience, it is
> probably 1-2 years of sponsored development to get a working
> IronPython 3.6.
What is the current state
Either wait for IronPython 3.6, use COM interop, pythonnet, subprocess, or
things like gRPC. Based on PyPy experience, it is probably 1-2 years of
sponsored development to get a working IronPython 3.6.
--
https://mail.python.org/mailman/listinfo/python-list
Wait.
-Original Message-
From: fantasywan...@gmail.com
Sent: Friday, June 22, 2018 2:45 AM
To: python-list@python.org
Subject: ironpython not support py3.6
We have a project implemented with c# and python, iron python is a good choice
for us to integrate these two tech together but
On Thu, 21 Jun 2018 23:44:40 -0700, fantasywangxg wrote:
> We have a project implemented with c# and python, iron python is a good
> choice for us to integrate these two tech together but iron python not
> support python 3.6 yet, any suggest for this?
How big is your budget? Could you pay the Ir
We have a project implemented with c# and python, iron python is a good choice
for us to integrate these two tech together but iron python not support python
3.6 yet, any suggest for this?
--
https://mail.python.org/mailman/listinfo/python-list
11 matches
Mail list logo
