Hi, Travis
I tried numpy1.0b4 and add this to setup.py
includes = ["numpy.core._internal"]
then it works! And all scripts can be packed into a single executables with
"bundle_files":2,
"skip_archive":0,
zipfile = None,
--skip_archive option is not needed now.
Hi, Travis
I can pack my scripts into an executable with py2exe, but errors occur
once it runs:
No scipy-style subpackage 'random' found in D:\test\dist\numpy.
Ignoring: No module named info
import core -> failed: No module named _internal
import lib -> failed: 'module' object has no attribute '_
st 27, 2006 3:55 pm
Subject: Re: [Numpy-discussion] [ANN] NumPy 1.0b4 now available
> If your Excel parsing has general application and
> illustrates applications beyond say
> http://www.bigbold.com/snippets/posts/show/2036
> maybe you c
On Sun, 27 Aug 2006, Les Schaffer apparently wrote:
> we are parsing excel spreadsheets and pushing them into
> recarrays
If your Excel parsing has general application and
illustrates applications beyond say
http://www.bigbold.com/snippets/posts/show/2036
maybe you could post a URL to some co
Travis:
thanks for your response. over the next couple days i will be working
with the records module, trying to fix things so we can move from
numarray to numpy. i will try to collect some docstrings that can be
added to the code base.
Travis Oliphant wrote:
> Your right. It's an oversight tha
Les Schaffer wrote:
> Travis E. Oliphant wrote:
>
>> Porting is not difficult especially using the compatibility layers
>> numpy.oldnumeric and numpy.numarray and the alter_code1.py modules in
>> those packages. The full C-API of Numeric is supported as is the C-API
>> of Numarray.
>>
>>
Alan G Isaac wrote:
> Did Albert's initiative get any traction?
> http://www.mail-archive.com/numpy-discussion@lists.sourceforge.net/msg01616.html
> If so, Les might profit from coordinating with him.
Not so much. Not many people showed up to the sprints, and most of those that
did were working
> Les Schaffer wrote:
>> i'll pitch in some
>> time to add docstrings, if i know they will be used.
On Sat, 26 Aug 2006, Robert Kern apparently wrote:
> Of course they will.
Did Albert's initiative get any traction?
http://www.mail-archive.com/numpy-discussion@lists.sourceforge.net/msg0161
Les Schaffer wrote:
> i'll pitch in some
> time to add docstrings, if i know they will be used.
Of course they will.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an u
Alan G Isaac wrote:
> Of course I bothered to write because I read this list and
> appreciate in addition to its helpfulness that it generally
> maintains a more polite tone. This too has value.
>
>
>
so, you want to work on improving the documentation of this poorly
documented module? then
On Sat, 26 Aug 2006, Les Schaffer apparently wrote:
> save the moral speech
I did not say anything about morals.
I spoke only of *advantages* of politeness,
which someone age 52 might still need to ponder.
Of course I bothered to write because I read this list and
appreciate in addition to its
Alan G Isaac wrote:
> I am always mystified when someone requesting free help
> adopts a pissy tone if they do not immediately
> get what they wish.
>
> It reminds me a bit of my youngest child, age 7,
> whom I am still teaching the advantages of politeness.
>
you are refering to robert kern i
On Sat, 26 Aug 2006, Les Schaffer apparently wrote:
> congratulations, this can be the first docstring in
> records. now what about the incompatibility between old
> and new
I am always mystified when someone requesting free help
adopts a pissy tone if they do not immediately
get what they wi
Robert Kern wrote:
> http://www.scipy.org/RecordArrays
>
which didn't help one iota. look, someone is charging for documentation,
but the claim is the free docstrings have docs. for the records module,
this ain't so. documentation means someone knows what is the complete
public interface. yes,
Les Schaffer wrote:
> 3. near zero docstrings for this module, hard to see how the new
> records works.
http://www.scipy.org/RecordArrays
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it
Les Schaffer wrote:
> 4. last year i made a case for the old records to return a list of the
> column names. it looks like the column names are now attributes of the
> record object, any chance of getting a list of them
> recarrayObj.get_colNames() or some such? yes, in working code, we know
> wha
Travis E. Oliphant wrote:
> Porting is not difficult especially using the compatibility layers
> numpy.oldnumeric and numpy.numarray and the alter_code1.py modules in
> those packages. The full C-API of Numeric is supported as is the C-API
> of Numarray.
>
this is not true of numpy.core.rec
The 4th beta release of NumPy 1.0 has just been made available.
NumPy 1.0 represents the culmination of over 18 months of work to unify
the Numeric and Numarray array packages into a single best-of-breed
array package for Python.
NumPy supports all the features of Numeric and Numarray with a he
18 matches
Mail list logo