forked from pool/python-keyring
Accepting request 256238 from home:KGronlund:branches:devel:languages:python
- Update to version 4.0 (boo#901066): * Removed ``keyring_path`` parameter from ``load_keyring``. See release notes for 3.0.3 for more details. * Issue #22: Removed support for loading the config from the current directory. The config file must now be located in the platform-specific config location. - Changes from version 3.7: * Issue #22: Deprecated loading of config from current directory. Support for loading the config in this manner will be removed in a future version. * Issue #131: Keyring now will prefer ``pywin32-ctypes <https://pypi.python.org/pypi/pywin32-ctypes>``_ to pywin32 if available. - Changes from version 3.6: * Gnome keyring no longer relies on the GNOME_KEYRING_CONTROL environment variable. * Issue #140: Restore compatibility for older versions of PyWin32. - Switch to pytest since nose doesn't support test fixtures and fails: - Add BuildRequires: python-pytest - Remove BuildRequires: python-nose OBS-URL: https://build.opensuse.org/request/show/256238 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-keyring?expand=0&rev=30
This commit is contained in:
@@ -17,7 +17,7 @@
|
||||
|
||||
|
||||
Name: python-keyring
|
||||
Version: 3.6
|
||||
Version: 4.0
|
||||
Release: 0
|
||||
Url: http://bitbucket.org/kang/python-keyring-lib
|
||||
Summary: Store and access your passwords safely
|
||||
@@ -29,7 +29,7 @@ BuildRequires: python-devel
|
||||
BuildRequires: unzip
|
||||
# Test requirements:
|
||||
BuildRequires: python-mock
|
||||
BuildRequires: python-nose
|
||||
BuildRequires: python-pytest
|
||||
BuildRequires: python-pytest-runner
|
||||
%if 0%{?suse_version} && 0%{?suse_version} <= 1110
|
||||
BuildRequires: python-unittest2
|
||||
@@ -61,7 +61,7 @@ python setup.py build
|
||||
python setup.py install --prefix=%{_prefix} --root=%{buildroot}
|
||||
|
||||
%check
|
||||
nosetests
|
||||
py.test
|
||||
|
||||
%files
|
||||
%defattr(-,root,root)
|
||||
|
Reference in New Issue
Block a user