Add ascii/no-color progressbar

[ant31]

Hi
I wanted a pytest-sugar without utf8 nor color, and the pytest --color=no was ignored by pytest-sugar. I ran into the same issue than #91
Even if themes can be created via the conf file, having an upstream one that match --color=no is usefull.

it looks like:

test_sugar.py sx...                    55% [=====   ]
test_sugar.py sx........s             100% [========]

Another thing added (that can be separated from this commit)
is the option --show-count to display the current tests-count/test-taken

 /test/test_api_usage.py ........................... 48% [=====     ][1072/2226]
                         ........................... 49% [=====     ][1099/2226]
                         ........................... 51% [======    ][1126/2226]
                         ........................... 52% [======    ][1153/2226]

[codecov-io]

Current coverage is 67.58% (diff: 47.61%)

Merging #101 into master will decrease coverage by 0.83%

@@             master       #101   diff @@
==========================================
  Files             4          4          
  Lines           380        398    +18   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits            260        269     +9   
- Misses          120        129     +9   
  Partials          0          0          

Powered by Codecov. Last update 306c61e...0b01777

[blueyed]

Please rebase it on master, which uses pytest 3.0 now.

[ant31]

it's rebased

[ant31]

Do I remove this version bump?

[blueyed]

No, it looks like you add it (and shouldn't) - master is at 0.7.1..

[ant31]

@blueyed I removed the version change. it should be good now

[Teemu]

Thank you for your contribution.

However, at this point I am focusing on:

1. improving code quality (the current code base is frankly a mess. It is not surprising since this project started as a hack and pytest code is frankly quite hard to understand)
2. improving our test coverage (how ironic for py.test plugin)
3. making things work (lots of issues!)

so this PR shall wait until then.

[ant31]

@Frozenball / @blueyed I would expect small project to be more open to contribution, especially when issue/feature request have been reported several times.

I close this, I'm good with using my fork.
thanks

[blueyed]

@ant31
No need to close it out of frustration.

btw: I am a contributor only myself.

[Teemu]

I am sorry if you feel ignored. I have very little time for personal projects nowadays and I don't like to spend that little time with stuff that doesn't bring joy to me. Maintaining code, checking pull requests and doing releases is work and is not as simple as pressing a button if you want to do it right. If your fork works, great! Pytest API has been pretty stable for a long time so there really isn't any urgency to get it upstream I think. On Oct 23, 2017 14:31, "Daniel Hahler" <notifications@github.com> wrote: @ant31 <https://github.com/ant31> No need to close it out of frustration. btw: I am a contributor only myself. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#101 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADQMmnzMW-WoD-X-GU642IhKZpC4sRQks5svHkVgaJpZM4K8Ak0> .

[blueyed]

I understand.
But still leave if open for others to pick it up, and maintainers to merge it eventually.

Are you trying to get PR zero? For me https://github.com/pulls shows 208 open PRs currently, but you do not have to check that page.
Let it rot and getting some attention even after years I would say.
It's different from maintainers wanting to get the queue down, where I can understand it better to close PRs.

Anyway, let's not waste our precious time in this discussion.