Mailman 3 January 2019 - Matplotlib-devel

matplotlib qt trading terminal; finance sample
by cerberus cerberus April 19, 2019

April 19, 2019

Hello Lists, I will park my matplotlib source code for a trading terminal written in python2/matplotlib/pyqt4 here in case one needs reasonable good reference code about how to plot financial candlestick charts and indicators with matplotlib and qt. A sample of a combined orderbook for several crypto currency exchanges is included, see attached screenshot. Google Notice: Wavetrend Robot. With Kind Regards, Aktiophi

3 3

Summer stundents
by Thomas Caswell Feb. 4, 2019

Feb. 4, 2019

Folks, On this weeks call we discussed if we want to take summer students this year (either through GSOC or running the JDH summer fellowship again). Is anyone able and interested in mentoring this summer? Notes from the call: https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AWH9pSDlOSvrxXBVPR… Tom -- Thomas Caswell tcaswell(a)gmail.com

1 1

Documnetation summit
by Thomas Caswell Jan. 21, 2019

Jan. 21, 2019

Folks, We are planning to have a documentation summit in late spring in Boulder. The work product of this summit is a roadmap of what we want to do with the documentation going forward and a proposal to hire a technical writer to implement it. Who is interested in attending? We do have a small budget for travel. notes from call: https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AWH9pSDlOSvrxXBVPR… Tom -- Thomas Caswell tcaswell(a)gmail.com

1 0

Students of ASPP contributing to Matplotlib
by Nelle Varoquaux Jan. 21, 2019

Jan. 21, 2019

Hello everyone, A bit of a last minute heads up… I'm at the advanced scientific programming in python summer school, and the instructor of the git & github lesson was looking for a package for students to do a small contribution (to see the workflow). As in 2016, I suggested small documentation changes to Matplotlib: we have selected 15 examples that could be improved, either in the title, either merging two examples that showcase similar, or just a better description. This means you might see 15 pull requests appear on the Matplotlib repository, by people who have experience in scientific Python, but no experience in contributing to open-source software. The students are pair-programming, so the authors of commits of each the pull request might not reflect an actual developer. The changes should be minimal, and I expect to be able to review and merge pull requests fairly quickly if the CI passes. If not, help in reviewing and merging is appreciated (but don't feel obliged to)! Thanks, Nelle

2 2

Proposal to amend the PR merge rules
by Antony Lee Jan. 17, 2019

Jan. 17, 2019

Hi all, During the weekly dev call, I proposed to amend the PR merge rules, following an initial comment on Github [ https://github.com/matplotlib/matplotlib/pull/13173#issuecomment-453921220]. There was general agreement among the devs present (Tom, Hannah, Jody, and myself), so I'm putting it here for discussion. The objective of this change is to prevent "uncontroversial but uninteresting" PRs from falling into oblivion, and try to decrease the size of the open PR stack. The current rule is that a PR needs positive reviews (from two committers, and excluding the author if a committer) to be merged, except that doc-only PRs (docstrings, rst) only needs a single positive review. I am proposing that, if a (non-doc) PR already has one positive review, but no activity on that PR has occurred for two weeks (exact time interval up to bikeshedding) [Jody suggests: and the PR has 100% code coverage], then a committer (either the first reviewer, or the author if a committer) can suggest that it be merged on the basis of that single review. To do so, the "sponsor" should ping all developers (@matplotlib/developers) on that issue indicating that intent, and add a "single-review-merge" label on the PR (so that these PRs can easily be found). Committers are encouraged to review the PR to accept and merge it or reject it or request changes on it; but they can also just indicate that they consider the PR sufficiently complex that a proper second review is needed before merging, or request an extension, etc. To do so they should still leave a "reject" review, even if just saying "objecting to single-review merged; anyone can dismiss after a second review". However, if within another two weeks, no committer voiced any objection (explicitly, i.e. by rejecting), then the PR can indeed be merged on the basis of that single review. To avoid overwhelming the system, any committer can only "sponsor" a single PR at a time. Thoughts? Antony

8 20

weekly meeting
by Jody Klymak Jan. 14, 2019

Jan. 14, 2019

Hi all, Weekly meeting agenda at: https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AVqsdFqn2tYkD0LzOQ… Cheers, Jody -- Jody Klymak http://web.uvic.ca/~jklymak/

1 0

[ANN] 2019 Scipy Conference: Call for Proposals
by Nathan Goldbaum Jan. 8, 2019

Jan. 8, 2019

SciPy 2019, the 18th annual Scientific Computing with Python conference, will be held July 8-14, 2019 in Austin, Texas. The annual SciPy Conference brings together over 800 participants from industry, academia, and government to showcase their latest projects, learn from skilled users and developers, and collaborate on code development. The call for abstracts for SciPy 2019 for talks, posters and tutorials is now open. The deadline for submissions is February 10, 2019. Conference Website: https://www.scipy2019.scipy.org/ Submission Website: https://easychair.org/conferences/?conf=scipy2019 *Talks and Posters (July 10-12, 2019)* In addition to the general track, this year will have specialized tracks focused on: - Data Driven Discoveries (including Machine Learning and Data Science) - Open Source Communities (Sustainability) *Mini Symposia* - Science Communication through Visualization - Neuroscience and Cognitive Science - Image Processing - Earth, Ocean, Geo and Atmospheric Science There will also be a SciPy Tools Plenary Session each day with 2 to 5 minute updates on tools and libraries. *Tutorials (July 8-9, 2019)* Tutorials should be focused on covering a well-defined topic in a hands-on manner. We are looking for useful techniques or packages, helping new or advanced Python programmers develop better or faster scientific applications. We encourage submissions to be designed to allow at least 50% of the time for hands-on exercises even if this means the subject matter needs to be limited. Tutorials will be 4 hours in duration. In your tutorial application, you can indicate what prerequisite skills and knowledge will be needed for your tutorial, and the approximate expected level of knowledge of your students (i.e., beginner, intermediate, advanced). Instructors of accepted tutorials will receive a stipend.

1 0

Weekly calll
by Jody Klymak Jan. 7, 2019

Jan. 7, 2019

Hi all Starting in a couple of minutes if anyone is around https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AVNCXbugY4xNG6rChQ…

1 0