Mailman 3 December 2019 - yt-dev

Switching from Nose to Pytest
by Coughlin, Jared W Dec. 20, 2019

Dec. 20, 2019

Hello! I've been working on a PR (https://github.com/yt-project/yt/pull/2286) that converts yt's testing framework from nose to pytest. I believe that it's mostly ready to go, so I was writing to see what everyone's thoughts on this change are, if there is any feedback on my implementation, and if anyone would be willing to help review it, since there are quite a few changes. Thanks, and have a good weekend! -Jared

5 10

Fwd: [NumFOCUS Projects] Google Summer of Code 2020
by Nathan Dec. 12, 2019

Dec. 12, 2019

Hi all, If anyone is interested in running GSOC, please see below. I'm happy to help out with GSOC but don't have the bandwidth to run it. Also happy to answer questions about it if you're interested. GSOC was very successful for us a few years ago and it would be nice to do it again if we can. -Nathan ---------- Forwarded message --------- From: Nicole Foster <nicole(a)numfocus.org> Date: Thu, Dec 12, 2019 at 2:51 PM Subject: [NumFOCUS Projects] Google Summer of Code 2020 To: <projects(a)numfocus.org>, Affiliated Projects <affiliated(a)numfocus.org> Cc: <seth.mridul(a)gmail.com> Hello, NumFOCUS project leaders! NumFOCUS has participated in Google Summer of Code (GSoC) as a mentoring organization since 2015 and will do so again for 2020. *If you would like to participate in GSoC 2020 under the NumFOCUS umbrella*, please email the NumFOCUS GSoC 2020 Coordinator: Mridul Seth < seth.mridul(a)gmail.com> *NumFOCUS will submit one application with as many projects underneath us as would like to participate.* Applications for GSoC mentoring organizations open on January 14th, and the deadline to apply is Feb 5th. (full timeline is here <https://developers.google.com/open-source/gsoc/timeline>) - - - - - Below is some additional information about the program and considerations for participating. *GSoC Last Year* In 2019, the following projects participated in GSoC under NumFOCUS: - ArviZ - Blosc - Cantera - Chainer - CuPy - Dask - Data Retriever - FEniCS - JuMP - Matplotlib - MDAnalysis - nteract - PyMC3 - QuTiP - Yellowbrick AstroPy, SunPy, Julia, Shogun and SymPy participated separately or under other partner organizations. We ran a blog series last summer highlighting all student participants which you can access here ( https://numfocus.org/blog/meet-our-2019-gsoc-students-part-1) . It should be enlightening in terms of student motivations and the sorts of projects they take on through the program. The GH repo that maintains information about the NumFOCUS process for GSoC is here <https://github.com/numfocus/gsoc> and contains many details about our internal processes and rules (not all of which are required by Google but which we have found to improve outcomes for the program). *Should My Project Participate?* The main thing to keep in mind when considering whether to participate is to ensure that you have a sufficient number of mentors with available mentoring time. 2 or even 3 mentors per student helps to spread the work around and keep things manageable for everyone. Based on Matplotlib's experience taking on two students in 2017, they recommend that projects who feel somewhat unsure about their mentoring capacity be less ambitious in the number of students you accept. *Why Participate?* Prior participants have generally had very good experiences with GSoC. It is often cited as a primary driver behind finding new regular contributors and eventual maintainers, so very good for the funnel of potential future project leaders. GSoC also offers a great opportunity to diversify the mix of your contributors. Shogun, for example, has had great success in recruiting and mentoring women through GSoC who then stayed on as project maintainers. If you have any further questions about GSoC participation, please reach out to Mridul Seth <seth.mridul(a)gmail.com>. Best, -- Nicole Foster Executive Operations Administrator, NumFOCUS nicole(a)numfocus.org 512-831-2870 <http://www.numfocus.org/> <https://twitter.com/NumFOCUS> <https://www.facebook.com/NumFOCUS/> -- You received this message because you are subscribed to the Google Groups "Fiscally Sponsored Project Representatives" group. To unsubscribe from this group and stop receiving emails from it, send an email to projects+unsubscribe(a)numfocus.org. To view this discussion on the web visit https://groups.google.com/a/numfocus.org/d/msgid/projects/CAJLwxPEWW72wiLQj… <https://groups.google.com/a/numfocus.org/d/msgid/projects/CAJLwxPEWW72wiLQj…> .

1 0

camera.__repr__() and associated docs
by Steiner, Andrew (Andrew W. Steiner) Dec. 6, 2019

Dec. 6, 2019

Hello all, This message is a follow-up of a discussion from yt-users. I was having problems understanding the operation of camera.rotate() (and camera.yaw() which is just a wrapper). I took a look at the code again, no rotation of any kind changes the camera.focus object, which again I find counterintuitive. Focus appears to be set and used in e.g. camera.__init__() but then never used later. Thus, my idea would be to update camera.__repr__() to show something more informative, such as camera.lens.origin and/or possibly some information from camera.orientation, and then explain somewhere in the docs what the difference between that and camera.position is. It is important for me to be able to determine what the camera is doing because I am plotting text labels in the 3D volume and I want to move the text labels while moving the camera. Of course, I'm sure other people have reasons for wanting the camera properties as well. Also, If there's a standard projective geometry reference which has a description of these things in the same language as the yt implementation somewhere I'd love to see it. I'm not sure if modifications of the camera class are part of your 4.0 work or not... Take care, Andrew -- Andrew W. Steiner Joint Faculty Asst. Prof. at UTK/ORNL https://neutronstars.utk.edu/

2 1