[SciPy-Dev] What we do struggle with is lack of progress on big-ticket items

[Andrew Nelson]

I do all my work on OSX.

This is a highlevel view of how I did my setup:

0) Make sure I have the command line tools for Xcode. Means installing
Xcode, then install those tools.
1) Install git from source on terminal. (might be difficult for those
unacquainted with POSIX, in that use of the terminal is required, etc)
2) Install miniconda
3) Create a conda Python36 environment and activate it (unless I have to I
don't touch 27 anymore)
4) conda install numpy, matplotlib, jupyter, cython, nose, pytest, etc into
that environment
5) create a local copy of my scipy fork on github.
6) Install pycharm as a IDE.
7) Install gfortran, I think I downloaded an installer from somewhere, but
I can't remember where. (I may have even built it myself, not sure).
8) test scipy: python runtests.py
9) install scipy: pip install .

Dev workflow:
1) Update master branch of local repo from scipy/master
2) Create a feature branch
3) Make changes in Pycharm, remember to add tests for the issue. Sometimes
I fiddle around with code in jupyter notebooks to see if what I've written
would work.
4) python runtests.py to see if the changes worked.
5) git Commit and push to github fork.
6) Create PR in scipy from github fork.

A lot of that might be scriptable. There are some that use brew, etc, but
I've always been a bit wary of using that kind of package manager. Usually
if you build it yourself (e.g. git) it works just fine.

When doing PR's I rely on Appveyor to tell me if something works on Windows
(just too complicated otherwise).
I'm happy to advise on any of those steps.
A.


On 24 January 2018 at 09:49, Matt Haberland <haberland at ucla.edu> wrote:

> Funny, I was just writing about this to suggest videos, too.
>
> I looked on YouTube but didn't find anything useful when searching for
> numpy/scipy development environment/workflow.
>
> Besides the day-to-day workflow, I also had a hard time getting my
> development environment set up initially. A video on that would be really
> helpful, too.
>
> I'd be happy to make some videos with a screen recording and voice-over. I
> want to start from scratch on Mac, as my environment seems to have broken
> over the past few months, and I'd like to try again on Windows, which I
> never got working. If someone with real experience on one or both of those
> platforms has some time to answer questions that inevitably arise, I'd be
> willing to work on this immediately.
>
> Matt
>
>
> On Tue, Jan 23, 2018 at 11:56 AM, Charles R Harris <
> charlesr.harris at gmail.com> wrote:
>
>>
>>
>> On Tue, Jan 23, 2018 at 12:20 PM, Stefan van der Walt <
>> stefanv at berkeley.edu> wrote:
>>
>>> Hi Robert
>>>
>>> On Tue, 23 Jan 2018 04:57:01 -0500, Robert Lucente - Pipeline.Com wrote:
>>> > I am a newbie and have just been lurking.
>>>
>>> Thank you for raising your thoughts here; it's so helpful to hear
>>> perspectives from outside the established developer community.
>>>
>>> > Perhaps we could put some bounds around unacceptable, good enough and
>>> > perfection? I realize that it is hard to put words to this. Perhaps an
>>> > example to kick off a conversation?
>>>
>>> It's a tricky balance.  My feeling is that a person should lower the
>>> barrier to contribution as much as possible: avoid unnecessary technical
>>> challenges like git rebasing, push to PRs to guide new contributors, and
>>> provide good documentation.
>>>
>>> That said, I think it's better to educate than to adjust standards.
>>> Experience has taught that introducing code of insufficient quality into
>>> the code base inevitably leads to headaches later on (we all have a lot
>>> of hypothetical time to fix things up in the future, right?).
>>>
>>> > Perhaps people could volunteer to just help someone w/ the SciPy
>>> > workflow?
>>>
>>> This is an excellent suggestion, and one we've also been considering for
>>> scikit-image.  The idea of having existing developers acting as mentors
>>> is often what happens informally, but it may be helpful to establish
>>> more obvious ways for that to take place.  Do you have any thoughts on
>>> how this could look?
>>>
>>
>> I know there have been several presentations on the workflow, Jamie Frio
>> did a couple. It might useful to see if anyone has made video's of a
>> tutorial like that so we could put it up on youtube or some other place.
>> Maybe NumFocus could have a youtube channel with such resources.
>>
>> Chuck
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
>>
>
>
> --
> Matt Haberland
> Assistant Adjunct Professor in the Program in Computing
> Department of Mathematics
> 6617A Math Sciences Building, UCLA
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
>


-- 
_____________________________________
Dr. Andrew Nelson


_____________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180124/6a932bb0/attachment.html>