| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'input_function'
When no parameter was given to the class, None was used as the `input`.
It used to work because when `input` (the argument) was None `raw_input` of six
was used instead. (-> self._input = input or raw_input).
Now that six has been dropped, we cannot have `input=None` in the arguments list
anymore and use the builtin `input` at the same time.
This patch suggests to deprecate this argument in favor of a new one called
`input_function`. If no `input_function`, let's use the `input` builtin.
For backward compatibility, if `input` should be given, it's caught in the
`kwargs` and used as `input_function`, and a deprecation warning is shown.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
logilab-pytest has a side effect of printing DeprecationWarnings by default,
when running modutils tests without logilab-pytest binary this fail.
In debian package we run python3 -m "logilab.common.pytest" and thus
DeprecationWarning are not displayed and tests fail.
Fix this by ensuring DeprecationWarning are displayed before running tests of
unittest_modutils.py
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This avoid having a python2 pip pulling our python3 only package.
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
time.clock is deprecated since python 3.3 and will be removed in python 3.8
this patch breaks backward compatibility with python < 3.3.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
So we can drop most of the debian/rules file.
Somes tests are broken so disable tests for now.
|
|/
|
|
| |
Followup b05f25 where doc directory has been renamed to docs but wasn't included in the sdist.
|
|
|
|
|
|
|
|
|
| |
In both ConfigurationMixIn and OptionsManager2ConfigurationAdapter.
Otherwise a child-class defining it's own __getitem__ wouldn't be called.
In ConfigurationMixIn.get, also catch for OptionError like before.
We could think about caching OptionError in __getitem__ but there's test
asserting this method can raise OptionError, so...
|
|
|
|
|
|
| |
The README is used in setup.py to generated the long description. And
this description must contain only plain rst in order the upload to be
accepted by PyPI (https://pypi.org/help/#description-content-type).
|
| |
|
| |
|
|
|
|
|
| |
The system has changed and we lack resources to
maintain it in Debian.
|
| |
|
|
|
|
|
|
| |
Otherwise, the error message looks like:
invalid unit minutes. valid units are dict_keys(['d', 'h', 'ms', 's', 'min'])
|
|
|
|
|
|
|
|
|
| |
The original KeyError comes from 57e242dffe89 which no justification. I
believe it was meant to be a ValueError as in other errors in this
function. Also, _ensure_correctly_typed() in cubicweb/web/formfields.py
will catch ValueError.
Adding a test for this.
|
|
|
|
|
| |
We use python2 since building the documentation with python3 does not
work at the moment.
|
| |
|
| |
|
|
|
|
| |
readthedocs likes documentation to be in a docS folder.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rationnal to do this migration are:
* be able to host the documentation on readthedocs.org, right now, according to
the README, the user needs to built it locally to be able to read it
* epydoc is not maintained anymore
* sphinx generally offer a better user experience and allow to write real
documentation instead of just generating an API
* it was quick to do with sphinx-apidoc and seems worth it to be able to put it
online
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In python 3 "getargspec" is deprecated and "getfullargspec" is added.
The only difference between these two functions is that the "keywords"
tuple's field is renamed into "varkw" (which does not impact us in this
case).
|
|
|
|
| |
The former would select any Python 3 interpreter.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The "options" iteration variable hid the original function
parameters, therefore only the options of the last group
were registered.
Rename the iteration variable and everything's fine.
|
| |
|
|
|
|
|
|
| |
Use io.open() which has a consistent interface between Python 2 and Python 3.
In particular, `newline` parameter is meant to control "universal new lines"
and it is None by default so we don't need to specify it.
|
|
|
|
|
|
| |
From the context, using action[0] seems correct. The problem comes from
changeset 0a22ff6e5207 and shows up when using "option_added()" CubicWeb
migration command.
|
| |
|