+1. This seems nicer than patching __init__.py itself, in that it is much
more transparent.
Good idea.
Michael
On Thu, Feb 11, 2016 at 7:19 PM Matthew Brett
wrote:
> Hi,
>
> Over at https://github.com/numpy/numpy/issues/5479 we're discussing
> Windows wheels.
>
> On
FWIW, we (Continuum) are working on a CI system that builds conda recipes.
Part of this is testing not only individual packages that change, but also
any downstream packages that are also in the repository of recipes. The
configuration for this is in
the whole
CI setup process. We hope we can help each other rather than compete.
Best,
Michael
On Sat, Feb 6, 2016 at 5:53 PM Chris Barker <chris.bar...@noaa.gov> wrote:
> On Sat, Feb 6, 2016 at 3:42 PM, Michael Sarahan <msara...@gmail.com>
> wrote:
>
>> FWIW, we (Continuum)
), but that shouldn't have
> any effect I would imagine.
>
> Greg
>
> On Wed, Jan 27, 2016 at 1:14 PM, Michael Sarahan <msara...@gmail.com>
> wrote:
>
>> I'm not sure about the mingw tool chain, but usually on windows at link
>> time you need a .lib file
I'm not sure about the mingw tool chain, but usually on windows at link
time you need a .lib file, called the import library. The .dll is used at
runtime, not at link time. This is different from *nix, where the .so
serves both purposes. The link you posted mentions import files, so I hope
this
Conda can generally install older versions of python in environments:
conda create -n myenv python=3.4
You really don't need any particular initial version of python/conda in
order to do this. You do, however, need to activate the new environment to
use it:
activate myenv
(For windows, you do
Continuum provides MKL free now - you just need to have a free anaconda.org
account to get the license: http://docs.continuum.io/mkl-optimizations/index
HTH,
Michael
On Wed, Dec 16, 2015 at 12:35 PM Edison Gustavo Muenz <
edisongust...@gmail.com> wrote:
> Sometime ago I saw this:
Running tests in the folder might be causing your problem. If it's trying
to import numpy, and numpy is a folder in your current folder, sometimes
you see errors like this. The confusion is that Python treats folders
(packages) similarly to modules, and the resolution order sometimes bites
you.
xrange should be more memory efficient than range:
http://stackoverflow.com/questions/135041/should-you-always-favor-xrange-over-range
Replacing arrays with lists is probably a bad idea for a lot of reasons.
You'll lose nice vectorization of simple operations, and all of numpy's
other benefits.