[SciPy-Dev] In-place developer installation instructions

Ralf Gommers ralf.gommers at gmail.com
Wed Aug 25 09:48:39 EDT 2021


On Sat, Aug 7, 2021 at 10:51 PM Stefan van der Walt <stefanv at berkeley.edu>
wrote:

> On Fri, Aug 6, 2021, at 11:21, Ralf Gommers wrote:
>
> Hey Stéfan, `build_ext` is used in the main "development workflow" guide:
> http://scipy.github.io/devdocs/dev/contributor/development_workflow.html#basic-workflow,
> and in several other guides. We already have too many guides; there's a
> tracking issue about reducing that complexity to make it easier to
> navigate. Subtracting >= adding here.
>
>
> Great, thanks for the pointer. We can also remove the files not used in
> the documentation (or were they left there for a reason? I see that one has
> an explicit orphan tag.)
>

I'm not sure which files those are. Some orphan tags are on purpose (like
for class methods/attributes IIRC), but not for narrative docs AFAIK.



>
> I would not recommend using `pip -e`, it's worse than `setup.py build_ext
> -i` or `setup.py develop`.
>
>
> What caught me by surprise is that the instructions stop after the
> in-place build step, but without showing how to add it to the Python path
> (instead simply pointing to the runtest script).
>

Yes, that is worth fixing.

Cheers,
Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/scipy-dev/attachments/20210825/9a6acf88/attachment.html>


More information about the SciPy-Dev mailing list