headers
mark florisson | 24 Aug 2012 20:40
Picon
Gravatar

[Cython] array expressions

Hey,

Here a pull request for element-wise array expressions for Cython:
https://github.com/cython/cython/pull/144
It includes the IndexNode refactoring branch as well.

This has been the work this last summer for the gsoc, with great
supervision from Dag, who helped steer the project in a great
direction to make it reusable (it's partially included in Numba and
will likely be in Theano in the future, hopefully others as well). I
also wrote a thesis for my master's, which can be found here
https://github.com/markflorisson88/minivect/tree/master/thesis, which
can shed
some light on some parts of the design and performance aspects.
Performance graphs can also be found here:
https://github.com/markflorisson88/minivect/tree/master/bench/graphs

So anyway, how would you prefer dealing with the minivect submodule?
We could include it verbatim, with any modifications made to minivect
directly, since we'd have separate git histories. We could
alternatively make it an optional submodule which is only required
when actually using array expressions. I like the latter, but anything
is fine with me really.

Mark
Permalink | Reply |
headers
Dag Sverre Seljebotn | 27 Aug 2012 11:53
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 08/24/2012 08:40 PM, mark florisson wrote:
> Hey,
>
> Here a pull request for element-wise array expressions for Cython:
> https://github.com/cython/cython/pull/144
> It includes the IndexNode refactoring branch as well.
>
> This has been the work this last summer for the gsoc, with great
> supervision from Dag, who helped steer the project in a great
> direction to make it reusable (it's partially included in Numba and
> will likely be in Theano in the future, hopefully others as well). I
> also wrote a thesis for my master's, which can be found here
> https://github.com/markflorisson88/minivect/tree/master/thesis, which
> can shed
> some light on some parts of the design and performance aspects.
> Performance graphs can also be found here:
> https://github.com/markflorisson88/minivect/tree/master/bench/graphs
>
> So anyway, how would you prefer dealing with the minivect submodule?
> We could include it verbatim, with any modifications made to minivect
> directly, since we'd have separate git histories. We could
> alternatively make it an optional submodule which is only required
> when actually using array expressions. I like the latter, but anything
> is fine with me really.

I think I support using a git submodule for now. Not sure about making 
it optional (which I assume would make array expression testcases not 
run if it minivect is not present so that there's no test failures); we 
want to make sure we are forced to do releases and testing right and 
include it, and if it is only required to compile code that uses
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 27 Aug 2012 11:55
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 08/27/2012 11:53 AM, Dag Sverre Seljebotn wrote:
> On 08/24/2012 08:40 PM, mark florisson wrote:
>> Hey,
>>
>> Here a pull request for element-wise array expressions for Cython:
>> https://github.com/cython/cython/pull/144
>> It includes the IndexNode refactoring branch as well.
>>
>> This has been the work this last summer for the gsoc, with great
>> supervision from Dag, who helped steer the project in a great
>> direction to make it reusable (it's partially included in Numba and
>> will likely be in Theano in the future, hopefully others as well). I
>> also wrote a thesis for my master's, which can be found here
>> https://github.com/markflorisson88/minivect/tree/master/thesis, which
>> can shed
>> some light on some parts of the design and performance aspects.
>> Performance graphs can also be found here:
>> https://github.com/markflorisson88/minivect/tree/master/bench/graphs
>>
>> So anyway, how would you prefer dealing with the minivect submodule?
>> We could include it verbatim, with any modifications made to minivect
>> directly, since we'd have separate git histories. We could
>> alternatively make it an optional submodule which is only required
>> when actually using array expressions. I like the latter, but anything
>> is fine with me really.
>
> I think I support using a git submodule for now. Not sure about making
> it optional (which I assume would make array expression testcases not
> run if it minivect is not present so that there's no test failures); we
> want to make sure we are forced to do releases and testing right and
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 27 Aug 2012 13:06
Picon
Favicon

Re: [Cython] array expressions

Dag Sverre Seljebotn, 27.08.2012 11:55:
> On 08/27/2012 11:53 AM, Dag Sverre Seljebotn wrote:
>> On 08/24/2012 08:40 PM, mark florisson wrote:
>>> Here a pull request for element-wise array expressions for Cython:
>>> https://github.com/cython/cython/pull/144
>>> It includes the IndexNode refactoring branch as well.
>>>
>>> This has been the work this last summer for the gsoc, with great
>>> supervision from Dag, who helped steer the project in a great
>>> direction to make it reusable (it's partially included in Numba and
>>> will likely be in Theano in the future, hopefully others as well). I
>>> also wrote a thesis for my master's, which can be found here
>>> https://github.com/markflorisson88/minivect/tree/master/thesis, which
>>> can shed
>>> some light on some parts of the design and performance aspects.
>>> Performance graphs can also be found here:
>>> https://github.com/markflorisson88/minivect/tree/master/bench/graphs
>>>
>>> So anyway, how would you prefer dealing with the minivect submodule?
>>> We could include it verbatim, with any modifications made to minivect
>>> directly, since we'd have separate git histories. We could
>>> alternatively make it an optional submodule which is only required
>>> when actually using array expressions. I like the latter, but anything
>>> is fine with me really.
>>
>> I think I support using a git submodule for now. Not sure about making
>> it optional (which I assume would make array expression testcases not
>> run if it minivect is not present so that there's no test failures); we
>> want to make sure we are forced to do releases and testing right and
>> include it, and if it is only required to compile code that uses
(Continue reading)

Permalink | Reply |
headers
mark florisson | 27 Aug 2012 13:13
Picon
Gravatar

Re: [Cython] array expressions

On 27 August 2012 12:06, Stefan Behnel <stefan_ml@...> wrote:
> Dag Sverre Seljebotn, 27.08.2012 11:55:
>> On 08/27/2012 11:53 AM, Dag Sverre Seljebotn wrote:
>>> On 08/24/2012 08:40 PM, mark florisson wrote:
>>>> Here a pull request for element-wise array expressions for Cython:
>>>> https://github.com/cython/cython/pull/144
>>>> It includes the IndexNode refactoring branch as well.
>>>>
>>>> This has been the work this last summer for the gsoc, with great
>>>> supervision from Dag, who helped steer the project in a great
>>>> direction to make it reusable (it's partially included in Numba and
>>>> will likely be in Theano in the future, hopefully others as well). I
>>>> also wrote a thesis for my master's, which can be found here
>>>> https://github.com/markflorisson88/minivect/tree/master/thesis, which
>>>> can shed
>>>> some light on some parts of the design and performance aspects.
>>>> Performance graphs can also be found here:
>>>> https://github.com/markflorisson88/minivect/tree/master/bench/graphs
>>>>
>>>> So anyway, how would you prefer dealing with the minivect submodule?
>>>> We could include it verbatim, with any modifications made to minivect
>>>> directly, since we'd have separate git histories. We could
>>>> alternatively make it an optional submodule which is only required
>>>> when actually using array expressions. I like the latter, but anything
>>>> is fine with me really.
>>>
>>> I think I support using a git submodule for now. Not sure about making
>>> it optional (which I assume would make array expression testcases not
>>> run if it minivect is not present so that there's no test failures); we
>>> want to make sure we are forced to do releases and testing right and
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 27 Aug 2012 13:40
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 27.08.2012 13:13:
> On 27 August 2012 12:06, Stefan Behnel wrote:
>> My experience with lxml tells me that it's often better to keep things
>> separate but integrated, instead of shipping them in a big box. As long as
>> it doesn't hurt too much to have separate tools, we should keep it that
>> way. Those who prefer everything in a big box can use distributions like
>> Sage, or use apt.
>>
>> As for versioning, you can set dependency version ranges in distutils (and
>> friends) which are honoured by install tools like pip. That keeps the
>> installation fully automatic (and definitely not "a lot more pain"). That
>> being said, the best way to handle this is to build a well defined
>> interface between the two components and to keep that alive for a while.
>>
>> For Jenkins, we'd set up separate jobs that build the dependencies and then
>> install them from there before running the integration tests. We could even
>> have dedicated integration test jobs that only run the tests that involve
>> the dependency (and potentially more than one version of the dependency).
> 
> Oh great, that works for me as well. I thought Cython's take was to
> avoid dependencies by shipping everything (like Plex and Tempita).

Those are core dependencies. Plex is actually modified IIRC, and even
compiled. Tempita was specifically chosen because it's so small and can be
shipped.

> I'll make minivect distributable, then.

I think the difference here is that it's an optional dependency. It makes
sense independently as well when used with other tools. And from my distant
(Continue reading)

Permalink | Reply |
headers
mark florisson | 27 Aug 2012 13:52
Picon
Gravatar

Re: [Cython] array expressions

On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
> mark florisson, 27.08.2012 13:13:
>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>> My experience with lxml tells me that it's often better to keep things
>>> separate but integrated, instead of shipping them in a big box. As long as
>>> it doesn't hurt too much to have separate tools, we should keep it that
>>> way. Those who prefer everything in a big box can use distributions like
>>> Sage, or use apt.
>>>
>>> As for versioning, you can set dependency version ranges in distutils (and
>>> friends) which are honoured by install tools like pip. That keeps the
>>> installation fully automatic (and definitely not "a lot more pain"). That
>>> being said, the best way to handle this is to build a well defined
>>> interface between the two components and to keep that alive for a while.
>>>
>>> For Jenkins, we'd set up separate jobs that build the dependencies and then
>>> install them from there before running the integration tests. We could even
>>> have dedicated integration test jobs that only run the tests that involve
>>> the dependency (and potentially more than one version of the dependency).
>>
>> Oh great, that works for me as well. I thought Cython's take was to
>> avoid dependencies by shipping everything (like Plex and Tempita).
>
> Those are core dependencies. Plex is actually modified IIRC, and even
> compiled. Tempita was specifically chosen because it's so small and can be
> shipped.
>
>
>> I'll make minivect distributable, then.
>
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 27 Aug 2012 14:05
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 27.08.2012 13:52:
> On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
>> mark florisson, 27.08.2012 13:13:
>>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>>> My experience with lxml tells me that it's often better to keep things
>>>> separate but integrated, instead of shipping them in a big box. As long as
>>>> it doesn't hurt too much to have separate tools, we should keep it that
>>>> way. Those who prefer everything in a big box can use distributions like
>>>> Sage, or use apt.
>>>>
>>>> As for versioning, you can set dependency version ranges in distutils (and
>>>> friends) which are honoured by install tools like pip. That keeps the
>>>> installation fully automatic (and definitely not "a lot more pain"). That
>>>> being said, the best way to handle this is to build a well defined
>>>> interface between the two components and to keep that alive for a while.
>>>>
>>>> For Jenkins, we'd set up separate jobs that build the dependencies and then
>>>> install them from there before running the integration tests. We could even
>>>> have dedicated integration test jobs that only run the tests that involve
>>>> the dependency (and potentially more than one version of the dependency).
>>>
>>> Oh great, that works for me as well. I thought Cython's take was to
>>> avoid dependencies by shipping everything (like Plex and Tempita).
>>
>> Those are core dependencies. Plex is actually modified IIRC, and even
>> compiled. Tempita was specifically chosen because it's so small and can be
>> shipped.
>>
>>
>>> I'll make minivect distributable, then.
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 27 Aug 2012 14:45
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 08/27/2012 02:05 PM, Stefan Behnel wrote:
> mark florisson, 27.08.2012 13:52:
>> On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
>>> mark florisson, 27.08.2012 13:13:
>>>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>>>> My experience with lxml tells me that it's often better to keep things
>>>>> separate but integrated, instead of shipping them in a big box. As long as
>>>>> it doesn't hurt too much to have separate tools, we should keep it that
>>>>> way. Those who prefer everything in a big box can use distributions like
>>>>> Sage, or use apt.
>>>>>
>>>>> As for versioning, you can set dependency version ranges in distutils (and
>>>>> friends) which are honoured by install tools like pip. That keeps the
>>>>> installation fully automatic (and definitely not "a lot more pain"). That
>>>>> being said, the best way to handle this is to build a well defined
>>>>> interface between the two components and to keep that alive for a while.
>>>>>
>>>>> For Jenkins, we'd set up separate jobs that build the dependencies and then
>>>>> install them from there before running the integration tests. We could even
>>>>> have dedicated integration test jobs that only run the tests that involve
>>>>> the dependency (and potentially more than one version of the dependency).
>>>>
>>>> Oh great, that works for me as well. I thought Cython's take was to
>>>> avoid dependencies by shipping everything (like Plex and Tempita).
>>>
>>> Those are core dependencies. Plex is actually modified IIRC, and even
>>> compiled. Tempita was specifically chosen because it's so small and can be
>>> shipped.
>>>
>>>
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 27 Aug 2012 14:47
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 08/27/2012 02:45 PM, Dag Sverre Seljebotn wrote:
> On 08/27/2012 02:05 PM, Stefan Behnel wrote:
>> mark florisson, 27.08.2012 13:52:
>>> On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
>>>> mark florisson, 27.08.2012 13:13:
>>>>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>>>>> My experience with lxml tells me that it's often better to keep
>>>>>> things
>>>>>> separate but integrated, instead of shipping them in a big box. As
>>>>>> long as
>>>>>> it doesn't hurt too much to have separate tools, we should keep it
>>>>>> that
>>>>>> way. Those who prefer everything in a big box can use
>>>>>> distributions like
>>>>>> Sage, or use apt.
>>>>>>
>>>>>> As for versioning, you can set dependency version ranges in
>>>>>> distutils (and
>>>>>> friends) which are honoured by install tools like pip. That keeps the
>>>>>> installation fully automatic (and definitely not "a lot more
>>>>>> pain"). That
>>>>>> being said, the best way to handle this is to build a well defined
>>>>>> interface between the two components and to keep that alive for a
>>>>>> while.
>>>>>>
>>>>>> For Jenkins, we'd set up separate jobs that build the dependencies
>>>>>> and then
>>>>>> install them from there before running the integration tests. We
>>>>>> could even
>>>>>> have dedicated integration test jobs that only run the tests that
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 27 Aug 2012 14:53
Picon
Favicon

Re: [Cython] array expressions

Dag Sverre Seljebotn, 27.08.2012 14:47:
> On 08/27/2012 02:45 PM, Dag Sverre Seljebotn wrote:
>> On 08/27/2012 02:05 PM, Stefan Behnel wrote:
>>> mark florisson, 27.08.2012 13:52:
>>>> On 27 August 2012 12:40, Stefan Behnel wrote:
>>>>> The code tree looks a bit disorganised currently, with a lot of
>>>>> modules at
>>>>> the top level. I guess that's what you meant when you said "make it
>>>>> distributable".
>>>>
>>>> Indeed, the idea was that it would be included verbatim in
>>>> projects/used as a submodule, since it'd be small enough to include
>>>> and would always be stable and integrated into the main project. That
>>>> basically means the entire thing would be the package. It'd be kind of
>>>> nice to allow it both ways, i.e. install as a package, and make it
>>>> convenient as a submodule. I think that can be managed.
>>>
>>> I'd just move it into a package anyway and let projects that want to
>>> use it
>>> as a git submodule move it to an appropriate place during installation by
>>> appropriately configuring their project specific distutils setup.
>>>
>>>> E.g. I can see situations where you need to fix a little bug, or make
>>>> a small change where you don't really want (to wait for) a new release
>>>> of minivect, but you do want that exact commit for the release of the
>>>> main project.
>>>
>>> Doesn't that apply to more or less all code out there?
>>
>> Most package dependencies are *a lot* more loosely coupled that Cython
(Continue reading)

Permalink | Reply |
headers
Robert Bradshaw | 27 Aug 2012 20:07
Picon

Re: [Cython] array expressions

On Mon, Aug 27, 2012 at 5:47 AM, Dag Sverre Seljebotn
<d.s.seljebotn@...> wrote:
> On 08/27/2012 02:45 PM, Dag Sverre Seljebotn wrote:
>>
>> On 08/27/2012 02:05 PM, Stefan Behnel wrote:
>>>
>>> mark florisson, 27.08.2012 13:52:
>>>>
>>>> On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
>>>>>
>>>>> mark florisson, 27.08.2012 13:13:
>>>>>>
>>>>>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>>>>>>
>>>>>>> My experience with lxml tells me that it's often better to keep
>>>>>>> things
>>>>>>> separate but integrated, instead of shipping them in a big box. As
>>>>>>> long as
>>>>>>> it doesn't hurt too much to have separate tools, we should keep it
>>>>>>> that
>>>>>>> way. Those who prefer everything in a big box can use
>>>>>>> distributions like
>>>>>>> Sage, or use apt.
>>>>>>>
>>>>>>> As for versioning, you can set dependency version ranges in
>>>>>>> distutils (and
>>>>>>> friends) which are honoured by install tools like pip. That keeps the
>>>>>>> installation fully automatic (and definitely not "a lot more
>>>>>>> pain"). That
>>>>>>> being said, the best way to handle this is to build a well defined
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 27 Aug 2012 20:16
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 08/27/2012 08:07 PM, Robert Bradshaw wrote:
> On Mon, Aug 27, 2012 at 5:47 AM, Dag Sverre Seljebotn
> <d.s.seljebotn@...> wrote:
>> On 08/27/2012 02:45 PM, Dag Sverre Seljebotn wrote:
>>>
>>> On 08/27/2012 02:05 PM, Stefan Behnel wrote:
>>>>
>>>> mark florisson, 27.08.2012 13:52:
>>>>>
>>>>> On 27 August 2012 12:40, Stefan Behnel <stefan_ml@...> wrote:
>>>>>>
>>>>>> mark florisson, 27.08.2012 13:13:
>>>>>>>
>>>>>>> On 27 August 2012 12:06, Stefan Behnel wrote:
>>>>>>>>
>>>>>>>> My experience with lxml tells me that it's often better to keep
>>>>>>>> things
>>>>>>>> separate but integrated, instead of shipping them in a big box. As
>>>>>>>> long as
>>>>>>>> it doesn't hurt too much to have separate tools, we should keep it
>>>>>>>> that
>>>>>>>> way. Those who prefer everything in a big box can use
>>>>>>>> distributions like
>>>>>>>> Sage, or use apt.
>>>>>>>>
>>>>>>>> As for versioning, you can set dependency version ranges in
>>>>>>>> distutils (and
>>>>>>>> friends) which are honoured by install tools like pip. That keeps the
>>>>>>>> installation fully automatic (and definitely not "a lot more
>>>>>>>> pain"). That
(Continue reading)

Permalink | Reply |
headers
Sturla Molden | 30 Aug 2012 17:42
Picon
Gravatar

Re: [Cython] array expressions

While I have not tried this yet, array expressions in Cython might be 
the final nails in the coffin for Fortran 90 as far as I am concerned.
Great work!

:-)

Sturla

On 24.08.2012 20:40, mark florisson wrote:
> Hey,
>
> Here a pull request for element-wise array expressions for Cython:
> https://github.com/cython/cython/pull/144
> It includes the IndexNode refactoring branch as well.
>
> This has been the work this last summer for the gsoc, with great
> supervision from Dag, who helped steer the project in a great
> direction to make it reusable (it's partially included in Numba and
> will likely be in Theano in the future, hopefully others as well). I
> also wrote a thesis for my master's, which can be found here
> https://github.com/markflorisson88/minivect/tree/master/thesis, which
> can shed
> some light on some parts of the design and performance aspects.
> Performance graphs can also be found here:
> https://github.com/markflorisson88/minivect/tree/master/bench/graphs
>
> So anyway, how would you prefer dealing with the minivect submodule?
> We could include it verbatim, with any modifications made to minivect
> directly, since we'd have separate git histories. We could
> alternatively make it an optional submodule which is only required
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 12 Oct 2012 09:36
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 24.08.2012 20:40:
> Here a pull request for element-wise array expressions for Cython:
> https://github.com/cython/cython/pull/144

Mark, any news on this? I'd like to see a version merged before the master
branch starts diverging all too far - it already requires a bit of adaptation.

Did you manage to split off a separate minivect package?

Stefan
Permalink | Reply |
headers
mark florisson | 12 Oct 2012 12:14
Picon
Gravatar

Re: [Cython] array expressions

On 12 October 2012 08:36, Stefan Behnel <stefan_ml@...> wrote:
> mark florisson, 24.08.2012 20:40:
>> Here a pull request for element-wise array expressions for Cython:
>> https://github.com/cython/cython/pull/144
>
> Mark, any news on this? I'd like to see a version merged before the master
> branch starts diverging all too far - it already requires a bit of adaptation.
>
> Did you manage to split off a separate minivect package?
>
> Stefan
>
> _______________________________________________
> cython-devel mailing list
> cython-devel@...
> http://mail.python.org/mailman/listinfo/cython-devel

I have some time this weekend, I'll see if I can finish it then. Shall
I make a new PR or merge it directly?
Permalink | Reply |
headers
Stefan Behnel | 12 Oct 2012 12:28
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 12.10.2012 12:14:
> On 12 October 2012 08:36, Stefan Behnel wrote:
>> mark florisson, 24.08.2012 20:40:
>>> Here a pull request for element-wise array expressions for Cython:
>>> https://github.com/cython/cython/pull/144
>>
>> Mark, any news on this? I'd like to see a version merged before the master
>> branch starts diverging all too far - it already requires a bit of adaptation.
>>
>> Did you manage to split off a separate minivect package?
> 
> I have some time this weekend, I'll see if I can finish it then. Shall
> I make a new PR or merge it directly?

As I said, I won't review it anyway, so it's no difference for me. But
given that your original pull request didn't receive any comments, I doubt
that making a new one would serve a major purpose.

Stefan
Permalink | Reply |
headers
Robert Bradshaw | 12 Oct 2012 17:50
Picon

Re: [Cython] array expressions

On Fri, Oct 12, 2012 at 3:14 AM, mark florisson
<markflorisson88@...> wrote:
> On 12 October 2012 08:36, Stefan Behnel <stefan_ml@...> wrote:
>> mark florisson, 24.08.2012 20:40:
>>> Here a pull request for element-wise array expressions for Cython:
>>> https://github.com/cython/cython/pull/144
>>
>> Mark, any news on this? I'd like to see a version merged before the master
>> branch starts diverging all too far - it already requires a bit of adaptation.
>>
>> Did you manage to split off a separate minivect package?

I'm assuming this has already been looked at, at least to some level,
by Dag, but I'll try to take a brief pass at it too (probably more the
interface than the implementation).

I don't see a reason for a new pull request.

- Robert
Permalink | Reply |
headers
Dag Sverre Seljebotn | 12 Oct 2012 21:01
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson
> <markflorisson88@...> wrote:
>> On 12 October 2012 08:36, Stefan Behnel <stefan_ml@...> wrote:
>>> mark florisson, 24.08.2012 20:40:
>>>> Here a pull request for element-wise array expressions for Cython:
>>>> https://github.com/cython/cython/pull/144
>>>
>>> Mark, any news on this? I'd like to see a version merged before the master
>>> branch starts diverging all too far - it already requires a bit of adaptation.
>>>
>>> Did you manage to split off a separate minivect package?
>
> I'm assuming this has already been looked at, at least to some level,
> by Dag, but I'll try to take a brief pass at it too (probably more the
> interface than the implementation).

Thanks for doing that, it'd be great to get this in (but myself I've got 
nothing to spare). I'll admit I was mostly focused on the generated code 
and the algorithms in minivect rather than the integration with Cython.

Dag Sverre

>
> I don't see a reason for a new pull request.
>
> - Robert
> _______________________________________________
> cython-devel mailing list
> cython-devel@...
(Continue reading)

Permalink | Reply |
headers
mark florisson | 13 Oct 2012 20:30
Picon
Gravatar

Re: [Cython] array expressions

On 12 October 2012 20:01, Dag Sverre Seljebotn
<d.s.seljebotn@...> wrote:
> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>
>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson
>> <markflorisson88@...> wrote:
>>>
>>> On 12 October 2012 08:36, Stefan Behnel <stefan_ml@...> wrote:
>>>>
>>>> mark florisson, 24.08.2012 20:40:
>>>>>
>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>> https://github.com/cython/cython/pull/144
>>>>
>>>>
>>>> Mark, any news on this? I'd like to see a version merged before the
>>>> master
>>>> branch starts diverging all too far - it already requires a bit of
>>>> adaptation.
>>>>
>>>> Did you manage to split off a separate minivect package?
>>
>>
>> I'm assuming this has already been looked at, at least to some level,
>> by Dag, but I'll try to take a brief pass at it too (probably more the
>> interface than the implementation).
>
>
> Thanks for doing that, it'd be great to get this in (but myself I've got
> nothing to spare). I'll admit I was mostly focused on the generated code and
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 14 Oct 2012 08:18
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 13.10.2012 20:30:
> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>> mark florisson, 24.08.2012 20:40:
>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>> https://github.com/cython/cython/pull/144
>>>>>
>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>> the master branch starts diverging all too far - it already
>>>>> requires a bit of adaptation.
>>>>> Did you manage to split off a separate minivect package?
>>>
>>> I'm assuming this has already been looked at, at least to some level,
>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>> interface than the implementation).
>>
>> Thanks for doing that, it'd be great to get this in (but myself I've got
>> nothing to spare). I'll admit I was mostly focused on the generated code and
>> the algorithms in minivect rather than the integration with Cython.
>>
>>> I don't see a reason for a new pull request.
> 
> Great. As for the packaging, I'm creating a distribution branch, and a
> subtree branch. Newer versions of git have a 'subtree' command
> (previously https://github.com/apenwarr/git-subtree), which allows one
> to split of, merge, push, and pull subdirectories.
> 
> This means when users pull the master project, they get the
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 14 Oct 2012 10:18
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/14/2012 08:18 AM, Stefan Behnel wrote:
> mark florisson, 13.10.2012 20:30:
>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>
>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>> the master branch starts diverging all too far - it already
>>>>>> requires a bit of adaptation.
>>>>>> Did you manage to split off a separate minivect package?
>>>>
>>>> I'm assuming this has already been looked at, at least to some level,
>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>> interface than the implementation).
>>>
>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>> nothing to spare). I'll admit I was mostly focused on the generated code and
>>> the algorithms in minivect rather than the integration with Cython.
>>>
>>>> I don't see a reason for a new pull request.
>>
>> Great. As for the packaging, I'm creating a distribution branch, and a
>> subtree branch. Newer versions of git have a 'subtree' command
>> (previously https://github.com/apenwarr/git-subtree), which allows one
>> to split of, merge, push, and pull subdirectories.
>>
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 14 Oct 2012 10:23
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/14/2012 10:18 AM, Dag Sverre Seljebotn wrote:
> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>> mark florisson, 13.10.2012 20:30:
>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>
>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>> the master branch starts diverging all too far - it already
>>>>>>> requires a bit of adaptation.
>>>>>>> Did you manage to split off a separate minivect package?
>>>>>
>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>> interface than the implementation).
>>>>
>>>> Thanks for doing that, it'd be great to get this in (but myself I've
>>>> got
>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>> code and
>>>> the algorithms in minivect rather than the integration with Cython.
>>>>
>>>>> I don't see a reason for a new pull request.
>>>
>>> Great. As for the packaging, I'm creating a distribution branch, and a
>>> subtree branch. Newer versions of git have a 'subtree' command
(Continue reading)

Permalink | Reply |
headers
mark florisson | 14 Oct 2012 13:59
Picon
Gravatar

Re: [Cython] array expressions

On 14 October 2012 09:23, Dag Sverre Seljebotn
<d.s.seljebotn@...> wrote:
> On 10/14/2012 10:18 AM, Dag Sverre Seljebotn wrote:
>>
>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>>
>>> mark florisson, 13.10.2012 20:30:
>>>>
>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>>
>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>>
>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>>
>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>>
>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>>
>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>
>>>>>>>>
>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>> requires a bit of adaptation.
>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>
>>>>>>
>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 14 Oct 2012 10:32
Picon
Favicon

Re: [Cython] array expressions

Dag Sverre Seljebotn, 14.10.2012 10:18:
> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>> mark florisson, 13.10.2012 20:30:
>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>
>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>> the master branch starts diverging all too far - it already
>>>>>>> requires a bit of adaptation.
>>>>>>> Did you manage to split off a separate minivect package?
>>>>>
>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>> interface than the implementation).
>>>>
>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>> code and
>>>> the algorithms in minivect rather than the integration with Cython.
>>>>
>>>>> I don't see a reason for a new pull request.
>>>
>>> Great. As for the packaging, I'm creating a distribution branch, and a
>>> subtree branch. Newer versions of git have a 'subtree' command
>>> (previously https://github.com/apenwarr/git-subtree), which allows one
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 14 Oct 2012 11:03
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/14/2012 10:32 AM, Stefan Behnel wrote:
> Dag Sverre Seljebotn, 14.10.2012 10:18:
>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>> mark florisson, 13.10.2012 20:30:
>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>
>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>> requires a bit of adaptation.
>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>
>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>>> interface than the implementation).
>>>>>
>>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>>> code and
>>>>> the algorithms in minivect rather than the integration with Cython.
>>>>>
>>>>>> I don't see a reason for a new pull request.
>>>>
>>>> Great. As for the packaging, I'm creating a distribution branch, and a
>>>> subtree branch. Newer versions of git have a 'subtree' command
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 14 Oct 2012 12:23
Picon
Favicon

Re: [Cython] array expressions

Dag Sverre Seljebotn, 14.10.2012 11:03:
> On 10/14/2012 10:32 AM, Stefan Behnel wrote:
>> Dag Sverre Seljebotn, 14.10.2012 10:18:
>>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>>> mark florisson, 13.10.2012 20:30:
>>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>>
>>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>>> requires a bit of adaptation.
>>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>>
>>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>>>> interface than the implementation).
>>>>>>
>>>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>>>> code and
>>>>>> the algorithms in minivect rather than the integration with Cython.
>>>>>>
>>>>>>> I don't see a reason for a new pull request.
>>>>>
>>>>> Great. As for the packaging, I'm creating a distribution branch, and a
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 14 Oct 2012 13:24
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/14/2012 12:23 PM, Stefan Behnel wrote:
> Dag Sverre Seljebotn, 14.10.2012 11:03:
>> On 10/14/2012 10:32 AM, Stefan Behnel wrote:
>>> Dag Sverre Seljebotn, 14.10.2012 10:18:
>>>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>>>> mark florisson, 13.10.2012 20:30:
>>>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>>>
>>>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>>>> requires a bit of adaptation.
>>>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>>>
>>>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>>>>> interface than the implementation).
>>>>>>>
>>>>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>>>>> code and
>>>>>>> the algorithms in minivect rather than the integration with Cython.
>>>>>>>
>>>>>>>> I don't see a reason for a new pull request.
>>>>>>
(Continue reading)

Permalink | Reply |
headers
mark florisson | 14 Oct 2012 14:02
Picon
Gravatar

Re: [Cython] array expressions

On 14 October 2012 11:23, Stefan Behnel <stefan_ml@...> wrote:
> Dag Sverre Seljebotn, 14.10.2012 11:03:
>> On 10/14/2012 10:32 AM, Stefan Behnel wrote:
>>> Dag Sverre Seljebotn, 14.10.2012 10:18:
>>>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>>>> mark florisson, 13.10.2012 20:30:
>>>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>>>
>>>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>>>> requires a bit of adaptation.
>>>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>>>
>>>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>>>>> interface than the implementation).
>>>>>>>
>>>>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>>>>> code and
>>>>>>> the algorithms in minivect rather than the integration with Cython.
>>>>>>>
>>>>>>>> I don't see a reason for a new pull request.
>>>>>>
(Continue reading)

Permalink | Reply |
headers
mark florisson | 14 Oct 2012 13:59
Picon
Gravatar

Re: [Cython] array expressions

On 14 October 2012 09:32, Stefan Behnel <stefan_ml@...> wrote:
> Dag Sverre Seljebotn, 14.10.2012 10:18:
>> On 10/14/2012 08:18 AM, Stefan Behnel wrote:
>>> mark florisson, 13.10.2012 20:30:
>>>> On 12 October 2012 20:01, Dag Sverre Seljebotn wrote:
>>>>> On 10/12/2012 05:50 PM, Robert Bradshaw wrote:
>>>>>> On Fri, Oct 12, 2012 at 3:14 AM, mark florisson wrote:
>>>>>>> On 12 October 2012 08:36, Stefan Behnel wrote:
>>>>>>>> mark florisson, 24.08.2012 20:40:
>>>>>>>>> Here a pull request for element-wise array expressions for Cython:
>>>>>>>>> https://github.com/cython/cython/pull/144
>>>>>>>>
>>>>>>>> Mark, any news on this? I'd like to see a version merged before
>>>>>>>> the master branch starts diverging all too far - it already
>>>>>>>> requires a bit of adaptation.
>>>>>>>> Did you manage to split off a separate minivect package?
>>>>>>
>>>>>> I'm assuming this has already been looked at, at least to some level,
>>>>>> by Dag, but I'll try to take a brief pass at it too (probably more the
>>>>>> interface than the implementation).
>>>>>
>>>>> Thanks for doing that, it'd be great to get this in (but myself I've got
>>>>> nothing to spare). I'll admit I was mostly focused on the generated
>>>>> code and
>>>>> the algorithms in minivect rather than the integration with Cython.
>>>>>
>>>>>> I don't see a reason for a new pull request.
>>>>
>>>> Great. As for the packaging, I'm creating a distribution branch, and a
>>>> subtree branch. Newer versions of git have a 'subtree' command
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 14 Oct 2012 15:05
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 14.10.2012 13:59:
> The problem with minivect as a package is that it caters to different
> projects, which have different requirements. Cython and minivect are
> quite closely coupled, and any future change, or in the future any
> older version may not have the functionality Cython needs, it's not
> exactly a stable API at this point.

Ok, understood.

> For instance Numba needs python
> 2.7, whereas Cython needs to be compatible with python 2.4.
> 
> Before releasing minivect I'll verify every time that it doesn't break
> Cython, but I currently have no real promises for backwards or forward
> compatibility. And that is really because not all use cases have yet
> been anticipated, and some really require a change, as I've already
> seen with Numba.
> 
> We could list minivect as a dependency, which works for
> easy_install/pip users, but I just foresee numerous people running
> into problems that didn't install with pip, and I don't think an
> exclusion of a 300kb addition is worth any of that.

Fine. In that case, I'm for not making minivect a separate package at all
but including it directly and considering it a part of Cython (and Numba
etc.) until there is enough of an interface to make it a reusable separate
package, or at least to support a separate installation and independent
update. Basically, if you can't update it separately, there's no use in
installing it separately.
(Continue reading)

Permalink | Reply |
headers
mark florisson | 14 Oct 2012 15:13
Picon
Gravatar

Re: [Cython] array expressions

On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
> mark florisson, 14.10.2012 13:59:
>> The problem with minivect as a package is that it caters to different
>> projects, which have different requirements. Cython and minivect are
>> quite closely coupled, and any future change, or in the future any
>> older version may not have the functionality Cython needs, it's not
>> exactly a stable API at this point.
>
> Ok, understood.
>
>
>> For instance Numba needs python
>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>
>> Before releasing minivect I'll verify every time that it doesn't break
>> Cython, but I currently have no real promises for backwards or forward
>> compatibility. And that is really because not all use cases have yet
>> been anticipated, and some really require a change, as I've already
>> seen with Numba.
>>
>> We could list minivect as a dependency, which works for
>> easy_install/pip users, but I just foresee numerous people running
>> into problems that didn't install with pip, and I don't think an
>> exclusion of a 300kb addition is worth any of that.
>
> Fine. In that case, I'm for not making minivect a separate package at all
> but including it directly and considering it a part of Cython (and Numba
> etc.) until there is enough of an interface to make it a reusable separate
> package, or at least to support a separate installation and independent
> update. Basically, if you can't update it separately, there's no use in
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 14 Oct 2012 15:39
Picon
Favicon

Re: [Cython] array expressions

mark florisson, 14.10.2012 15:13:
> The hg support didn't work great for me (it was really slow),

It's fast enough for almost everything. What's really slow is when it has
to figure out how to match branches after head changes - I consider that a
pretty serious bug. But that happens quite rarely. And I usually push only
the master branch anyway, which is quick.

Obviously, hg is way faster against a mercurial server than against a git
server.

> can I ask why you're using it?

I prefer the interface of hg over that of git, that's the main reason.

In fact, whenever I have to touch git, it quickly lives up to its name:

http://dict.leo.org/ende?lang=en&search=igitt

Stefan
Permalink | Reply |
headers
Robert Bradshaw | 16 Oct 2012 19:48
Picon

Re: [Cython] array expressions

On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
<markflorisson88@...> wrote:
> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>> mark florisson, 14.10.2012 13:59:
>>> The problem with minivect as a package is that it caters to different
>>> projects, which have different requirements. Cython and minivect are
>>> quite closely coupled, and any future change, or in the future any
>>> older version may not have the functionality Cython needs, it's not
>>> exactly a stable API at this point.
>>
>> Ok, understood.
>>
>>
>>> For instance Numba needs python
>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>
>>> Before releasing minivect I'll verify every time that it doesn't break
>>> Cython, but I currently have no real promises for backwards or forward
>>> compatibility. And that is really because not all use cases have yet
>>> been anticipated, and some really require a change, as I've already
>>> seen with Numba.
>>>
>>> We could list minivect as a dependency, which works for
>>> easy_install/pip users, but I just foresee numerous people running
>>> into problems that didn't install with pip, and I don't think an
>>> exclusion of a 300kb addition is worth any of that.
>>
>> Fine. In that case, I'm for not making minivect a separate package at all
>> but including it directly and considering it a part of Cython (and Numba
>> etc.) until there is enough of an interface to make it a reusable separate
(Continue reading)

Permalink | Reply |
headers
mark florisson | 21 Oct 2012 14:39
Picon
Gravatar

Re: [Cython] array expressions

On 16 October 2012 18:48, Robert Bradshaw <robertwb@...> wrote:
> On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
> <markflorisson88@...> wrote:
>> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>>> mark florisson, 14.10.2012 13:59:
>>>> The problem with minivect as a package is that it caters to different
>>>> projects, which have different requirements. Cython and minivect are
>>>> quite closely coupled, and any future change, or in the future any
>>>> older version may not have the functionality Cython needs, it's not
>>>> exactly a stable API at this point.
>>>
>>> Ok, understood.
>>>
>>>
>>>> For instance Numba needs python
>>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>>
>>>> Before releasing minivect I'll verify every time that it doesn't break
>>>> Cython, but I currently have no real promises for backwards or forward
>>>> compatibility. And that is really because not all use cases have yet
>>>> been anticipated, and some really require a change, as I've already
>>>> seen with Numba.
>>>>
>>>> We could list minivect as a dependency, which works for
>>>> easy_install/pip users, but I just foresee numerous people running
>>>> into problems that didn't install with pip, and I don't think an
>>>> exclusion of a 300kb addition is worth any of that.
>>>
>>> Fine. In that case, I'm for not making minivect a separate package at all
>>> but including it directly and considering it a part of Cython (and Numba
(Continue reading)

Permalink | Reply |
headers
mark florisson | 21 Oct 2012 14:44
Picon
Gravatar

Re: [Cython] array expressions

On 21 October 2012 13:39, mark florisson
<markflorisson88@...> wrote:
> On 16 October 2012 18:48, Robert Bradshaw <robertwb@...> wrote:
>> On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
>> <markflorisson88@...> wrote:
>>> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>>>> mark florisson, 14.10.2012 13:59:
>>>>> The problem with minivect as a package is that it caters to different
>>>>> projects, which have different requirements. Cython and minivect are
>>>>> quite closely coupled, and any future change, or in the future any
>>>>> older version may not have the functionality Cython needs, it's not
>>>>> exactly a stable API at this point.
>>>>
>>>> Ok, understood.
>>>>
>>>>
>>>>> For instance Numba needs python
>>>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>>>
>>>>> Before releasing minivect I'll verify every time that it doesn't break
>>>>> Cython, but I currently have no real promises for backwards or forward
>>>>> compatibility. And that is really because not all use cases have yet
>>>>> been anticipated, and some really require a change, as I've already
>>>>> seen with Numba.
>>>>>
>>>>> We could list minivect as a dependency, which works for
>>>>> easy_install/pip users, but I just foresee numerous people running
>>>>> into problems that didn't install with pip, and I don't think an
>>>>> exclusion of a 300kb addition is worth any of that.
>>>>
(Continue reading)

Permalink | Reply |
headers
Robert Bradshaw | 23 Oct 2012 03:44
Picon

Re: [Cython] array expressions

On Sun, Oct 21, 2012 at 5:39 AM, mark florisson
<markflorisson88@...> wrote:
> On 16 October 2012 18:48, Robert Bradshaw <robertwb@...> wrote:
>> On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
>> <markflorisson88@...> wrote:
>>> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>>>> mark florisson, 14.10.2012 13:59:
>>>>> The problem with minivect as a package is that it caters to different
>>>>> projects, which have different requirements. Cython and minivect are
>>>>> quite closely coupled, and any future change, or in the future any
>>>>> older version may not have the functionality Cython needs, it's not
>>>>> exactly a stable API at this point.
>>>>
>>>> Ok, understood.
>>>>
>>>>
>>>>> For instance Numba needs python
>>>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>>>
>>>>> Before releasing minivect I'll verify every time that it doesn't break
>>>>> Cython, but I currently have no real promises for backwards or forward
>>>>> compatibility. And that is really because not all use cases have yet
>>>>> been anticipated, and some really require a change, as I've already
>>>>> seen with Numba.
>>>>>
>>>>> We could list minivect as a dependency, which works for
>>>>> easy_install/pip users, but I just foresee numerous people running
>>>>> into problems that didn't install with pip, and I don't think an
>>>>> exclusion of a 300kb addition is worth any of that.
>>>>
(Continue reading)

Permalink | Reply |
headers
mark florisson | 23 Oct 2012 11:47
Picon
Gravatar

Re: [Cython] array expressions

On 23 October 2012 02:44, Robert Bradshaw <robertwb@...> wrote:
> On Sun, Oct 21, 2012 at 5:39 AM, mark florisson
> <markflorisson88@...> wrote:
>> On 16 October 2012 18:48, Robert Bradshaw <robertwb@...> wrote:
>>> On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
>>> <markflorisson88@...> wrote:
>>>> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>>>>> mark florisson, 14.10.2012 13:59:
>>>>>> The problem with minivect as a package is that it caters to different
>>>>>> projects, which have different requirements. Cython and minivect are
>>>>>> quite closely coupled, and any future change, or in the future any
>>>>>> older version may not have the functionality Cython needs, it's not
>>>>>> exactly a stable API at this point.
>>>>>
>>>>> Ok, understood.
>>>>>
>>>>>
>>>>>> For instance Numba needs python
>>>>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>>>>
>>>>>> Before releasing minivect I'll verify every time that it doesn't break
>>>>>> Cython, but I currently have no real promises for backwards or forward
>>>>>> compatibility. And that is really because not all use cases have yet
>>>>>> been anticipated, and some really require a change, as I've already
>>>>>> seen with Numba.
>>>>>>
>>>>>> We could list minivect as a dependency, which works for
>>>>>> easy_install/pip users, but I just foresee numerous people running
>>>>>> into problems that didn't install with pip, and I don't think an
>>>>>> exclusion of a 300kb addition is worth any of that.
(Continue reading)

Permalink | Reply |
headers
mark florisson | 28 Oct 2012 13:45
Picon
Gravatar

Re: [Cython] array expressions

On 23 October 2012 10:47, mark florisson
<markflorisson88@...> wrote:
> On 23 October 2012 02:44, Robert Bradshaw <robertwb@...> wrote:
>> On Sun, Oct 21, 2012 at 5:39 AM, mark florisson
>> <markflorisson88@...> wrote:
>>> On 16 October 2012 18:48, Robert Bradshaw <robertwb@...> wrote:
>>>> On Sun, Oct 14, 2012 at 6:13 AM, mark florisson
>>>> <markflorisson88@...> wrote:
>>>>> On 14 October 2012 14:05, Stefan Behnel <stefan_ml@...> wrote:
>>>>>> mark florisson, 14.10.2012 13:59:
>>>>>>> The problem with minivect as a package is that it caters to different
>>>>>>> projects, which have different requirements. Cython and minivect are
>>>>>>> quite closely coupled, and any future change, or in the future any
>>>>>>> older version may not have the functionality Cython needs, it's not
>>>>>>> exactly a stable API at this point.
>>>>>>
>>>>>> Ok, understood.
>>>>>>
>>>>>>
>>>>>>> For instance Numba needs python
>>>>>>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>>>>>>
>>>>>>> Before releasing minivect I'll verify every time that it doesn't break
>>>>>>> Cython, but I currently have no real promises for backwards or forward
>>>>>>> compatibility. And that is really because not all use cases have yet
>>>>>>> been anticipated, and some really require a change, as I've already
>>>>>>> seen with Numba.
>>>>>>>
>>>>>>> We could list minivect as a dependency, which works for
>>>>>>> easy_install/pip users, but I just foresee numerous people running
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 14 Oct 2012 16:27
Picon
Picon
Gravatar

Re: [Cython] array expressions

On 10/14/2012 03:05 PM, Stefan Behnel wrote:
> mark florisson, 14.10.2012 13:59:
>> The problem with minivect as a package is that it caters to different
>> projects, which have different requirements. Cython and minivect are
>> quite closely coupled, and any future change, or in the future any
>> older version may not have the functionality Cython needs, it's not
>> exactly a stable API at this point.
>
> Ok, understood.
>
>
>> For instance Numba needs python
>> 2.7, whereas Cython needs to be compatible with python 2.4.
>>
>> Before releasing minivect I'll verify every time that it doesn't break
>> Cython, but I currently have no real promises for backwards or forward
>> compatibility. And that is really because not all use cases have yet
>> been anticipated, and some really require a change, as I've already
>> seen with Numba.
>>
>> We could list minivect as a dependency, which works for
>> easy_install/pip users, but I just foresee numerous people running
>> into problems that didn't install with pip, and I don't think an
>> exclusion of a 300kb addition is worth any of that.
>
> Fine. In that case, I'm for not making minivect a separate package at all
> but including it directly and considering it a part of Cython (and Numba
> etc.) until there is enough of an interface to make it a reusable separate
> package, or at least to support a separate installation and independent
> update. Basically, if you can't update it separately, there's no use in
(Continue reading)

Permalink | Reply |

Gmane