beeware / duvet Goto Github PK

View Code? Open in Web Editor NEW

53.0 53.0 16.0 51 KB

A GUI tool for visualizing coverage data.

License: BSD 3-Clause "New" or "Revised" License

Python 100.00%

duvet's Introduction

BeeWare

BeeWare is a collection of tools and libraries for building and distributing native applications in Python.

For an introduction to the full BeeWare suite, we recommend running the BeeWare Tutorial.

Community

You can talk to the BeeWare community through:

We foster a welcoming and respectful community as described in our BeeWare Community Code of Conduct.

Contributing

If you experience problems with BeeWare, log them on GitHub. If you want to contribute code, please fork the code and submit a pull request.

Translations

We manage translations using Weblate.

If you'd like to contribute to the translation effort, join the #translations channel on Discord and introduce yourself!

duvet's People

Contributors

Stargazers

Watchers

Forkers

peteraa kampfschlaefer funkybob glasnt adamchainz jrabbit schinckel dec0dedab0de akubera techdragon doismellburning nagyist stevemolloy gridl jacebrowning

duvet's Issues

Contributing: A bazillion trivial pull-requests, or one ginormous one?

I'm very interested in contributing to Duvet, but I'm very new at this and am wondering how the devs would prefer me to work. Obviously the two extremes I used in the title of this issue are wrong, but what would be best?

Given that Duvet isn't a very active repo, my guess is that the lead dev would rather read a few large(ish) pull requests than swim through loads of small proposals with semi-trivial changes. Is that true?

What would you recommend?

New release needed.

I have some coverage data. I need to view it.

PyBee has a coverage tool, I think.

Head to PyBee
Browse a bit
Find Tools > Duvet
Head to the docs, see Quickstart
Think, "That's me"

(django-filter)~/Documents/Django-Stack/django-filter (pr/634)$ pip install duvet
Collecting duvet
  Downloading duvet-0.1.2.tar.gz
Collecting coverage (from duvet)
  Downloading coverage-4.3.4-cp35-cp35m-macosx_10_10_x86_64.whl (168kB)
    100% |████████████████████████████████| 174kB 45kB/s 
Collecting tkreadonly (from duvet)
  Downloading tkreadonly-0.6.1-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): Pygments>=1.5 in /Users/carlton/ve/django-filter/lib/python3.5/site-packages (from tkreadonly->duvet)
Building wheels for collected packages: duvet
  Running setup.py bdist_wheel for duvet ... done
  Stored in directory: /Users/carlton/Library/Caches/pip/wheels/db/81/20/3ff47bc04ae68f252e8fe5ae9964bc969c2b35a4e6a88c80f8
Successfully built duvet
Installing collected packages: coverage, tkreadonly, duvet
Successfully installed coverage-4.3.4 duvet-0.1.2 tkreadonly-0.6.1
(django-filter)~/Documents/Django-Stack/django-filter (pr/634)$ duvet
Traceback (most recent call last):
  File "/Users/carlton/ve/django-filter/bin/duvet", line 7, in <module>
    from duvet.__main__ import main
  File "/Users/carlton/ve/django-filter/lib/python3.5/site-packages/duvet/__main__.py", line 4, in <module>
    from Tkinter import *
ImportError: No module named 'Tkinter'
(django-filter)~/Documents/Django-Stack/django-filter (pr/634)$

Hmmm.

Fortunately StackOverflow has me covered.

Edit duvet/__main__.py:

try:
    from Tkinter import *   
except ImportError:
    from tkinter import *

Try again:

$ duvet
Traceback (most recent call last):
  File "/Users/carlton/ve/django-filter/bin/duvet", line 7, in <module>
    from duvet.__main__ import main
  File "/Users/carlton/ve/django-filter/lib/python3.5/site-packages/duvet/__main__.py", line 4, in <module>
    from Tkinter import *
ImportError: No module named 'Tkinter'
(django-filter)~/Documents/Django-Stack/django-filter (pr/634)$ bbedit /Users/carlton/ve/django-filter/lib/python3.5/site-packages/duvet/__main__.py
(django-filter)~/Documents/Django-Stack/django-filter (pr/634)$ duvet
Traceback (most recent call last):
  File "/Users/carlton/ve/django-filter/bin/duvet", line 7, in <module>
    from duvet.__main__ import main
  File "/Users/carlton/ve/django-filter/lib/python3.5/site-packages/duvet/__main__.py", line 16, in <module>
    from duvet.view import MainWindow
  File "/Users/carlton/ve/django-filter/lib/python3.5/site-packages/duvet/view.py", line 425
    except Exception, e:
                    ^
SyntaxError: invalid syntax

This'll take longer than I thought. 🙂

$ deactivate
$ pyenv shell 2.7
$ pip install duvet
...
$ duvet
...
ImportError: cannot import name CodeParser

Hang on, I saw that on GiHub, that's #3

Right:

$ pip install -e git+https://github.com/pybee/duvet.git#egg=duvet
$ duvet

And we're in business. 👍

Good work! Thank you! Glad to be here. Happy to help as I get into it. Think a PyPI release would be worth the effort. 🙂

Duvet refuses to let go of files

Background

Running a Django project (1.6.11 - making the upgrade, please no shaming.) with duvet 0.1.2, coverage 3.7.1 and python 2.7.10.

Issue

This probably isn't a bug per se but I deleted a file from my repo (an admin.py file that no one used), ran coverage.py (which complained a bit that the file was missing) but when running duvet with duvet I encountered an error message alert:

Couldn't load coverage data -- data file may be corrupted (Error was: No source for code: '/path/to/my/app/admin.py': [Errno 2] No such file or directory: '/path/to/my/app/admin.py')

If I click retry, the behavior is as expected - it still can't find the file, nothing crazy there.

If I click cancel it exits duvet. I would assume that this is so duvet doesn't end up in some strange error state but maybe this type of exception is worth handling so I can still interact with my coverage reports.

Really loving the PyBee suite so far, thanks!

Coverage 4.0 support

Seems some things were changed in 4.0:

Traceback (most recent call last):
  File "/usr/local/bin/duvet", line 7, in <module>
    from duvet.__main__ import main
  File "/usr/local/lib/python2.7/dist-packages/duvet/__main__.py", line 10, in <module>
    from duvet.view import MainWindow
  File "/usr/local/lib/python2.7/dist-packages/duvet/view.py", line 14, in <module>
    from coverage.parser import CodeParser
ImportError: cannot import name CodeParser

Fails to Start on Windows

Looks like the problem is that directory paths need to be translated (/ to ) for Windows (or maybe escaped).

Traceback (most recent call last):
  File "C:\Users\Tom\Envs\project\Scripts\duvet-script.py", line 8, in <module>
    load_entry_point('duvet==0.1.1', 'console_scripts', 'duvet')()
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\__main__.py", line 35, in main
    view = MainWindow(root, options)
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\view.py", line 78, in __init__
    self._setup_main_content()
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\view.py", line 150, in _setup_main_content
    self._setup_file_tree()
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\view.py", line 164, in _setup_file_tree
    self.file_tree = FileView(self.file_tree_frame, normalizer=self.filename_normalizer, root=self.base_path)
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\widgets.py", line 45, in __init__
    os.path.walk(self.root, self._visitor, None)
  File "C:\Users\Tom\Envs\project\Lib\ntpath.py", line 259, in walk
    func(arg, top, names)
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\widgets.py", line 49, in _visitor
    self.insert_dirname(dirname)
  File "C:\Users\Tom\Envs\project\Lib\site-packages\duvet\widgets.py", line 90, in insert_dirname
    tags=['directory']
  File "C:\Python27\Lib\lib-tk\ttk.py", line 1359, in insert
    "-id", iid, *opts)
_tkinter.TclError: Item c:/clientwork not found