I have cp34837, cp34892, cp34910 fixed. I will make a PR.
I also have some workarounds where I am not clear if they should get
into release:
1. cp32331 - better unicode success rate in real application, but
decreased number of unit test passed
2. update to installer to modify PATH and register .p
I know everyone wants to hear about ItonPython 3, but it's time to
talk about IronPython 2.7 for a bit. Enough changes have accumulated
(thanks Pawel!) that it's probably time for another release. I'm
thinking Beta 1 around March 17, Beta 2 around April 1, and an
RC/final around April 15. Does anyb
On Thu, Feb 27, 2014 at 8:10 PM, Pawel Jasinski
wrote:
> I just checked, the part in question is covered by MIT.
Oh, that's better. MIT is no problem (once upon a time parts of Mono
were LGPL, which is right out).
Also, I had assumed that Mono would use native platform libraries for
crypto. You
I just checked, the part in question is covered by MIT.
On Thu, Feb 27, 2014 at 8:48 PM, Slide wrote:
> I had asked this question before, but there was some hesitation based on the
> licensing of Mono. I'm not sure if that is an issue anymore.
>
>
> On Thu, Feb 27, 2014 at 12:16 PM, Pawel Jasinsk
I had asked this question before, but there was some hesitation based on
the licensing of Mono. I'm not sure if that is an issue anymore.
On Thu, Feb 27, 2014 at 12:16 PM, Pawel Jasinski
wrote:
> Is there any reason not to use code out of mono?
> It looks like it supports SHA2 and RIPEMD160.
> h
Is there any reason not to use code out of mono?
It looks like it supports SHA2 and RIPEMD160.
https://bugzilla.xamarin.com/show_bug.cgi?id=11703
On Thu, Feb 27, 2014 at 2:10 PM, Markus Schaber wrote:
> Hi,
>
> Von: Jeff Hardy [mailto:jdha...@gmail.com]
>> On Thu, Feb 27, 2014 at 11:11 AM, Markus
Hi,
Von: Jeff Hardy [mailto:jdha...@gmail.com]
> On Thu, Feb 27, 2014 at 11:11 AM, Markus Schaber
> wrote:
> > Hi,
> >
> > I'm just trying to sum it up:
> >
> > 1) The current code:
> >- High memory usage.
> >- High load on the large object heap.
> >- Limited by the available amount o
On Thu, Feb 27, 2014 at 11:11 AM, Markus Schaber wrote:
> Hi,
>
> I'm just trying to sum it up:
>
> 1) The current code:
>- High memory usage.
>- High load on the large object heap.
>- Limited by the available amount of memory (which might be considered a
> violation of the Python API
Hi,
I'm just trying to sum it up:
1) The current code:
- High memory usage.
- High load on the large object heap.
- Limited by the available amount of memory (which might be considered a
violation of the Python API).
- High CPU usage when used incrementally (quadratic to the number
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] Include some way to discover IronPython path
2. [New comment] Include some way to discover IronPython path
3. [New comment] Include some way to discover IronPython path
10 matches
Mail list logo
