On Sat, Aug 15, 2015 at 1:08 AM, Pauli Virtanen wrote:
> 15.08.2015, 01:44, Chris Barker kirjoitti:
> [clip]
> > numpy doesn't use namespace packages, so develop mode works there.
>
> The develop mode is mainly useful with a virtualenv.
>
> Otherwise, you install work-in-progress development vers
15.08.2015, 01:44, Chris Barker kirjoitti:
[clip]
> numpy doesn't use namespace packages, so develop mode works there.
The develop mode is mainly useful with a virtualenv.
Otherwise, you install work-in-progress development version into your
~/.local which then breaks everything else. In addition
On Fri, Aug 14, 2015 at 10:15 AM, Stefan van der Walt
wrote:
> Perhaps mpl_toolkits should think of
> becoming mpl_3d, mpl_basemaps, etc.?
>
namespace packages are a fine idea, but the implementation(s) are just one
big kludge...
I think so, but we're getting off-topic here.
numpy doesn't us
On 2015-08-14 10:08:11, Benjamin Root wrote:
> I should also note that there is currently an open issue with
> "pip install -e" and namespace packages. This has been reported
> to matplotlib with regards to mpl_toolkits. Essentially, if you
> have namespace packages, it doesn't get installed co
I think it's clear that develop/-e does not work well together with
namespace packages. As noted on the relevant matplotlib issue
https://github.com/matplotlib/matplotlib/issues/4907 I think the issue with
namespace packages is essentially this well known one
https://github.com/pypa/pip/issues/3 wh
On Fri, Aug 14, 2015 at 10:08 AM, Benjamin Root wrote:
> I used to be a huge advocate for the "develop" mode, but not anymore. I
> have run into way too many Heisenbugs that would clear up if I nuked my
> source tree and re-clone.
>
well, you do need to remember to clean out once in a while, whe
On Aug 14, 2015 09:16, "Chris Barker" wrote:
>
> On Thu, Aug 13, 2015 at 11:25 AM, Stefan van der Walt <
stef...@berkeley.edu> wrote:
>>
>> >(for
>> > example "python setup.py develop", although suggested by
>> > setup.py itself, claims that "develop" is not a command).
>
>
> develop is a command
On 08/14/2015 01:52 PM, Pauli Virtanen wrote:
> 14.08.2015, 20:45, Allan Haldane kirjoitti:
> [clip]
>> Related to this, does anyone know how to debug numpy in gdb with proper
>> symbols/source lines, like I can do with other C extensions? I've tried
>> modifying numpy distutils to try to add the r
14.08.2015, 20:45, Allan Haldane kirjoitti:
[clip]
> Related to this, does anyone know how to debug numpy in gdb with proper
> symbols/source lines, like I can do with other C extensions? I've tried
> modifying numpy distutils to try to add the right compiler/linker flags,
> without success.
runte
On 08/13/2015 11:52 AM, Anne Archibald wrote:
> Hi,
>
> What is a sensible way to work on (modify, compile, and test) numpy?
>
> There is documentation about "contributing to numpy" at:
> http://docs.scipy.org/doc/numpy-dev/dev/index.html
> and:
> http://docs.scipy.org/doc/numpy-dev/dev/gitwash/
I used to be a huge advocate for the "develop" mode, but not anymore. I
have run into way too many Heisenbugs that would clear up if I nuked my
source tree and re-clone.
I should also note that there is currently an open issue with "pip install
-e" and namespace packages. This has been reported to
On Thu, Aug 13, 2015 at 11:25 AM, Stefan van der Walt
wrote:
> >(for
> > example "python setup.py develop", although suggested by
> > setup.py itself, claims that "develop" is not a command).
develop is a command provided by setuptools, not distutils itself.
I find it absolutely invaluable --
On 2015-08-13 08:52:22, Anne Archibald
wrote:
> My current approach is to build an empty virtualenv, pip install
> nose, and from the numpy root directory do "python setup.py
> build_ext --inplace" and "python -c 'import numpy;
> numpy.test()'". This works, for my stock system python, though I
On Thu, Aug 13, 2015 at 10:00 AM, Sebastian Berg wrote:
> On Do, 2015-08-13 at 15:52 +, Anne Archibald wrote:
> > Hi,
> >
> >
> > What is a sensible way to work on (modify, compile, and test) numpy?
> >
> >
> > There is documentation about "contributing to numpy" at:
> > http://docs.scipy.org
On Do, 2015-08-13 at 15:52 +, Anne Archibald wrote:
> Hi,
>
>
> What is a sensible way to work on (modify, compile, and test) numpy?
>
>
> There is documentation about "contributing to numpy" at:
> http://docs.scipy.org/doc/numpy-dev/dev/index.html
>
> and:
> http://docs.scipy.org/doc/num
Hi,
What is a sensible way to work on (modify, compile, and test) numpy?
There is documentation about "contributing to numpy" at:
http://docs.scipy.org/doc/numpy-dev/dev/index.html
and:
http://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html
but these are entirely focused on usi
16 matches
Mail list logo
