Sasha wrote:
>I would like to add my voice to a call for single prefix (I like
>PyArray_ for everything, but can live with npy_). Presumably npy_
>vs. NPY_ variation is supposed to distinguish between macros and C
>language elements, but as long as the stem is properly capitalized, I
>don't see
I would like to add my voice to a call for single prefix (I like
PyArray_ for everything, but can live with npy_). Presumably npy_
vs. NPY_ variation is supposed to distinguish between macros and C
language elements, but as long as the stem is properly capitalized, I
don't see a problem of using
Russell E. Owen wrote:
>In article <[EMAIL PROTECTED]>,
> Travis Oliphant <[EMAIL PROTECTED]> wrote:
>
>
>
>>3) C-API names have prefix PyArray_ (like always), NPY_ or npy_.
>>
>> The NPY_ and npy_ prefixes are new and were done to remove the
>> likelihood of name collisions when NumPy is
Christian Kristukat wrote:
>Travis Oliphant ieee.org> writes:
>
>
>
>>Some of you may have noticed that things have been changing rapidly in
>>the NumPy world (if you were out of the office in June then all the
>>activity may seem overwhelming).
>>
>>All of this activity is based on the fact
In article <[EMAIL PROTECTED]>,
Travis Oliphant <[EMAIL PROTECTED]> wrote:
> 3) C-API names have prefix PyArray_ (like always), NPY_ or npy_.
>
>The NPY_ and npy_ prefixes are new and were done to remove the
>likelihood of name collisions when NumPy is used with another
>library.
Charles R Harris gmail.com> writes:
>
>
> Hi,
>
> On 7/9/06, Robert Kern gmail.com> wrote:
> Christian Kristukat wrote:> Robert Kern gmail.com>
writes:>>> I believe that Debian recently changed its configuration to default
to
> >> /usr/local (for good reason!). Perhaps that is causing what
Hi,On 7/9/06, Robert Kern <[EMAIL PROTECTED]> wrote:
Christian Kristukat wrote:> Robert Kern gmail.com> writes:>>> I believe that Debian recently changed its configuration to default to
>> /usr/local (for good reason!). Perhaps that is causing what you see.>> I just found out that this is feature/
Christian Kristukat wrote:
> Robert Kern gmail.com> writes:
>
>> I believe that Debian recently changed its configuration to default to
>> /usr/local (for good reason!). Perhaps that is causing what you see.
>
> I just found out that this is feature/bug of opensuse 10.1. I'm beginning to
> like
Robert Kern gmail.com> writes:
> I believe that Debian recently changed its configuration to default to
> /usr/local (for good reason!). Perhaps that is causing what you see.
>
I just found out that this is feature/bug of opensuse 10.1. I'm beginning to
like it but can you tell what you have t
Christian Kristukat wrote:
> Travis Oliphant ieee.org> writes:
>
>> Some of you may have noticed that things have been changing rapidly in
>> the NumPy world (if you were out of the office in June then all the
>> activity may seem overwhelming).
>>
>> All of this activity is based on the fact
Travis Oliphant ieee.org> writes:
>
>
> Some of you may have noticed that things have been changing rapidly in
> the NumPy world (if you were out of the office in June then all the
> activity may seem overwhelming).
>
> All of this activity is based on the fact that the upcoming beta releas
Hi Travis,
My suggestion: Because you said you want to do a feature freeze, this
should be pretty easy to handle. Wait for a feature freeze point then
create a 1.0 branch. From then, new stuff can continue going into the
trunk. Bug fixes go into the trunk and the 1.0 branch.
Gary R.
Travis Ol
Charles R Harris wrote:
> Hi Travis,
>
> Are you going to make a development branch so other things can
> continue going into Numpy until the 1.0 release?
Something like that is a good idea. I'm open to suggestions...
-Travis
--
Hi Travis,Are you going to make a development branch so other things can continue going into Numpy until the 1.0 release?ChuckOn 7/8/06, Darren Dale
<[EMAIL PROTECTED]> wrote:On Saturday 08 July 2006 4:04 am, Stephan Tolksdorf wrote:
> Hi Travis,>> thanks for putting all the effort into NumPy.>>
On Saturday 08 July 2006 4:04 am, Stephan Tolksdorf wrote:
> Hi Travis,
>
> thanks for putting all the effort into NumPy.
>
> > Unless there is a serious issue pointed out, the only thing that should
> > be changed at this point are bug-fixes, documentation strings, and added
> > tests. Once 1.
Hi Travis,
thanks for putting all the effort into NumPy.
> Unless there is a serious issue pointed out, the only thing that should
> be changed at this point are bug-fixes, documentation strings, and added
> tests. Once 1.0b1 is released nothing but those things can be added.
The beginning o
16 matches
Mail list logo
