2009/11/30 James Bergstra :
> Your question involves a few concepts:
>
> - an integer vector describing the position of an element
>
> - the logical shape (another int vector)
>
> - the physical strides (another int vector)
>
> Ignoring the case of negative offsets, a physical offset is the inner
>
Hi,
The first release candidate for 1.4.0 has been released. The sources,
as well as mac and windows installers may be found here:
https://sourceforge.net/projects/numpy/files/
The main improvements compared to 1.3.0 are:
* Faster import time
* Extended array wrapping mechanism for ufuncs
* New
Your question involves a few concepts:
- an integer vector describing the position of an element
- the logical shape (another int vector)
- the physical strides (another int vector)
Ignoring the case of negative offsets, a physical offset is the inner
product of the physical strides with the po
Donovan Parks wrote:
I think this may have nothing at all to do with numpy. Have you tried a
simple script that doesn't use numpy?
> OS X Leopard
> MacPort
I use neither Leopard nor macports, so it may be an issue there, but
with the python.org python25 and numpy1.3, I have no problems.
> When
Hello,
I am trying to package a simple python script which uses numpy using
py2app. There was a lengthy discussion about this back in 2006 on this
list, but it doesn't seem relevant anymore given the changes to numpy
and py2app over the last few years. I am hoping someone on this list
has experien
Hi Pauli,
It looks like you doing great stuff with the py3k transition. Do you and
David have any sort of merge schedule in mind?
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
The most popular/simple way to deal with the VC90.CRT dependency issue
is to have the user install the runtime redistributable on their system.
If you don't want to put that burden on the user, which I understand,
you have to make adjustments to the assembly manifests. This is not
unofficial or
David Cournapeau skrev:
> We are talking about the numpy extensions here, which are not
> installed through the install_data command. The problem is about how
> windows looks for dll with the manifest mechanism, and how to
> build/install extensions when the C runtime (or any other "system"
> dll)
David Cournapeau skrev:
> We are talking about the numpy extensions here, which are not
> installed through the install_data command. The problem is about how
> windows looks for dll with the manifest mechanism, and how to
> build/install extensions when the C runtime (or any other "system"
> dll)
On Mon, Nov 30, 2009 at 10:48 PM, Sturla Molden wrote:
> David Cournapeau skrev:
>> If every python package starts to put its extensions (*.pyd) into a
>> directory, what happens when two different packages have an extension
>> with the same name (e.g. package foo has a package multiarray.pyd) ? I
David Cournapeau skrev:
> If every python package starts to put its extensions (*.pyd) into a
> directory, what happens when two different packages have an extension
> with the same name (e.g. package foo has a package multiarray.pyd) ? I
> would also be really annoyed if a 3rd party extension star
Colin J. Williams skrev:
> Where the distribution of a variate is not known a priori, then I
> believe that it can be shown
> that the n-1 divisor provides the best estimate of the variance.
>
Have you ever been shooting with a rifle?
What would you rather do:
- Hit 9 or 10, with a bias to th
On Mon, Nov 30, 2009 at 8:52 PM, Eloi Gaudry wrote:
>
> Well, I wasn't aware of Microsoft willing to giving up the whole
> SxS/manifest thing. Is there any MSDN information available?
I have seen this mentioned for the first time on the python-dev ML:
http://aspn.activestate.com/ASPN/Mail/Messa
David Cournapeau wrote:
> Eloi Gaudry wrote:
>
>> David, I think that what Christoph pointed here applies to the msvc
>> built libraries only (I need to build the whole python/extensions using
>> msvc).
>>
>>
>
> Ok, I did not understand that point. Do you know if the patch discussed
>
Eloi Gaudry wrote:
> David, I think that what Christoph pointed here applies to the msvc
> built libraries only (I need to build the whole python/extensions using
> msvc).
>
Ok, I did not understand that point. Do you know if the patch discussed
in 4120 has been applied to 2.6.4 ?
> May I a
David, I think that what Christoph pointed here applies to the msvc
built libraries only (I need to build the whole python/extensions using
msvc).
May I ask you what re the "clashes between extensions" you were
referring to in your previous answer ? Have you already encountered such
issues ?
I
Christoph, thanks for pointing this discussion. That's a perfect match.
If the workaround provided offers a solution to the current
redistribution issue, I'm wondering if it will still be the case when an
update to the assembly check function will be activated/implemented
(within Windows).
The
17 matches
Mail list logo
