Hi, Jeff,
Von: Jeff Hardy [mailto:jdha...@gmail.com]
>
> Also, there might be some changes that require 3.5 (use of Linq, etc.)
> since I don't know if anyone was testing on plain-old .NET 2.0 (I
think
> the v2 targets are actually set for 3.5). There are supposed to be
targets
> on the build ser
Hi, Jimmy,
Von: Jimmy Schementi [mailto:jscheme...@gmail.com]
> On Jul 27, 2011, at 2:28 AM, Markus Schaber wrote:
>> It seems that IronPython 2.7 beta 2 can only be compiled for .NET 3.5, but
>> will not work any more when the projects are converted to be pure .NET 2.0
>> projects (using Shar
Also, there might be some changes that require 3.5 (use of Linq, etc.)
since I don't know if anyone was testing on plain-old .NET 2.0 (I
think the v2 targets are actually set for 3.5). There are supposed to
be targets on the build server that build .NET 2, but I'm not sure if
they're working. Of co
On Wed, Jul 27, 2011 at 9:01 AM, Vernon Cole wrote:
> I am using this as a renewal of my request/suggestion that we revisit
> the decision to not supply a .NET 2.0 version of IronPython 2.7.
I'm considering doing a zip-only release of 2.7.1 for .NET 2 for the
reasons that you give. I need to fix
We do still have the v2Debug build configuration available in the csproj files,
and IronPython.Mono.sln still allows building it:
msbuild Solutions\IronPython.Mono.sln /p:Configuration=v2Debug
However, current sources fail to build in a few places. Looks like you can put
#if !CLR2 around those a
I am using this as a renewal of my request/suggestion that we revisit
the decision to not supply a .NET 2.0 version of IronPython 2.7.
The current shipping version of Ubuntu has the .NET 2.0 compatible
version of MONO, and cannot easily be upgraded. It cannot be used to
build IronPython, so user
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] os.access(..., os.F_OK) is incorrect for directories
--
ISSUES
1. [New issue] os.access(..., os.F_OK) is incorrect for directorie
