[IPython-dev] 0.13.2

[MinRK]

On Thu, Mar 14, 2013 at 7:23 AM, David Verelst <david.verelst at gmail.com>wrote:

> Hi,
>
> I just want to mention that due to the issue #2831<https://github.com/ipython/ipython/issues/2831>IPython fails to start with PyQt 4.10. This case occurs for the next Ubuntu
> release (13.04), future Fedora (scheduled for June), and is already current
> in Arch Linux.
>

And that's precisely why it is backported to 0.13.2.  We will start the
release cycle after PyCon / PyData - if there's a reason to hasten the
release (e.g. 13.04 deadlines), I am fine calling the current state of
0.13.x an RC.


>
> Since this is my first message on this list, I just want to show my
> appreciation for this great piece of software by shouting: Thanks!
>

Much appreciated!



>
> Best regards,
> David
>
>
> On 14 March 2013 03:36, MinRK <benjaminrk at gmail.com> wrote:
>
>>
>> On Mar 13, 2013, at 14:46, Jonathan March <JDM at MarchRay.net> wrote:
>>
>>>
>>> Min et al,
>>> It looks like the backport-0.13.2 issue queue was emptied 3 days ago --
>>> impressive feat, Min.
>>
>>
>> I actually wrote the queue at the same time as applying the patches, so
>> perhaps not so impressive that the queue was flushed quickly :)
>>
>> Any sense of the likely timeline of this release? Enthought is fast
>>> approaching release of Canopy 1.0 (next generation EPD). It will of
>>> necessity be based on IPython > 0.13.1. Obviously it would be desirable all
>>> around if that were a named version, i.e. 0.13.2.
>>
>>
>> No specific timeline, but I don't think there are any more fixes that
>> need to go in.  I will probably do a bit of testing and cut an RC once the
>> dust settles after PyCon/PyData next week, then, assuming I didn't break
>> everything, we should have a release a week or two after that, so ~ 4/1 I
>> guess?
>>
>> -MinRK
>>
>>
>> Thanks,
>>> Jonathan
>>
>>
>>
>> On Mon, Mar 4, 2013 at 9:34 PM, MinRK <benjaminrk at gmail.com> wrote:
>>
>>> I've started the process of backporting PRs for an 0.13.2 bugfix release,
>>> the results of which can be seen by looking at Issues labeled
>>> backport-0.13.2<https://github.com/ipython/ipython/issues?labels=backport-0.13.2&state=closed>
>>> .
>>>
>>> The following PRs have been backported so far:
>>>
>>> 2399
>>> 2503
>>> 2500
>>> 2498
>>> 2490
>>> 2491
>>> 2511
>>> 2294
>>> 2554
>>> 2561
>>> 2546
>>> 2526
>>> 2591
>>> 2582
>>> 2574
>>> 2638
>>> 2656
>>> 2663
>>> 2668
>>> 2662
>>> 2686
>>> 2685
>>> 2713
>>> 2717
>>> 2544
>>> 2749
>>> 2738
>>> 2769
>>> 2773
>>> 2778
>>> 2757
>>> 2783
>>> 2796
>>> 2799
>>> 2816
>>> 2830
>>> 2849
>>> 2859
>>> 2861
>>> 2863
>>> 2852
>>> 2864
>>> 2926
>>> 2924
>>> 2901
>>>
>>> If there are any others you think should be applied for 0.13.2, or if
>>> any of those shouldn't be included, let me know.
>>> In general, these are bugfixes that are either small or important.  No
>>> new features or APIs, etc.
>>>
>>> This is currently reflected in the 0.13.x branch<https://github.com/ipython/ipython/tree/0.13.x>
>>> .
>>>
>>> -MinRK
>>>
>>> _______________________________________________
>>> IPython-dev mailing list
>>> IPython-dev at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>
>>>
>>
>> On Mon, Mar 4, 2013 at 9:34 PM, MinRK <benjaminrk at gmail.com> wrote:
>>
>>> I've started the process of backporting PRs for an 0.13.2 bugfix release,
>>> the results of which can be seen by looking at Issues labeled
>>> backport-0.13.2<https://github.com/ipython/ipython/issues?labels=backport-0.13.2&state=closed>
>>> .
>>>
>>> The following PRs have been backported so far:
>>>
>>> 2399
>>> 2503
>>> 2500
>>> 2498
>>> 2490
>>> 2491
>>> 2511
>>> 2294
>>> 2554
>>> 2561
>>> 2546
>>> 2526
>>> 2591
>>> 2582
>>> 2574
>>> 2638
>>> 2656
>>> 2663
>>> 2668
>>> 2662
>>> 2686
>>> 2685
>>> 2713
>>> 2717
>>> 2544
>>> 2749
>>> 2738
>>> 2769
>>> 2773
>>> 2778
>>> 2757
>>> 2783
>>> 2796
>>> 2799
>>> 2816
>>> 2830
>>> 2849
>>> 2859
>>> 2861
>>> 2863
>>> 2852
>>> 2864
>>> 2926
>>> 2924
>>> 2901
>>>
>>> If there are any others you think should be applied for 0.13.2, or if
>>> any of those shouldn't be included, let me know.
>>> In general, these are bugfixes that are either small or important.  No
>>> new features or APIs, etc.
>>>
>>> This is currently reflected in the 0.13.x branch<https://github.com/ipython/ipython/tree/0.13.x>
>>> .
>>>
>>> -MinRK
>>>
>>> _______________________________________________
>>> IPython-dev mailing list
>>> IPython-dev at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>
>>>
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>
>>
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>
>>
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20130314/2bd442e4/attachment.html>