Introduce new option to skip header and summary
See original GitHub issue#6454 reminds me that sometimes we want to skip header and summary entirely from the output (posting examples online for example). Currently the only way to skip headers is to use -q
, but this is a global option which affects many other parts (like diff and progress reporting).
How about a --lean-terminal
or something which only skips both header and summary?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Skip header rows on SQL Data Warehouse PolyBase load
Azure SQL Data Warehouse users can now skip these rows by using the First_Row option in the delimited text file format for PolyBase...
Read more >Import CSV Files As Pandas DataFrame With skiprows ...
You can skip rows of any range using a 'for loop'. This option can be very useful at times. I am using a...
Read more >How to read Pandas csv file with no header - Edureka
Using only header option, will either make header as data or one of the data as header. So, better to use it with...
Read more >SQLite3 Import CSV & exclude/skip header - Stack Overflow
I would have expected there to be an easy option to skip the header row when calling . import as having header rows...
Read more >Skip first rows excel and read headers - Alteryx Community
Solved: Hello, I am using Salesforce data and when I export the data to excel it has first rows showing which filters were...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s correct, I’m a -.5 on this change because I find the header very useful in bug reports and don’t think omitting it is very helpful.
I also have a general preference for less config options, because the more we add the harder it becomes to learn pytest or to write exhaustive self-tests and reliable plugins.
As both a user and a maintainer, it’s occasionally but very very useful to be able to see what version of Python, pytest, and plugins are running. IMO it’s not worth endangering this to save just two lines of space in the terminal!