n Fri, Nov 18, 2016 at 2:46 PM, Nathan Goldbaum wrote:
> Since the NumPy API is forwards compatible, you should use the oldest
> version of NumPy you would like to support to build your wheels with. The
> wheels will then work with any future NumPy versions.
>
> On Fri, Nov 18, 2
I have a related question to Matti's,
Do you have any recommendations for building standard wheels
for 3rd party Python libraries which use both the NumPy Python
and C API?
e.g. Do we need to do anything special given the NumPy C API
itself is versioned? Does it matter compiler chain should we us
On Fri, Jun 10, 2016 at 7:42 AM, Nathaniel Smith wrote:
> On Mon, Jun 6, 2016 at 1:17 PM, Charles R Harris
> wrote:
>>
>> ...
>>
>> It looks to me like users want floats, while developers want the
>> easy path of raising an error. Darn those users, they just make
>> life sooo difficult...
>
> I d
On Sun, Apr 3, 2016 at 2:11 AM, Matthew Brett wrote:
> On Fri, Mar 25, 2016 at 6:39 AM, Peter Cock wrote:
>> On Fri, Mar 25, 2016 at 3:02 AM, Robert T. McGibbon
>> wrote:
>>> I suspect that many of the maintainers of major scipy-ecosystem projects are
>>>
On Fri, Mar 25, 2016 at 3:02 AM, Robert T. McGibbon wrote:
> I suspect that many of the maintainers of major scipy-ecosystem projects are
> aware of these (or other similar) travis wheel caches, but would guess that
> the pool of travis-ci python users who weren't aware of these wheel caches
> is
On Thu, Mar 24, 2016 at 6:37 PM, Nathaniel Smith wrote:
> On Mar 24, 2016 8:04 AM, "Peter Cock" wrote:
>>
>> Hi Nathaniel,
>>
>> Will you be providing portable Linux wheels aka manylinux1?
>> https://www.python.org/dev/peps/pep-0513/
>
> Matthew B
Hi Nathaniel,
Will you be providing portable Linux wheels aka manylinux1?
https://www.python.org/dev/peps/pep-0513/
Does this also open up the door to releasing wheels for SciPy
too?
While speeding up "pip install" would be of benefit in itself,
I am particularly keen to see this for use within
On Fri, Dec 18, 2015 at 9:12 AM, Nathaniel Smith wrote:
> Hi all,
>
> I'm wondering what people think of the idea of us (= numpy) stopping
> providing our "official" win32 builds (the "superpack installers"
> distributed on sourceforge) starting with the next release.
>
> These builds are:
>
> -
Migrating from SourceForge seems worth considering. I also
agree this is a breach of trust with the open source community.
It is my impression that the GIMP team stopped using SF for
downloads some time ago in favour of using their own website,
leaving the SF account live to maintain the old relea
On Mon, Apr 27, 2015 at 1:04 PM, Ralf Gommers wrote:
>
> Done in the master branch of https://github.com/rgommers/vendor. I think
> that "numpy-vendor" is a better repo name than "vendor" (which is pretty
> much meaningless outside of the numpy github org), so I propose to push my
> master branch
On Tue, Feb 25, 2014 at 4:41 PM, Alexander Belopolsky wrote:
>
> On Tue, Feb 25, 2014 at 11:29 AM, Benjamin Root wrote:
>>
>> I seem to recall reading somewhere that pickles are not intended to be
>> long-term archives as there is no guarantee that a pickle made in one
>> version of python would
On Sat, Feb 1, 2014 at 3:40 PM, Ralf Gommers wrote:
>
> On Fri, Jan 24, 2014 at 12:26 AM, Vincent Davis
> wrote:
>>
>> I happen to be working with De Bruijn sequences. Is there any interest in
>> this being part of numpy/scipy?
>>
>> https://gist.github.com/vincentdavis/8588879
>
> That looks lik
On Mon, Sep 23, 2013 at 10:53 PM, Charles R Harris
wrote:
> On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris wrote:
>> On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock wrote:
>>>
>>> Hi Chuck,
>>>
>>> Could you clarify how we'd know if this is a prob
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris
wrote:
> Hi All,
>
> I have gotten no feedback on the removal of the numarray and oldnumeric
> packages. Consequently the removal will take place on 9/28. Scream now or
> never...
>
> Chuck
Hi Chuck,
Could you clarify how we'd know if this is a p
On Mon, Sep 16, 2013 at 8:05 PM, Nathaniel Smith wrote:
>
> Why not just release numpy 1.8 with the old and terrible system? As
> you know I'm 110% in favor of getting rid of it, but 1.8 is ready to
> go and 1.9 is coming soon enough, and the old and terrible system does
> work right now, today. N
On Sun, Sep 8, 2013 at 9:07 PM, Charles R Harris wrote:
>
> On Sun, Sep 8, 2013 at 1:29 PM, Ralf Gommers wrote:
>>
>> On Sun, Sep 8, 2013 at 7:26 PM, Charles R Harris wrote:
>>>
>>> Hi All,
>>>
>>> Currently the beta and rc files for numpy versions >= 1.6.1 are still up
>>> on sourceforge. I think
On Tue, Aug 13, 2013 at 1:20 PM, Resmi wrote:
> Hi,
>
> I've a list of long files of numerical data ending with footer lines
> (beginning with #). I am using numpy.loadtxt to read the numbers, and
> loadtxt ignores these footer lines. I want the numpy code to read one of the
> footer lines and ext
On Fri, May 24, 2013 at 3:02 PM, Warren Weckesser
wrote:
> On 5/24/13, Peter Cock wrote:
>>Warren wrote:
>>> Two more data points:
>>> On Ubuntu 12.04, using 64 bit builds of Python 2.7.4 (from Anaconda
>>> 1.5.0), and numpy built from source: numpy 1.6.1 giv
On Fri, May 24, 2013 at 2:47 PM, Warren Weckesser
wrote:
>
>Peter wrote:
>> ---
>> Successes
>> ---
>>
>> 64 bit Linux:
>>
>> $ python2.6
>> Python 2.6.6 (r266:84292, Sep 11 2012, 08:34:23)
>> [GCC 4.4.6 20120305 (Red
On Fri, May 24, 2013 at 2:15 PM, Robert Kern wrote:
> On Fri, May 24, 2013 at 9:12 AM, Peter Cock wrote:
>> On Fri, May 24, 2013 at 1:59 PM, Emanuele Olivetti
>> wrote:
>>> Interesting. Anyone able to reproduce what I observe?
>>>
>>> Emanuele
>>
On Fri, May 24, 2013 at 1:59 PM, Emanuele Olivetti
wrote:
> Interesting. Anyone able to reproduce what I observe?
>
> Emanuele
Yes, I can reproduce this IndexError under Mac OS X:
$ which python2.7
/usr/bin/python2.7
$ python2.7
Python 2.7.2 (default, Oct 11 2012, 20:14:37)
[GCC 4.2.1 Compatibl
On Fri, Apr 26, 2013 at 4:11 PM, Robert Kern wrote:
> On Fri, Apr 26, 2013 at 3:20 PM, Christopher Hanley wrote:
>> Dear Numpy Webmasters,
>>
>> Would it be possible to either redirect numpy.scipy.org to www.numpy.org or
>> to the main numpy github landing page? Currently numpy.scipy.org hits a
Hello all,
http://numpy.scipy.org is giving a GitHub 404 error.
As this used to be a widely used URL for the project,
and likely appears in many printed references, could
it be fixed to point to or redirect to the (relatively new)
http://www.numpy.org site please?
Thanks,
Peter
On Wed, Feb 20, 2013 at 11:23 PM, Robert Kern wrote:
> On Wed, Feb 20, 2013 at 11:21 PM, Peter Cock wrote:
>> On Wed, Feb 20, 2013 at 8:27 PM, Todd wrote:
>>>
>>> I am looking at documentation now, but a couple things from what I seen:
>>>
>>> Are you
On Wed, Feb 20, 2013 at 8:27 PM, Todd wrote:
>
> I am looking at documentation now, but a couple things from what I seen:
>
> Are you particularly tied to sourceforge? It seems a lot of python
> development is moving to github, and it makes third party contribution much
> easier. You can still di
On Wed, Feb 6, 2013 at 3:46 AM, Ondřej Čertík wrote:
> On Tue, Feb 5, 2013 at 12:22 PM, Ralf Gommers wrote:
>> On Tue, Feb 5, 2013 at 3:01 PM, Peter Cock
>> wrote:
>>>
>>> Hello all,
>>>
>>> Will the numpy 1.7.0 'final' be binary c
Hello all,
Will the numpy 1.7.0 'final' be binary compatible with the release
candidate(s)? i.e. Would it be safe for me to release a Windows
installer for a package using the NumPy C API compiled against
the NumPy 1.7.0rc?
I'm specifically interested in Python 3.3, and NumPy 1.7 will be
the firs
On Thu, Jan 10, 2013 at 3:56 PM, klo wrote:
> Hi,
>
> I run `python3 setup.py config` and then
>
> python3 setup.py build --compiler=mingw32
>
> but it picks that I have MSVC 10 and complains about manifests.
> Why, or even better, how to compile with available MinGW compilers?
I reported this
On Fri, Jan 4, 2013 at 12:49 AM, Nathaniel Smith wrote:
> On 4 Jan 2013 00:39, "Peter Cock" wrote:
>> I agree with Dag rather than Andrew, "Explicit is better than implicit".
>> i.e. What Nathaniel described earlier as the apparent consensus.
>>
>
On Fri, Jan 4, 2013 at 12:39 AM, Peter Cock wrote:
>> Since I've actually used NumPy arrays with specific low memory
>> types, I thought I should comment about my use case if case it
>> is helpful:
>>
>> I've only used the low precision types like np.uint8
On Fri, Jan 4, 2013 at 12:11 AM, Dag Sverre Seljebotn
wrote:
> On 01/04/2013 12:39 AM, Andrew Collette wrote:
> > Nathaniel Smith wrote:
> >> Consensus in that bug report seems to be that for array/scalar operations
> >> like:
> >>np.array([1], dtype=np.int8) + 1000 # can't be represented as
On Tue, Nov 27, 2012 at 9:25 PM, Anthony Scopatz wrote:
> On Tue, Nov 27, 2012 at 2:08 PM, Fernando Perez
> wrote:
>>
>> On Thu, Nov 22, 2012 at 1:30 AM, Peter Cock
>> wrote:
>>
>> > Perhaps http://numfocus.org/ could take them on, or the PSF?
>>
On Tue, Nov 27, 2012 at 12:27 PM, Thomas Robitaille
wrote:
> Hi everyone,
>
> I'm currently having issues with installing Numpy 1.6.2 with Python
> 3.1 and 3.2 using pip in Travis builds - see for example:
>
> https://travis-ci.org/astropy/astropy/jobs/3379866
>
> The build aborts with a cryptic m
On Thu, Nov 22, 2012 at 4:17 AM, Fernando Perez wrote:
> Hi folks,
>
> years ago, John Hunter and I bought the py4science.{com, org, info}
> domains thinking they might be useful. We never did anything with
> them, and with his passing I realized I'm not really in the mood to
> keep renewing them
On Fri, Nov 16, 2012 at 10:08 AM, Christoph Gohlke wrote:
> On 11/16/2012 1:28 AM, Peter Cock wrote:
>> On Thu, Nov 15, 2012 at 6:15 PM, Christoph Gohlke wrote:
>>>
>>> Naturally the file would be named msvc10compiler.py but the name may be
>>> kept for comp
On Thu, Nov 15, 2012 at 6:15 PM, Christoph Gohlke wrote:
>
> Naturally the file would be named msvc10compiler.py but the name may be
> kept for compatibility reasons. AFAIK msvc10 does not use manifests any
> longer for the CRT dependencies and all the code handling msvc9
> manifests could be remo
On Wed, Nov 14, 2012 at 7:35 PM, Christoph Gohlke wrote:
>> ...
>> RuntimeError: Broken toolchain: cannot link a simple C program
>>
>> It appears a similar issue was raised before:
>> http://mail.scipy.org/pipermail/numpy-discussion/2012-June/062866.html
>>
>> Any tips?
>>
>> Peter
>
> Try changi
Changing title to reflect the fact this thread is now about using
the Microsoft compiler rather than mingw32 as in the old thread.
On Sat, Nov 10, 2012 at 11:04 PM, Peter Cock wrote:
> On Sat, Nov 10, 2012 at 5:47 PM, Ralf Gommers wrote:
>>
>>
>>
>> On Tue, Nov 6,
On Wed, Nov 14, 2012 at 4:24 AM, Ondřej Čertík wrote:
> On Mon, Nov 12, 2012 at 2:27 PM, Ondřej Čertík
> wrote:
> [...]
> > Here is a list of issues that need to be fixed before the release:
> >
> > https://github.com/numpy/numpy/issues?milestone=3&state=open
> >
> > If anyone wants to help, we j
On Tue, Nov 13, 2012 at 12:36 AM, Peter Cock wrote:
>
> I've not yet run the numpy tests yet, but I think this means
> my github branches are worth merging:
>
> https://github.com/peterjc/numpy/commits/msvc10
>
Hi Ralf,
Pull request filed, assuming this gets applied to th
On Mon, Nov 12, 2012 at 9:20 PM, Ralf Gommers wrote:
>> ...
>> Found executable C:\cygwin\usr\bin\gcc.exe
>> g++ -mno-cygwin _configtest.o -lmsvcr100 -o _configtest.exe
>> Could not locate executable g++
>> Executable g++ does not exist
>
>
> A C++ compiler shouldn't be needed for numpy, so it sho
On Sun, Nov 11, 2012 at 11:20 PM, Peter Cock wrote:
> On Sun, Nov 11, 2012 at 9:05 PM, Ralf Gommers wrote:
>>
>> Those changes look correct, a PR would be great.
>>
>
> I'll do that later this week - but feel free to do it yourself immediately
> if more con
On Sun, Nov 11, 2012 at 9:05 PM, Ralf Gommers wrote:
>
> Those changes look correct, a PR would be great.
>
I'll do that later this week - but feel free to do it yourself immediately
if more convenient.
> Fixing the next error also seems straightforward; around line 465 of
> mingw32ccompiler a c
On Sat, Nov 10, 2012 at 11:24 PM, Peter Cock wrote:
>
> I think part of the problem could be in numpy/distutils/misc_util.py
> where there is no code to detect MSCV 10,
>
> def msvc_runtime_library():
> "Return name of MSVC runtime library if Python was built with M
I meant to click on "save" not "send", anyway:
On Sat, Nov 10, 2012 at 11:13 PM, Peter Cock wrote:
>>
>> Either MSVC or MinGW 3.4.5. For the latter see
>> https://github.com/certik/numpy-vendor
>>
>> Ralf
>
> I was trying with mingw32 v
On Sat, Nov 10, 2012 at 5:47 PM, Ralf Gommers wrote:
> On Tue, Nov 6, 2012 at 6:49 PM, Peter Cock wrote:
>>
>> Dear all,
>>
>> Since the NumPy 1.7.0b2 release didn't include a Windows
>> (32 bit) installer for Python 3.3, I am considering compiling it
>>
On Sat, Nov 10, 2012 at 5:47 PM, Ralf Gommers wrote:
>
>
>
> On Tue, Nov 6, 2012 at 6:49 PM, Peter Cock
> wrote:
>>
>> Dear all,
>>
>> Since the NumPy 1.7.0b2 release didn't include a Windows
>> (32 bit) installer for Python 3.3, I am consider
Dear all,
Since the NumPy 1.7.0b2 release didn't include a Windows
(32 bit) installer for Python 3.3, I am considering compiling it
myself for local testing. What compiler is recommended?
Thanks,
Peter
___
NumPy-Discussion mailing list
NumPy-Discussion
48 matches
Mail list logo
