ttp://store.codesys.com
>> CODESYS forum: http://forum.codesys.com
>>
>> Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade
>> register: Kempten HRB 6186 | Tax ID No.: DE 167014915
>>
>>> -Ursprüngliche Nachricht-
>>>
t;
>> -Ursprüngliche Nachricht-
>> Von: Jeff Hardy [mailto:[email protected]]
>> Gesendet: Dienstag, 4. Februar 2014 10:01
>> An: Markus Schaber
>> Cc: [email protected]
>> Betreff: Re: [Ironpython-users] Splitting up the IronPython repo
>
Hi,
Von: Ironpython-users [mailto:ironpython-users-
> Have no problems with either IronPython.sln or Git here at HEAD
> ed928f6b39bff20a2f60225193b459581b9b756e
> with VS 2010 Ultimate and TortoiseGit 1.8.5.0 .
It seems you're at a different repository.
On my machine, the IronPython only reposit
Have no problems with either IronPython.sln or Git here
at HEAD ed928f6b39bff20a2f60225193b459581b9b756e
with VS 2010 Ultimate and TortoiseGit 1.8.5.0 .
-Original Message-
From: Markus Schaber
Sent: Tuesday, February 4, 2014 12:21
To: Jeff Hardy
Cc:
Subject: [Ironpython-users] Splitting
he Nachricht-
> Von: Jeff Hardy [mailto:[email protected]]
> Gesendet: Dienstag, 4. Februar 2014 10:01
> An: Markus Schaber
> Cc: [email protected]
> Betreff: Re: [Ironpython-users] Splitting up the IronPython repo
>
> I did most of the work on my MacBook, just runni
I did most of the work on my MacBook, just running MSBuild from the
command line; it might still need some tweaking to work from VS. The
main thing is making sure all of the properties are set when just
loading the projects (not using Build.proj as a wrapper). If you look
in the .csproj file, it tr
Hi, Jeff,
I tried to open the IronPython solution file using Visual Studio 2010 Pro and
2012 Express for Desktop. Both failed to open the IronPython, IronPython and
IronPython.SQLite projects with the following error messages:
D:\Contribs\Ironpython\ironpython-only\Src\IronPython\IronPython.cs
+1 on splitting.
I have been trying to quietly lobby for returning IronPython into the
Ubuntu distribution.
Splitting out Ruby would be a helpful step.
On Wed, Jan 22, 2014 at 3:20 PM, Doug Blank wrote:
> +1 for these plans! I think this split will be good for the dlr, which
> hasn't (so far)
+1 for these plans! I think this split will be good for the dlr, which
hasn't (so far) been used as much as it could.
BTW, (and this is a small point) even though IronRuby is dead and was
never complete, it is still functional for some purposes. So, if it is
possible without major time commitments
On Mon, Jan 20, 2014 at 10:13 AM, Markus Schaber wrote:
> Hi, Jeff,
>
> Good work, I'm all in favour of it. Splitting DLR, IronPython and IronRuby
> into different projects is a good thing.
>
> Just some unordered thoughts:
>
> The python standard library could be fetched by the build script dire
Hi, Jeff,
Good work, I'm all in favour of it. Splitting DLR, IronPython and IronRuby into
different projects is a good thing.
Just some unordered thoughts:
The python standard library could be fetched by the build script directly from
the cPython servers (maybe with a few local patches applied
11 matches
Mail list logo
