matplotlib / matplotlib/cheatsheets
`tight_layout` versus `constrained_layout`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.7k
- Forks
- 916
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/matplotlib/cheatsheets/blob/329e0ba94d06c2a9f6af4600af9a25dcac6d9f5a/handout-tips.tex#L215 calls out `tight_layout` in particular. Is there a reason to not also call out `constrained_layout`? In general `constrained_layout` is more "automatic".
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open handout-tips.tex at line 215 and review the existing tight_layout callout in the context of constrained_layout. Check the Matplotlib documentation or examples to determine whether both should be mentioned; done means the cheat sheet accurately explains the relevant layout guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matplotlib, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100