[Python-modules-commits] [python-keyring] 01/02: Import python-keyring_10.0.2.orig.tar.gz
Dmitry Shachnev
mitya57 at moszumanska.debian.org
Thu Oct 20 18:12:57 UTC 2016
This is an automated email from the git hooks/post-receive script.
mitya57 pushed a commit to branch master
in repository python-keyring.
commit 89765ec7a29d3c68e51038c17143ed1480aaedfc
Author: Dmitry Shachnev <mitya57 at gmail.com>
Date: Thu Oct 20 21:09:11 2016 +0300
Import python-keyring_10.0.2.orig.tar.gz
---
.hgtags | 118 --------------------------------------
.travis-osx | 5 ++
.travis.yml | 10 +---
CHANGES.rst | 11 ++++
PKG-INFO | 59 ++++---------------
README.rst | 57 +++---------------
keyring.egg-info/PKG-INFO | 59 ++++---------------
keyring.egg-info/SOURCES.txt | 6 +-
keyring.egg-info/entry_points.txt | 3 +
setup.py | 3 +
tests/test_packaging.py | 14 +++++
11 files changed, 71 insertions(+), 274 deletions(-)
diff --git a/.hgtags b/.hgtags
deleted file mode 100644
index 061276b..0000000
--- a/.hgtags
+++ /dev/null
@@ -1,118 +0,0 @@
-eca8f4a35834f58a4008048a3c5c5c89592cb260 0.2
-24dcf507483ee9fe0f078f2d45f9a3e231d13ade remove
-24dcf507483ee9fe0f078f2d45f9a3e231d13ade remove
-0000000000000000000000000000000000000000 remove
-eca8f4a35834f58a4008048a3c5c5c89592cb260 0.2
-0000000000000000000000000000000000000000 0.2
-0000000000000000000000000000000000000000 0.2
-eca8f4a35834f58a4008048a3c5c5c89592cb260 0.2
-4575a13448f8a85ab6553fba033c5a2ec41dd21c 0.3
-bf5a92e6ad9bd1a613ced83cbfa86d4b54117142 0.4
-e1cf2f1a4a5306da54e485249e54e8f462a8db5e 0.5
-e1cf2f1a4a5306da54e485249e54e8f462a8db5e 0.5
-eb4ea659c9cf0c47b758094b894f7ccc36325aa6 0.5
-151f79315c8250982ce2c8af27dad16009a0edb4 0.5.1
-f43ff1d34884a6b8cba6574960cdcbe126140c59 0.6.1
-a604d2b8549c8ac97f7537609191ba32292b3d25 0.6.2
-a367ade70d37206891f0653f68472fbcc59d97f1 0.7
-695fde92f9cf7dd7dd5ef6a03b37db1271d01dcc 0.7.1
-fff4872e0b6be02ee2c7a6802d8f2c7129d210aa 0.8
-0dcd2ef344a060b130833d5a13f3dab2d1fa8f15 0.8.1
-584c7bbcdad57a8871a0bd705f159b60f392f0cd 0.9
-4ad9b5e9a3ac1dda8f3734bf30e7fc1981ed14d4 0.9.1
-4ad9b5e9a3ac1dda8f3734bf30e7fc1981ed14d4 0.9.1
-0000000000000000000000000000000000000000 0.9.1
-0000000000000000000000000000000000000000 0.9.1
-ab8f14be5e08b75db21a775481474a9e9a12083f 0.9.1
-5038d4dc7d3f558acabb050700eace017320805a 0.9.2
-da76a647919299ced33de2cc56ad9e62330fa7ad 0.10
-b446509c021926096cd80f058b273ac8aaf7fa40 0.9.3
-1107cbf1081dc26fc0168b0d8caf5c24d39c1000 0.10.1
-50feafd06305b562ffaf7b92ba058fd940b1f679 1.0
-aa99317ef95e587224faed28c2eb598cccca32d4 1.1
-e16a5f97ae32c8e48abe035e9e31ffb848933209 1.1.1
-e16a5f97ae32c8e48abe035e9e31ffb848933209 1.1.1
-0000000000000000000000000000000000000000 1.1.1
-0000000000000000000000000000000000000000 1.1.1
-e2a55056a93d8af0f569e53fef899656d9f25fc5 1.1.1
-d357564b127beac819e0922e56b8af3914690e63 1.1.2
-49e6c6cc8bf56523925fd8e4b1764003e5dceeb7 1.2
-3f0bd46c9051d4720f95fcfa16a2988f01457e17 1.2.1
-5d826f81a5cdf5f66808627eaecdc6932a7d0081 1.2.2
-c756ca4fdc3762fe0f63292e8637a7ca3b6bfcb3 1.2.3
-1db006246178ce9a4905443d71ff5fe9cadb2c45 1.3
-e8e07ecf2e1ba2ca0e4b88288f191cfead8f075c 1.4
-cf4a792f142df63a5a687dee46e728340af4b465 1.5
-fbce773ad6c14a46c568fd45363d006290f98c98 1.6
-f6583190c3de22ce9736e87c8f2c6d3beb6eab21 2.0b1
-081c6742b0a197297322ae5fcd4f8fa379378736 1.6.1
-55e8cb1e184885b0473643684e30ca4b559f690e 2.0
-c5273e261be34d609019db63f429bb6b34cf92ca 2.0.1
-a29b8da4ff264471adc0fd4033a3674529a210fd 2.0.2
-55831944f1c00ff5e913952ab73ccddd9242ace5 2.0.3
-01a217c7cedc645ba19776d2479a0aeceb664410 2.1b1
-5af8ebb2f2b9bda489ea0aef39c19ee9796e0e3e 2.1
-c000a249012fc302daeaea873fee3a861e31d8f5 2.1.1
-946509efadd0331365a7cbf6d6455a4752e199a2 3.0
-15e818f6a87b075e65a3e444a0e1db3ffc0890d9 3.0.1
-b2629a6ef04f4b46affb3dc3751cf3b01b145751 3.0.2
-d1266aaff8d9b4c22e4d89e65c7813658ac18de5 3.0.3
-b24852dba2e0a1b555c4129bdba217c293942656 3.0.4
-acf7b0591089a77bb2c920c8ce445bcd2a502717 3.0.5
-6d9407b6ed3579c0ebbf6f8d1d461a6cb6cdd82c 3.1b1
-0a5868df092005c73c4f999495236757371be191 3.1
-05bcc5cd7bf946f7e987c25f698de3d244013be1 3.2
-e4ce9b6392fe786bb3b56e2d724721b5d063a9d2 3.2.1
-26c53a6f5d64667ac60e15f3595214d0f89d0040 3.3
-598488b60d2148d4c44e64e9e725cde93a258c75 3.4
-05cb255d539563b0c626b24aa22cfc08f9eaa17d 3.5
-692ab5c3c197d524f99924f39b43de9a388b0d1a 3.6
-549954d7a0d716a556c331ad9d36fdbb63f7794f 3.7
-ce314407ffb017166d0bf3dec57c1e5979d916fc 3.8
-67352e4c26f1278b50c5d8914b6ecdc11f75d2a7 4.0
-5f6c010873bda9a23049f97d77515f3b9b76b4c8 4.1
-68bcccb34cc65bf48b87e7a68711ef54274efde9 4.1.1
-c3fd3cac00241f48f3982e3706c45f5da01abb13 5.0
-b2e88501a6a9bc7f1c7c230a6431ac0860ff4e50 5.1
-331d1a79f4025f029befaceb337b7612f9cf5a55 5.2
-4059d5c6c76cb43d9c79dd2f5b849a57ac33bcd5 5.2.1
-ec350f6cd8328edc404e6cbfd489b657cf7a2dea 5.3
-6d6aa6b6b030f1ea900ab59e7496e8eb105e9af3 5.4
-25fc5b1f44a2a5acf5f314f47b4df1486dae767a 5.5
-41a4a8009d2336bfebe221e735a642d0740651e6 5.5.1
-155b7078a68c14f4a8158e1154fd5c050acbcf2a 5.6
-b627f03618585eeb8df1d7403ac3637ece06d644 5.7
-a4a35ff779eb9125f2ec550e90a3a839bd8c48a9 5.7.1
-dc1cf8a793120e51c2d4b8f5a210048cb354f7f0 6.0
-dc1cf8a793120e51c2d4b8f5a210048cb354f7f0 6.0
-4f626f3936d782caba0cd63bd31df278a3528e49 6.0
-4da739a49d9e72e901111e2e4a86964a17fbf47d 6.1
-902ca64b5639519f6d0aecd786949a83944291ca 6.1.1
-63e5de418ff70bba19d758a146cf8bdf642d6e36 7.0
-8c7a0fb016a87931292c2f7ab1b735a97768759f 7.0.1
-1eed5d66e94b78aebb97d75d95559ed2e27c5447 7.0.2
-b49aea662a2ba2e30fb5288a5bfbd834be674505 7.1
-89f927d763931b78263022cca25ec85b47b6f27e 7.1.1
-8009ebf8badd5fc409a7f393209038b0057fb23e 7.1.2
-510a876a75acdb3dbd7c7db44a12004b34c8ee90 7.2
-ce25102896cdb5aeff5937bce37097b6bd960f67 7.3
-c8220affec79af112409b82a868333786f9a5e88 7.3.1
-3952633b87570a50aba6349bcc75f89f7a1db724 8.0
-fed334c57a38ea22886d311d4daf581be25b558a 8.0.1
-dbc981b43088e635228899e779747ce0eafde491 8.1
-81e61bc8edc2d6e9415005557fe216f027b5bfd6 8.1.1
-8f15c2addf681c11ce8f0437deebb338cab920d8 8.2
-d225d8ba8a020eed8170389090a5a82abc38289b 8.3
-f9004a4c72d1e41f473eef3fefa7b596b30d9259 8.4
-6ddcb034223246c4b67d9caea3f0deb18f462c59 8.4.1
-5f0cc53d698fcac4174bc54ae84b3478cb5cd06e 8.5
-e837337c9b9375a9db508a2bd4dfd0e1c3e2bcc2 8.5.1
-45a70dfe822cbdc889142e1d984a5074396ba711 8.6
-87d6d34cdea1b3b40bb60c3286b672c69ec49223 8.6.1
-d8633f6d4baf8abcffa80c456a89bf0ff09ff706 8.7
-a17bfebdf428e42ff31b71beee3e700b8329acdf 9.0
-e0adabb76d3d729c55c9211d9f5314fcce210149 9.1
-074f2c9cade6bc89372133e6d2674cfcff4b4194 9.2
-3cc50ae65bc4ceef0ce7d06f8b455d3e655396f3 9.2.1
-94e5cb8fd63b71ed9f711d3c3abeaaf9b7fd0e1d 9.3
-2dabc8d8bd343a0bfcee426efab9f0024d887271 9.3.1
diff --git a/.travis-osx b/.travis-osx
new file mode 100644
index 0000000..f22e09c
--- /dev/null
+++ b/.travis-osx
@@ -0,0 +1,5 @@
+# Perform the manual steps on osx to install python3 and activate an environment
+brew update
+brew install python3
+rm /usr/local/bin/python
+ln -s python3 /usr/local/bin/python
diff --git a/.travis.yml b/.travis.yml
index 10d509a..22fb3e0 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -4,8 +4,6 @@ matrix:
- os: linux
python: 2.7
- os: linux
- python: 3.2
- - os: linux
python: 3.3
- os: linux
python: 3.4
@@ -14,15 +12,11 @@ matrix:
- os: osx
language: generic
-# Perform the manual steps on osx to install python3 and activate venv
before_install:
-- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew update; fi
-- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew install python3; fi
-- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then python3 -m venv /tmp/.env; fi
-- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then source /tmp/.env/bin/activate; fi
+- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then source .travis-osx; fi
install:
-- pip install tox "setuptools>=28.2"
+- python -m pip install tox "setuptools>=28.2"
script:
- tox -- -rs -v
branches:
diff --git a/CHANGES.rst b/CHANGES.rst
index 78cd98a..aa96303 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -1,11 +1,22 @@
CHANGES
=======
+10.0.2
+-----
+
+* #247: Restored console script.
+
+10.0.1
+------
+
+* Update readme to reflect test recommendations.
+
10.0
----
* Drop support for Python 3.2.
* Test suite now uses tox instead of pytest-runner.
+ Test requirements are now defined in tests/requirements.txt.
9.3.1
-----
diff --git a/PKG-INFO b/PKG-INFO
index 14fc487..a75c40c 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: keyring
-Version: 10.0
+Version: 10.0.2
Summary: Store and access your passwords safely.
Home-page: https://github.com/jaraco/keyring
Author: Jason R. Coombs
@@ -278,14 +278,15 @@ Description: .. image:: https://img.shields.io/pypi/v/keyring.svg
Making Releases
===============
- Python keyring lib uses a simple tag and release process. The simplified
- workflow is first tag a release, then invoke ``setup.py release``.
+ This project makes use of automated releases via Travis-CI. The
+ simple workflow is to tag a commit and push it to Github. If it
+ passes tests on a late Python version, it will be automatically
+ deployed to PyPI.
Other things to consider when making a release:
- first ensure that tests pass (preferably on Windows and Linux)
- check that the changelog is current for the intended release
- - after tagging, but before releasing, push the changes to the repository
Running Tests
=============
@@ -293,57 +294,17 @@ Description: .. image:: https://img.shields.io/pypi/v/keyring.svg
Tests are `continuously run <https://travis-ci.org/#!/jaraco/keyring>`_ using
Travis-CI.
- |BuildStatus|_
-
- .. |BuildStatus| image:: https://secure.travis-ci.org/jaraco/keyring.png
- .. _BuildStatus: http://travis-ci.org/jaraco/keyring
-
To run the tests yourself, you'll want keyring installed to some environment
- in which it can be tested. Recommended techniques are described below.
-
- Using pytest runner
- -------------------
+ in which it can be tested. Recommended technique is described below.
- Keyring is instrumented with `pytest runner
- <https://github.com/pytest-dev/pytest-runner>`_. Thus, you may invoke the tests
- from any supported Python (with setuptools installed) using this command::
+ Using tox
+ ---------
- python setup.py test
-
- pytest runner will download any unmet dependencies and run the tests using
- `pytest <https://bitbucket.org/hpk42/pytest>`_.
+ Keyring prefers use of `tox <https://pypi.org/project/tox>` to run tests.
+ Simply install and invoke ``tox``.
This technique is the one used by the Travis-CI script.
- Using virtualenv and pytest/nose/unittest
- -----------------------------------------
-
- Pytest and Nose are two popular test runners that will discover tests and run
- them. Unittest also has a mode to discover tests.
-
- First, however, these test runners typically need a test environment in which
- to run. It is recommended that you install keyring to a virtual environment
- to avoid interfering with your system environment. For more information, see
- the `venv documentation <https://docs.python.org/dev/library/venv.html>`_ or
- the `virtualenv homepage <http://www.virtualenv.org>`_.
-
- After you've created (or designated) your environment, install keyring into
- the environment by running::
-
- python setup.py develop
-
- You then need to install the test requirements with something like::
-
- pip install $( python -c "import setup, subprocess; print(subprocess.list2cmdline(setup.test_requirements))" )
-
- Then, invoke your favorite test runner, e.g.::
-
- py.test
-
- or::
-
- nosetests
-
----------
Background
----------
diff --git a/README.rst b/README.rst
index bda16f6..609adce 100644
--- a/README.rst
+++ b/README.rst
@@ -270,14 +270,15 @@ contributors.
Making Releases
===============
-Python keyring lib uses a simple tag and release process. The simplified
-workflow is first tag a release, then invoke ``setup.py release``.
+This project makes use of automated releases via Travis-CI. The
+simple workflow is to tag a commit and push it to Github. If it
+passes tests on a late Python version, it will be automatically
+deployed to PyPI.
Other things to consider when making a release:
- first ensure that tests pass (preferably on Windows and Linux)
- check that the changelog is current for the intended release
- - after tagging, but before releasing, push the changes to the repository
Running Tests
=============
@@ -285,57 +286,17 @@ Running Tests
Tests are `continuously run <https://travis-ci.org/#!/jaraco/keyring>`_ using
Travis-CI.
-|BuildStatus|_
-
-.. |BuildStatus| image:: https://secure.travis-ci.org/jaraco/keyring.png
-.. _BuildStatus: http://travis-ci.org/jaraco/keyring
-
To run the tests yourself, you'll want keyring installed to some environment
-in which it can be tested. Recommended techniques are described below.
-
-Using pytest runner
--------------------
+in which it can be tested. Recommended technique is described below.
-Keyring is instrumented with `pytest runner
-<https://github.com/pytest-dev/pytest-runner>`_. Thus, you may invoke the tests
-from any supported Python (with setuptools installed) using this command::
+Using tox
+---------
- python setup.py test
-
-pytest runner will download any unmet dependencies and run the tests using
-`pytest <https://bitbucket.org/hpk42/pytest>`_.
+Keyring prefers use of `tox <https://pypi.org/project/tox>` to run tests.
+Simply install and invoke ``tox``.
This technique is the one used by the Travis-CI script.
-Using virtualenv and pytest/nose/unittest
------------------------------------------
-
-Pytest and Nose are two popular test runners that will discover tests and run
-them. Unittest also has a mode to discover tests.
-
-First, however, these test runners typically need a test environment in which
-to run. It is recommended that you install keyring to a virtual environment
-to avoid interfering with your system environment. For more information, see
-the `venv documentation <https://docs.python.org/dev/library/venv.html>`_ or
-the `virtualenv homepage <http://www.virtualenv.org>`_.
-
-After you've created (or designated) your environment, install keyring into
-the environment by running::
-
- python setup.py develop
-
-You then need to install the test requirements with something like::
-
- pip install $( python -c "import setup, subprocess; print(subprocess.list2cmdline(setup.test_requirements))" )
-
-Then, invoke your favorite test runner, e.g.::
-
- py.test
-
-or::
-
- nosetests
-
----------
Background
----------
diff --git a/keyring.egg-info/PKG-INFO b/keyring.egg-info/PKG-INFO
index 14fc487..a75c40c 100644
--- a/keyring.egg-info/PKG-INFO
+++ b/keyring.egg-info/PKG-INFO
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: keyring
-Version: 10.0
+Version: 10.0.2
Summary: Store and access your passwords safely.
Home-page: https://github.com/jaraco/keyring
Author: Jason R. Coombs
@@ -278,14 +278,15 @@ Description: .. image:: https://img.shields.io/pypi/v/keyring.svg
Making Releases
===============
- Python keyring lib uses a simple tag and release process. The simplified
- workflow is first tag a release, then invoke ``setup.py release``.
+ This project makes use of automated releases via Travis-CI. The
+ simple workflow is to tag a commit and push it to Github. If it
+ passes tests on a late Python version, it will be automatically
+ deployed to PyPI.
Other things to consider when making a release:
- first ensure that tests pass (preferably on Windows and Linux)
- check that the changelog is current for the intended release
- - after tagging, but before releasing, push the changes to the repository
Running Tests
=============
@@ -293,57 +294,17 @@ Description: .. image:: https://img.shields.io/pypi/v/keyring.svg
Tests are `continuously run <https://travis-ci.org/#!/jaraco/keyring>`_ using
Travis-CI.
- |BuildStatus|_
-
- .. |BuildStatus| image:: https://secure.travis-ci.org/jaraco/keyring.png
- .. _BuildStatus: http://travis-ci.org/jaraco/keyring
-
To run the tests yourself, you'll want keyring installed to some environment
- in which it can be tested. Recommended techniques are described below.
-
- Using pytest runner
- -------------------
+ in which it can be tested. Recommended technique is described below.
- Keyring is instrumented with `pytest runner
- <https://github.com/pytest-dev/pytest-runner>`_. Thus, you may invoke the tests
- from any supported Python (with setuptools installed) using this command::
+ Using tox
+ ---------
- python setup.py test
-
- pytest runner will download any unmet dependencies and run the tests using
- `pytest <https://bitbucket.org/hpk42/pytest>`_.
+ Keyring prefers use of `tox <https://pypi.org/project/tox>` to run tests.
+ Simply install and invoke ``tox``.
This technique is the one used by the Travis-CI script.
- Using virtualenv and pytest/nose/unittest
- -----------------------------------------
-
- Pytest and Nose are two popular test runners that will discover tests and run
- them. Unittest also has a mode to discover tests.
-
- First, however, these test runners typically need a test environment in which
- to run. It is recommended that you install keyring to a virtual environment
- to avoid interfering with your system environment. For more information, see
- the `venv documentation <https://docs.python.org/dev/library/venv.html>`_ or
- the `virtualenv homepage <http://www.virtualenv.org>`_.
-
- After you've created (or designated) your environment, install keyring into
- the environment by running::
-
- python setup.py develop
-
- You then need to install the test requirements with something like::
-
- pip install $( python -c "import setup, subprocess; print(subprocess.list2cmdline(setup.test_requirements))" )
-
- Then, invoke your favorite test runner, e.g.::
-
- py.test
-
- or::
-
- nosetests
-
----------
Background
----------
diff --git a/keyring.egg-info/SOURCES.txt b/keyring.egg-info/SOURCES.txt
index 19be1ac..10296a4 100644
--- a/keyring.egg-info/SOURCES.txt
+++ b/keyring.egg-info/SOURCES.txt
@@ -1,5 +1,5 @@
.gitignore
-.hgtags
+.travis-osx
.travis.yml
CHANGES.rst
README.rst
@@ -26,6 +26,7 @@ keyring/py33compat.py
keyring.egg-info/PKG-INFO
keyring.egg-info/SOURCES.txt
keyring.egg-info/dependency_links.txt
+keyring.egg-info/entry_points.txt
keyring.egg-info/namespace_packages.txt
keyring.egg-info/requires.txt
keyring.egg-info/top_level.txt
@@ -48,4 +49,5 @@ keyring/util/__init__.py
keyring/util/escape.py
keyring/util/platform_.py
keyring/util/properties.py
-tests/requirements.txt
\ No newline at end of file
+tests/requirements.txt
+tests/test_packaging.py
\ No newline at end of file
diff --git a/keyring.egg-info/entry_points.txt b/keyring.egg-info/entry_points.txt
new file mode 100644
index 0000000..b550864
--- /dev/null
+++ b/keyring.egg-info/entry_points.txt
@@ -0,0 +1,3 @@
+[console_scripts]
+keyring = keyring.cli:main
+
diff --git a/setup.py b/setup.py
index 6332920..8833efb 100644
--- a/setup.py
+++ b/setup.py
@@ -51,6 +51,9 @@ setup_params = dict(
"Programming Language :: Python :: 3.5",
],
entry_points={
+ 'console_scripts': [
+ 'keyring=keyring.cli:main',
+ ],
},
)
if __name__ == '__main__':
diff --git a/tests/test_packaging.py b/tests/test_packaging.py
new file mode 100644
index 0000000..201c607
--- /dev/null
+++ b/tests/test_packaging.py
@@ -0,0 +1,14 @@
+import pkg_resources
+
+def test_entry_point():
+ """
+ Keyring provides exactly one 'keyring' console script
+ that's a callable.
+ """
+ eps = pkg_resources.iter_entry_points('console_scripts')
+ ep, = (
+ ep
+ for ep in eps
+ if ep.name == 'keyring'
+ )
+ assert callable(ep.resolve())
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/packages/python-keyring.git
More information about the Python-modules-commits
mailing list