| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A commonly reported issue from users on Gitter is that they get an
AttributeError for an attribute that should be present. This is often
caused due to the fact that they used the `list()` method to retrieve
the object and objects retrieved this way often only have a subset of
the full data.
Add more details in the AttributeError message that explains the
situation to users. This will hopefully allow them to resolve the
issue.
Update the FAQ in the docs to add a section discussing the issue.
Closes #1138
|
| |\ \
| |/
|/| |
refactor: explicitly import gitlab.const values into top-level namespace
|
| | |
| |
| |
| | |
Update the docs to use gitlab.const to access constants.
|
| | |
| |
| |
| |
| | |
Have code use constants from the gitlab.const module instead of from
the top-level gitlab module.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are planning on adding enumerated constants into gitlab/const.py,
but if we do that than they will end up being added to the top-level
gitlab namespace. We really want to get users to start using
`gitlab.const.` to access the constant values in the future.
Add the currently defined constants to a list that should not change.
Use a module level __getattr__ function so that we can deprecate
access to the top-level constants.
Add a unit test which verifies we generate a warning when accessing
the top-level constants.
|
| |\
| |
| | |
test(cli): improve basic CLI coverage
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
chore: remove pytest-console-scripts specific config
|
| |/
|
|
|
|
|
|
|
| |
Remove the pytest-console-scripts specific config from the global
'[pytest]' config section.
Use the command line option `--script-launch-mode=subprocess`
Closes #1713
|
| |\
| |
| | |
feat(api): add support for epic notes
|
| | |
| |
| |
| |
| |
| | |
Added support for notes on group epics
Signed-off-by: Raimund Hook <raimund.hook@exfo.com>
|
| |\ \
| | |
| | | |
feat: add support for `projects.groups.list()`
|
| |/ /
| |
| |
| |
| |
| | |
Add support for `projects.groups.list()` endpoint.
Closes #1717
|
| |/ |
|
| |\
| |
| | |
chore: remove duplicate/no-op tests from meta/test_ensure_type_hints
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before we were generating 725 tests for the
meta/test_ensure_type_hints.py tests. Which isn't a huge concern as
it was fairly fast. But when we had a failure we would usually get two
failures for each problem as the same test was being run multiple
times.
Changed it so that:
1. Don't add tests that are not for *Manager classes
2. Use a set so that we don't have duplicate tests.
After doing that our generated test count in
meta/test_ensure_type_hints.py went from 725 to 178 tests.
Additionally removed the parsing of `pyproject.toml` to generate files
to ignore as we have finished adding type-hints to all files in
gitlab/v4/objects/. This also means we no longer use the toml library
so remove installation of `types-toml`.
To determine the test count the following command was run:
$ tox -e py39 -- -k test_ensure_type_hints
|
| |\
| |
| | |
chore: add type-hints to remaining gitlab/v4/objects/*.py files
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When attempting to add type-hints to the the 'manager' attribute into
a RESTObject derived class it would break things.
This was because our auto-manager creation code would automatically
add the specified annotated manager to the 'manager' attribute. This
breaks things.
Now check in our auto-manager creation if our attribute is called
'manager'. If so we ignore it.
|
| |\ \
| | |
| | | |
feat: remove support for Python 3.6, require 3.7 or higher
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Python 3.6 is End-of-Life (EOL) as of 2021-12 as stated in
https://www.python.org/dev/peps/pep-0494/
By dropping support for Python 3.6 and requiring Python 3.7 or higher
it allows python-gitlab to take advantage of new features in Python
3.7, which are documented at:
https://docs.python.org/3/whatsnew/3.7.html
Some of these new features that may be useful to python-gitlab are:
* PEP 563, postponed evaluation of type annotations.
* dataclasses: PEP 557 – Data Classes
* importlib.resources
* PEP 562, customization of access to module attributes.
* PEP 560, core support for typing module and generic types.
* PEP 565, improved DeprecationWarning handling
BREAKING CHANGE: As of python-gitlab 3.0.0, Python 3.6 is no longer
supported. Python 3.7 or higher is required.
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
chore: enable mypy for tests/meta/*
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
renovate is not upgrading the `black` package. There is an open
issue[1] about this.
Also change .commitlintrc.json to allow 200 character footer lines in
the commit message. Otherwise would be forced to split the URL across
multiple lines making it un-clickable :(
Use suggested work-arounds from:
https://github.com/renovatebot/renovate/issues/7167#issuecomment-904106838
https://github.com/scop/bash-completion/blob/e7497f6ee8232065ec11450a52a1f244f345e2c6/renovate.json#L34-L38
[1] https://github.com/renovatebot/renovate/issues/7167
|
| |\ \ \
| |_|/
|/| | |
chore: correct test_groups.py test
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The test was checking twice if the same group3 was not in the returned
list. Should have been checking for group3 and group4.
Also added a test that only skipped one group and checked that the
group was not in the returned list and a non-skipped group was in the
list.
|
| |\ \
| |/
|/|
| |
| | |
python-gitlab/jlvillal/mypy_merge_request_approvals
chore: add type-hints to gitlab/v4/objects/merge_request_approvals.py
|
| |/ |
|
| |\
| |
| | |
chore: check setup.py with mypy
|
| |/
|
|
|
|
|
|
| |
Prior commit 06184daafd5010ba40bb39a0768540b7e98bd171 fixed the
type-hints for setup.py. But missed removing 'setup' from the exclude
list in pyproject.toml for mypy checks.
Remove 'setup' from the exclude list in pyproject.toml from mypy checks.
|
| |\
| |
| | |
Ensure get() methods have correct type-hints
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Fix classes which don't have correct 'get()' methods for classes
derived from GetMixin.
Add a unit test which verifies that classes have the correct return
type in their 'get()' method.
|
| | |
| |
| |
| |
| | |
The 'test_mro.py' file is not really a unit test but more of a 'meta'
check on the validity of the code base.
|
| |\ \
| |/
| | |
chore: add type-hints to setup.py and check with mypy
|
| |/ |
|
| |\
| |
| | |
chore: add type-hints to gitlab/v4/objects/snippets.py
|
