om] Im Auftrag von Tomas Matousek
> Gesendet: Mittwoch, 16. März 2011 17:41
> An: Discussion of IronPython
> Betreff: Re: [IronPython] IronPython 2.7.1 & 3.x Development
>
> Yes, you can do it and w/o any glue - the version of the assembly is a
> part of the name, so
Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Markus Schaber
Sent: Wednesday, March 16, 2011 12:24 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.7.1 & 3.x Development
Hi,
Von Tomas Matousek
>>&g
Hi,
Von Tomas Matousek
>>> As I wrote, we host IronPython inside our application, so shebang
and
>>> file name suffixes are irrelevant - but we could use the shebang as
a
>>> marker for python 3 (given that we can host both versions
>>> side-by-side) and parse the source manually to find out whic
Michael;
IIRC you are at pycon. (I am at the wrong end of America and Mark is at the
wrong end of Earth. I couldn't make it.)
Can you create/find a bof session to hash out a "standard" shebang? It
should be something good enough that 2to3 could have a fixer for it.
--
[ reminder for the day:
Now
on of IronPython
Subject: Re: [IronPython] IronPython 2.7.1 & 3.x Development
On Tue, Mar 15, 2011 at 9:55 AM, Markus Schaber
wrote:
> As I wrote, we host IronPython inside our application, so shebang and
> file name suffixes are irrelevant - but we could use the shebang as a
> m
On Tue, Mar 15, 2011 at 9:55 AM, Markus Schaber
wrote:
> As I wrote, we host IronPython inside our application, so shebang and
> file name suffixes are irrelevant - but we could use the shebang as a
> marker for python 3 (given that we can host both versions side-by-side)
> and parse the source ma
Hi, Vernon,
Von: Vernon Cole
> #!/usr/bin/ipy3
> A shebang on the first line is the usual way of specifying which
scripting engine to use on a posix system.
As I wrote, we host IronPython inside our application, so shebang and
file name suffixes are irrelevant - but we could use the shebang as a
On 15/03/2011 07:18, Vernon Cole wrote:
#!/usr/bin/ipy3
A shebang on the first line is the usual way of specifying which
scripting engine to use on a posix system. If introspection were to be
used to select between python versions, that would be the most obvious
way to do it.
Windows (tm)
#!/usr/bin/ipy3
A shebang on the first line is the usual way of specifying which scripting
engine to use on a posix system. If introspection were to be used to select
between python versions, that would be the most obvious way to do it.
Windows (tm) prefers to use filename extensions, which is wh
Hi, Jeff,
Von: Jeff Hardy
> With the 2.7 out the door, it's time to start thinking about 3.x. I've
> created a ipy-2.7-maint branch for continued 2.7 work (and it needs
some),
> and any 3.x work will go on master. Any 2.7 fixes that also go into
3.x
> (and really, most of them should) go into the
On Mon, Mar 14, 2011 at 7:50 AM, Vernon Cole wrote:
> I was running a test of adodbapi -- IPy 2.7 RC2 ran it fine, but CPython 2.7
> had errors. I was starting to debug the CPython when I discovered that I was
> running the Python _3_ version of the test suite! The "error" was in the
> Unicode vs
Sounds like a good plan, Jeff.
I got a quick hint the other day that IronPython 3.2 might not be as hard as
we think...
I was running a test of adodbapi -- IPy 2.7 RC2 ran it fine, but CPython 2.7
had errors. I was starting to debug the CPython when I discovered that I was
running the Python _3_
12 matches
Mail list logo
