Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / zeekay/decorum issues and pull requests

#30 - Implement __get__ to allow instance methods to be decorated

Pull Request - State: closed - Opened by nathanielford almost 8 years ago

#29 - Refactored README

Pull Request - State: closed - Opened by benoitbryon over 9 years ago - 1 comment

#28 - Decorum's magic 'self._wrapped' should not be part of 'wraps'

Issue - State: closed - Opened by benoitbryon over 9 years ago - 6 comments

#27 - Setup 'assigned' option in 'init' (was in '__init__')

Pull Request - State: closed - Opened by benoitbryon over 9 years ago

#26 - Decorum.assigned should be managed in init()

Issue - State: closed - Opened by benoitbryon over 9 years ago - 1 comment

#25 - Introduce customizable Decorum.call()

Pull Request - State: closed - Opened by benoitbryon over 9 years ago - 2 comments

#24 - Decorum.__call__() should first check self._wrapped

Issue - State: open - Opened by benoitbryon over 9 years ago

#23 - Decorum class runs wrapped function via a `call()` method

Issue - State: closed - Opened by benoitbryon over 9 years ago - 2 comments

#22 - Promote subclassing Decorum instead of decorating classes

Pull Request - State: closed - Opened by benoitbryon over 9 years ago - 2 comments

#21 - Inherit from class Decorum, instead of using @decorator

Issue - State: closed - Opened by benoitbryon over 9 years ago - 4 comments

#19 - assigned=None preserves name and doc of decorator

Issue - State: closed - Opened by benoitbryon over 9 years ago - 1 comment

#18 - 'assigned' option defaults to functools.WRAPPER_ASSIGNMENTS

Pull Request - State: closed - Opened by benoitbryon over 9 years ago

#17 - 'assigned' option defaults to functools.WRAPPER_ASSIGNMENTS

Issue - State: closed - Opened by benoitbryon over 9 years ago

#16 - Fixed doctests around 'assigned'

Pull Request - State: closed - Opened by benoitbryon over 9 years ago - 5 comments

#15 - Make sure there are doctests in README

Pull Request - State: closed - Opened by benoitbryon over 9 years ago

#14 - tests/doctests.py report errors, but pass

Issue - State: closed - Opened by benoitbryon over 9 years ago

#13 - Added 'url' to setup script

Pull Request - State: closed - Opened by benoitbryon over 9 years ago

#12 - Missing url in setup

Issue - State: closed - Opened by benoitbryon over 9 years ago

#11 - Add CONTRIBUTORS or update README.

Issue - State: closed - Opened by zeekay over 10 years ago - 3 comments

#10 - Refs #8 - In README, converted examples into doctests

Pull Request - State: closed - Opened by benoitbryon over 10 years ago - 3 comments

#9 - Add Sphinx documentation

Issue - State: open - Opened by benoitbryon over 10 years ago - 2 comments

#8 - Increase code coverage to 100% (or nearly)

Issue - State: open - Opened by benoitbryon over 10 years ago - 2 comments

#7 - Added minimal support for Python 3.3 and 3.4

Pull Request - State: closed - Opened by benoitbryon over 10 years ago - 4 comments

#6 - Support Python>=3.3

Issue - State: closed - Opened by benoitbryon over 10 years ago

#5 - Introduced Tox, Travis and CONTRIBUTING

Pull Request - State: closed - Opened by benoitbryon over 10 years ago - 3 comments

#4 - CONTRIBUTING.rst provides contribution guidelines

Issue - State: closed - Opened by benoitbryon over 10 years ago

#3 - Travis runs Tox

Issue - State: closed - Opened by benoitbryon over 10 years ago

#2 - Tox runs tests

Issue - State: closed - Opened by benoitbryon over 10 years ago

#1 - What is project status?

Issue - State: closed - Opened by benoitbryon over 10 years ago - 3 comments