- Notifications
You must be signed in to change notification settings - Fork 7.1k
ENH+BF: fix up of some tests/docs to pass with python2.7, testing on travis, consistent shebanging, #144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
…unction from future for chaining_method.py
yarikoptic commented May 17, 2016
ok -- with a small tune up (could not do also here is coverage report from https://codecov.io/gh/yarikoptic/python-patterns (also enable for your repo, and then can add a badge or two to your README etc) |
fkromer commented May 17, 2016
I did not get why lines 81, 61 and 91 in https://codecov.io/gh/yarikoptic/python-patterns/src/ef3dbe3b17b10f9926607f98fa10b1913c61476f/test_hsm.py are not covered... |
yarikoptic commented May 17, 2016
Pushed more fixes and trying to enhance testing by actually running all of the scripts. It required also fixing 3-tier.py by reverting 69b507b -- descriptors must be bound to classes, not to instances, thus that change broke the "pythonish" idea completely. Could be redone without relying on Python descriptors at the instance level |
…tment to UI and Business logic for injecting dependencies" This reverts commit 69b507b.
yarikoptic commented May 17, 2016
woohoo -- tests pass again (although I have dropped pypy* for now, was getting stuck), and coverage is whooping 93%: see https://codecov.io/gh/yarikoptic/python-patterns on what to improve. You can easily get 100% with little effort! |
yarikoptic commented May 17, 2016
On Tue, 17 May 2016, thinwybk wrote:
ain't auto coverage great?! ;) my guess, is that since it is assertRaises, is that previous lines cause Yaroslav O. Halchenko |
yarikoptic commented May 17, 2016
On Tue, 17 May 2016, Yaroslav Halchenko wrote:
ok -- did that for that file... there might be more... Yaroslav O. Halchenko |
yarikoptic commented May 17, 2016
fkromer commented May 17, 2016
Thanks a lot :) |
fkromer commented May 17, 2016
Could you merge https://github.com/fkromer/python-patterns/tree/test_proxy (#139) into your fork to make sure these tests are still running ;) |
* pr-139: change: refactor (work -> talk) change: refactoring self->cls
yarikoptic commented May 17, 2016
On Tue, 17 May 2016, thinwybk wrote:
heh -- only for you and only today... merged, fixed it up the Yaroslav O. Halchenko |
…version specific import of StringIO (breaks on 2.x with io.StringIO)
fkromer commented May 17, 2016
Thanks! That's just how it is (right now). :) |
faif commented May 18, 2016
Hi, Thanks for your contributions. Sorry for not taking any actions yet but I'm ill. I will check everything after recovering. Kind regards,
|
yarikoptic commented May 18, 2016
sure -- no rush. Get better! |
I really loved the idea and the collection so decided to contribute a bit ;)
https://travis-ci.org/yarikoptic/python-patterns/builds/130877280
should eventually reflect current state of things -- either tests pass as is or more things to be done
Please enable travis for your project @faif -- it is easy, just go to http://travis-ci.org, authenticate through github, click toggle for this repository
I have already complained in #143 about necessity to have clear copyright/license statement(s) so this code could e.g. be actually used/redistributed etc. Ideally the most permissive license (BSD-2 or -3 or MIT) would be the best fit.
Also would be nice to make all code PEP8 compliant. I have added call to flake8 in travis.yml but ignoring its failure atm. Didn't want to introduce big "stylistic" changes without "go ahead"