Lines Matching +full:git +full:- +full:core
10 …/kubernetes/community/blob/master/contributors/guide/pull-requests.md#best-practices-for-faster-re…
20 - The feature must be documented in both the API and narrative
23 - The feature must work fully on the following CPython versions:
26 - The feature must not add unnecessary dependencies (where
34 You'll have to create a development environment using a Git checkout:
36 - While logged into your GitHub account, navigate to the
37 ``python-api-core`` `repo`_ on GitHub.
39 - Fork and clone the ``python-api-core`` repository to your GitHub account by
42 - Clone your fork of ``python-api-core`` from your GitHub account to your local
44 as ``hack-on-python-api-core``. E.g.::
47 $ git clone git@github.com:USERNAME/python-api-core.git hack-on-python-api-core
48 $ cd hack-on-python-api-core
49 # Configure remotes such that you can pull changes from the googleapis/python-api-core
51 $ git remote add upstream git@github.com:googleapis/python-api-core.git
53 $ git fetch upstream
54 $ git merge upstream/main
62 .. _repo: https://github.com/googleapis/python-api-core
69 - To test your changes, run unit tests with ``nox``::
70 $ nox -s unit
72 - To run a single unit test::
74 $ nox -s unit-3.10 -- -k <name of test>
89 install ``python-dev`` and try again.
92 $ sudo apt-get install python-dev
97 - We use the automatic code formatter ``black``. You can run it using
100 $ nox -s blacken
102 - PEP8 compliance is required, with exceptions defined in the linter configuration.
104 any non-compliant code via::
106 $ nox -s lint
108 - In order to make ``nox -s lint`` run faster, you can set some environment
114 By doing this, you are specifying the location of the most up-to-date
115 version of ``python-api-core``. The the suggested remote name ``upstream``
119 - This repository contains configuration for the
120 `pre-commit <https://pre-commit.com/>`__ tool, which automates checking
124 .. code-block:: bash
126 $ pre-commit install
127 pre-commit installed at .git/hooks/pre-commit
131 - Many unit tests use a helper method, ``_call_fut`` ("FUT" is short for
132 "Function-Under-Test"), which is PEP8-incompliant, but more readable.
133 Some also use a local variable, ``MUT`` (short for "Module-Under-Test").
140 - The codebase *must* have 100% test statement coverage after each commit.
141 You can test coverage via ``nox -s cover``.
154 $ nox -s docs
170 - To run sample tests, you can execute::
174 $ nox -s py-3.8
178 $ nox -s py-3.8 -- -k <name of test>
188 ``https://github.com/googleapis/python-api-core/blob/main/CONTRIBUTING.rst``)
191 .. _description on PyPI: https://pypi.org/project/google-api-core
200 - `Python 3.6`_
201 - `Python 3.7`_
202 - `Python 3.8`_
203 - `Python 3.9`_
204 - `Python 3.10`_
215 .. _config: https://github.com/googleapis/python-api-core/blob/main/noxfile.py
221 - Encouraging use of newest versions of Python 3
222 - Taking the lead of `prominent`_ open-source `projects`_
223 - `Unicode literal support`_ which allows for a cleaner codebase that
226 …inent: https://docs.djangoproject.com/en/1.9/faq/install/#what-python-version-can-i-use-with-django
228 .. _Unicode literal support: https://www.python.org/dev/peps/pep-0414/
249 - **If you are an individual writing original source code** and **you own the
251 `individual CLA <https://developers.google.com/open-source/cla/individual>`__.
252 - **If you work for a company that wants to allow you to contribute your work**,
254 `corporate CLA <https://developers.google.com/open-source/cla/corporate>`__.