Weekly GitHub Report for Matplotlib: June 02, 2025 - June 09, 2025 (12:02:41)
Weekly GitHub Report for Matplotlib
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is v3.10.1
1.2 Version Information:
Released on February 27, 2025, this first bugfix update for the 3.10.x series addresses several issues, including respecting array alpha in image interpolation, removing md5 usage for FIPS compliance, and fixing various plotting and figure handling bugs, alongside documentation enhancements.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- [Bug]: Misalignment of Labels and Incorrect Density Values in
ax.hist()for Categorical Variables: This issue highlights a bug in theax.hist()function of Matplotlib when used with categorical variables and thedensity=Trueparameter, leading to incorrect density computations due to the internal conversion of categories to integers, which affects the expected sum of column heights. Additionally, the issue addresses the misalignment of labels, as the function does not position them accurately at the center of the bars, complicating the process of plotting labels correctly due to the lack of documentation on the category-to-integer conversion process. - [MNT]: Ease building just one Sphinx Gallery example file: This issue addresses the challenge of efficiently building a single Sphinx Gallery example file, which currently requires a lengthy process through
make htmlormake html-skip-subdirs, often resulting in numerous unhelpful warnings. The proposed solution involves updating the documentation to provide clearer guidance on building individual files and potentially adding a new build target in the Makefile to streamline the process, thereby making it more accessible for developers, especially beginners, who need to frequently preview their work. - [ENH]: Parse "\limits" in mathtext: This issue pertains to a bug in the matplotlib library's mathtext module, where the parsing of LaTeX expressions containing the "\limits" command is not functioning as expected. The user reports that when attempting to render an integral expression with "\limits" to position subscripts and superscripts above and below the integral sign, a ParseFatalException error occurs, indicating that the "\limits" command is not recognized by the parser.
- [ENH]: Fix precision displayed by LogFormatter.format_data_short: This issue addresses the need to enhance the LogFormatter in a GitHub project by ensuring that it displays mouse cursor values with a precision that matches the cursor pointing accuracy, similar to the existing functionality for linear formatters. The problem has been open for over 423 days, and while a solution has not yet been proposed, the enhancement would improve the consistency and usability of the tool's interface.
- [Bug]:
ax.transDatadoes not honor data limits: This issue highlights a bug in Matplotlib where theax.transDatatransformation does not automatically update to reflect changes in data limits (xlimandylim) when new data is added to the axes, contrary to what the documentation suggests. The user reports that this discrepancy requires manual intervention to update the data limits, which is confusing and suggests either a need for documentation clarification or an improvement in the functionality to ensuretransDataalways uses the latest data limits.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 0
Summarized Issues:
As of our latest update, there were no issues closed in the project this week.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed issues with discussions going on within the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 0
As of our latest update, there are no open pull requests for the project this week.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 0
As of our latest update, there are no closed pull requests for the project this week.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed pull requests with discussions going on within the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| jklymak | 1 | 1 | 3 | 24 |
| story645 | 6 | 0 | 0 | 22 |
| anntzer | 13 | 9 | 0 | 5 |
| timhoffm | 8 | 0 | 0 | 12 |
| rcomer | 1 | 0 | 0 | 14 |
| QuLogic | 4 | 0 | 0 | 8 |
| tacaswell | 1 | 0 | 0 | 8 |
| oscargus | 3 | 2 | 1 | 2 |
| matthewfeickert | 4 | 0 | 2 | 2 |
| MiniX16 | 6 | 1 | 0 | 0 |