Wes McKinney, 26.01.2012 18:56:
> Just wanted to bring this issue to your guys' attention in case you
> knew what was responsible for this:
>
> https://github.com/ipython/ipython/issues/1317#issuecomment-3652550
>
> I traced down the problem (with git bisect) to a seemingly innocuous
> commit ref
Vitja Makarov, 26.01.2012 21:19:
> 2012/1/27 Stefan Behnel:
>> Robert Bradshaw, 21.01.2012 23:09:
>>> On Sat, Jan 21, 2012 at 10:50 AM, Stefan Behnel wrote:
I did some callgrind profiling on Cython's generators and was surprised to
find that AddTraceback() represents a serious performance
On Thu, Jan 26, 2012 at 11:21 AM, mark florisson
wrote:
> Apologies, it was indeed a rather vague comment. I had some issues
No worries.
> with pasting unicode characters a few years back that would get
> incorrect codepoints in ipython but not regular python, but I'm afraid
We had a long and d
2012/1/27 Stefan Behnel :
> Robert Bradshaw, 21.01.2012 23:09:
>> On Sat, Jan 21, 2012 at 10:50 AM, Stefan Behnel wrote:
>>> I did some callgrind profiling on Cython's generators and was surprised to
>>> find that AddTraceback() represents a serious performance penalty for short
>>> running generat
On 26 January 2012 19:40, Wes McKinney wrote:
> On Thu, Jan 26, 2012 at 2:21 PM, mark florisson
> wrote:
>> On 26 January 2012 19:10, Fernando Perez wrote:
>>> On Thu, Jan 26, 2012 at 10:37 AM, mark florisson
>>> wrote:
On a side note, ipython is not something I usually trust to test
Robert Bradshaw, 21.01.2012 23:09:
> On Sat, Jan 21, 2012 at 10:50 AM, Stefan Behnel wrote:
>> I did some callgrind profiling on Cython's generators and was surprised to
>> find that AddTraceback() represents a serious performance penalty for short
>> running generators.
>>
>> I profiled a compiled
On Thu, Jan 26, 2012 at 2:21 PM, mark florisson
wrote:
> On 26 January 2012 19:10, Fernando Perez wrote:
>> On Thu, Jan 26, 2012 at 10:37 AM, mark florisson
>> wrote:
>>> On a side note, ipython is not something I usually trust to test
>>> things out, as it gets things wrong sometimes which can
On 26 January 2012 19:27, Stefan Behnel wrote:
> mark florisson, 26.01.2012 20:15:
>> On 26 January 2012 18:53, Stefan Behnel wrote:
>>> mark florisson, 26.01.2012 16:20:
I think this problem can trivially be solved by creating a ProxyNode
that should never be replaced by any transform,
mark florisson, 26.01.2012 20:15:
> On 26 January 2012 18:53, Stefan Behnel wrote:
>> mark florisson, 26.01.2012 16:20:
>>> I think this problem can trivially be solved by creating a ProxyNode
>>> that should never be replaced by any transform, but it's argument may
>>> be replaced. So you wrap sel
On 26 January 2012 19:10, Fernando Perez wrote:
> On Thu, Jan 26, 2012 at 10:37 AM, mark florisson
> wrote:
>> On a side note, ipython is not something I usually trust to test
>> things out, as it gets things wrong sometimes which can seriously make
>> you question your own sanity.
>
> I should n
On 26 January 2012 18:53, Stefan Behnel wrote:
> mark florisson, 26.01.2012 16:20:
>> On 26 January 2012 06:39, Vitja Makarov wrote:
>>> 2012/1/25 Stefan Behnel:
Back to the old idea of separating the type analysis into 1) a basic
typing, inference and entry creation step and 2) a proper
On 26 January 2012 18:51, Vitja Makarov wrote:
> 2012/1/26 mark florisson :
>> On 26 January 2012 06:39, Vitja Makarov wrote:
>>> 2012/1/25 Stefan Behnel :
mark florisson, 24.01.2012 14:53:
> On 24 January 2012 11:37, Konrad Hinsen wrote:
>> Compiling the attached Cython file produce
On Thu, Jan 26, 2012 at 10:37 AM, mark florisson
wrote:
> On a side note, ipython is not something I usually trust to test
> things out, as it gets things wrong sometimes which can seriously make
> you question your own sanity.
I should note that we'd love to know specifics about problems that
se
mark florisson, 26.01.2012 16:20:
> On 26 January 2012 06:39, Vitja Makarov wrote:
>> 2012/1/25 Stefan Behnel:
>>> Back to the old idea of separating the type analysis into 1) a basic
>>> typing, inference and entry creation step and 2) a proper type analysis,
>>> coercion, etc. step.
>>>
>>
>> Yea
2012/1/26 mark florisson :
> On 26 January 2012 06:39, Vitja Makarov wrote:
>> 2012/1/25 Stefan Behnel :
>>> mark florisson, 24.01.2012 14:53:
On 24 January 2012 11:37, Konrad Hinsen wrote:
> Compiling the attached Cython file produced the attached C file which
> has errors in lines 5
On 26 January 2012 18:36, mark florisson wrote:
> On 26 January 2012 17:56, Wes McKinney wrote:
>> Just wanted to bring this issue to your guys' attention in case you
>> knew what was responsible for this:
>>
>> https://github.com/ipython/ipython/issues/1317#issuecomment-3652550
>>
>> I traced do
On 26 January 2012 17:56, Wes McKinney wrote:
> Just wanted to bring this issue to your guys' attention in case you
> knew what was responsible for this:
>
> https://github.com/ipython/ipython/issues/1317#issuecomment-3652550
>
> I traced down the problem (with git bisect) to a seemingly innocuous
Just wanted to bring this issue to your guys' attention in case you
knew what was responsible for this:
https://github.com/ipython/ipython/issues/1317#issuecomment-3652550
I traced down the problem (with git bisect) to a seemingly innocuous
commit referenced in that GitHub thread. The issue seeme
On 26 January 2012 06:39, Vitja Makarov wrote:
> 2012/1/25 Stefan Behnel :
>> mark florisson, 24.01.2012 14:53:
>>> On 24 January 2012 11:37, Konrad Hinsen wrote:
Compiling the attached Cython file produced the attached C file which
has errors in lines 532-534:
__pyx_v_self->x
19 matches
Mail list logo
