So I’ve been exploring the possibility of using Black and the likes to start enforcing styling standard throughout the code base.
Since this process involves changing a significant portion of it (several thousands of lines), it was suggested to me to make it into YTEP.
Here it is !
Hope you like it,
As a heads up, we're in the final stages of merging yt-4.0 into the
branch that is presently called "master" on github. So if you are
running off the mainline development, you will soon see this rather
extensive change. You may need to install additional dependencies
(notably unyt) but this should be handled by running "pip install -e
." in your yt directory.
Once this is in, we'll work to update and edit PRs to retarget them.
Most should not need much in the way of changes.
Thanks to everybody who worked so hard to make this happen!
Hi yt-users and yt-devs,
As we are getting closer to the yt-4.0 release, we could really use your
help! Do you have an issue with yt that has been bugging you? *In
particular we are looking for API issues:* are there ways that using yt is
inconsistent? Does an argument that you use in one function differ in
another one (e.g. using `axes` in one and `ax` in another? or ds working
for some plotting functions but ad required for others?)? Or would you
expect to be able to use a function on a yt object and it doesn't work the
way you're expecting?
*Please add any issues you have to github! *
Be as detailed as you can, but don't worry--if someone is confused about
the problem, they will ask you!
*It is important to do this now, so big API changes are added before the
yt-4.0 release! *This will allow them to be better tested for a better yt!!
*(fine print: remember, we all want yt to be perfect, but with limited
person-hours, the yt-4.0 developers will do the best they can. Please
don't be discouraged if your issue isn't solved right away! Also, if you
don't know if your issue falls under "API" you can always add it so
everyone knows about it, even if it doesn't get pushed in the yt-4.0
Dr. Stephanie Tonnesen
Associate Research Scientist
CCA, Flatiron Institute
New York, NY
We have quite a few PRs waiting on merging for the master/4.0 merge. Once
that's finished, we'll have a lot of new features that we can merge since
they're approved. I'd like to start a discussion about what else we need to
do to get the 4.0 release out the door. We have some milestones that we
constructed for the 4.0 release last winter:
We also have other things that have been added since then. I think it would
be good to have a check in with the devs to see if we still want:
- all of these features in 4.0,
- if we should make a 4.1 milestone and move some of them, and
- whether we want to do a beta release of 4.0 once the merge happens.
It'd be nice to get this discussion going, so I've selected several times
for next week in a poll. Please respond with your availability if you're
interested in this discussion; this is a big community push and all of your
voices are important for this release!
Doodle Poll: https://doodle.com/poll/68xn2b25cang4ckb
Dear yt-users and yt-dev,
My apologies for repeated in-list and cross-list posts!
I'd like to remind everybody that the 2020 John Hunter Excellence in
Plotting Contest submission deadline is on June 01 -- only a few days away. We
welcome and look forward to your submissions!
In memory of John Hunter, we are pleased to announce the John Hunter
Excellence in Plotting Contest for 2020. This open competition aims to
highlight the importance of data visualization to scientific progress and
showcase the capabilities of open source software.
Participants are invited to submit scientific plots to be judged by a
panel. The winning entries will be announced and displayed at SciPy 2020 or
announced in the John Hunter Excellence in Plotting Contest website and
John Hunter’s family are graciously sponsoring cash prizes for the winners
in the following amounts:
1st prize: $1000
2nd prize: $750
3rd prize: $500
Entries must be submitted by June 1st to the form at
Winners will be announced at Scipy 2020 or publicly on the John Hunter
Excellence in Plotting Contest website and youtube channel
Participants do not need to attend the Scipy conference.
Entries may take the definition of “visualization” rather broadly.
Entries may be, for example, a traditional printed plot, an interactive
visualization for the web, a dashboard, or an animation.
Source code for the plot must be provided, in the form of Python code
and/or a Jupyter notebook, along with a rendering of the plot in a widely
used format. The rendering may be, for example, PDF for print, standalone
original data can not be shared for reasons of size or licensing, "fake"
data may be substituted, along with an image of the plot using real data.
Each entry must include a 300-500 word abstract describing the plot and
its importance for a general scientific audience.
Entries will be judged on their clarity, innovation and aesthetics, but
most importantly for their effectiveness in communicating a real-world
problem. Entrants are encouraged to submit plots that were used during the
course of research or work, rather than merely being hypothetical.
SciPy and the John Hunter Excellence in Plotting Contest organizers
reserves the right to display any and all entries, whether prize-winning or
not, at the conference, use in any materials or on its website, with
attribution to the original author(s).
Past entries can be found at https://jhepc.github.io/
Questions regarding the contest can be sent to jhepc.organizers(a)gmail.com
John Hunter Excellence in Plotting Contest Co-Chairs