summaryrefslogtreecommitdiff
path: root/python-btnamespace.spec
blob: 0d28e2445bcbe49b9d8c9c2765309123c5a20e89 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
%global _empty_manifest_terminate_build 0
Name:		python-btnamespace
Version:	2.1.1
Release:	1
Summary:	Isolate state on the Braintree sandbox during testing.
License:	MIT
URL:		https://github.com/venmo/btnamespace
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/75/ba/56c45e1676c352352ba5d6bb1508ef7ec5029d75740677c54662f81bf2bd/btnamespace-2.1.1.tar.gz
BuildArch:	noarch

Requires:	python3-future
Requires:	python3-mock
Requires:	python3-bidict
Requires:	python3-braintree
Requires:	python3-bidict
Requires:	python3-braintree

%description
*[not actively supported outside of internal Venmo usage]*
A Braintree namespace isolates state on the Braintree gateway:
    import braintree
    import btnamespace
    with btnamespace.Namespace():
        customer = braintree.Customer.create({"id": "123"})
        assert customer.id == "123"
        braintree.Customer.find("123")  # success
    braintree.Customer.find("123")  # NotFound exception
This is primarily useful during integration tests:
    def setUp(self):
        self.namespace = btnamespace.Namespace()
        self.namespace.__enter__()
    def test_some_sandbox_integration(self):
        #...
    def tearDown(self):
        self.namespace.__exit__()
Compared to calling eg ``braintree.Customer.delete`` during ``tearDown``, this has a number of advantages:
-  it's faster, since no teardown is needed
-  it's simpler, since it doesn't require any bookkeeping
-  it's robust, since tests can be written without any state assumptions
You can install it with ``$ pip install btnamespace``.

%package -n python3-btnamespace
Summary:	Isolate state on the Braintree sandbox during testing.
Provides:	python-btnamespace
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-btnamespace
*[not actively supported outside of internal Venmo usage]*
A Braintree namespace isolates state on the Braintree gateway:
    import braintree
    import btnamespace
    with btnamespace.Namespace():
        customer = braintree.Customer.create({"id": "123"})
        assert customer.id == "123"
        braintree.Customer.find("123")  # success
    braintree.Customer.find("123")  # NotFound exception
This is primarily useful during integration tests:
    def setUp(self):
        self.namespace = btnamespace.Namespace()
        self.namespace.__enter__()
    def test_some_sandbox_integration(self):
        #...
    def tearDown(self):
        self.namespace.__exit__()
Compared to calling eg ``braintree.Customer.delete`` during ``tearDown``, this has a number of advantages:
-  it's faster, since no teardown is needed
-  it's simpler, since it doesn't require any bookkeeping
-  it's robust, since tests can be written without any state assumptions
You can install it with ``$ pip install btnamespace``.

%package help
Summary:	Development documents and examples for btnamespace
Provides:	python3-btnamespace-doc
%description help
*[not actively supported outside of internal Venmo usage]*
A Braintree namespace isolates state on the Braintree gateway:
    import braintree
    import btnamespace
    with btnamespace.Namespace():
        customer = braintree.Customer.create({"id": "123"})
        assert customer.id == "123"
        braintree.Customer.find("123")  # success
    braintree.Customer.find("123")  # NotFound exception
This is primarily useful during integration tests:
    def setUp(self):
        self.namespace = btnamespace.Namespace()
        self.namespace.__enter__()
    def test_some_sandbox_integration(self):
        #...
    def tearDown(self):
        self.namespace.__exit__()
Compared to calling eg ``braintree.Customer.delete`` during ``tearDown``, this has a number of advantages:
-  it's faster, since no teardown is needed
-  it's simpler, since it doesn't require any bookkeeping
-  it's robust, since tests can be written without any state assumptions
You can install it with ``$ pip install btnamespace``.

%prep
%autosetup -n btnamespace-2.1.1

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-btnamespace -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 2.1.1-1
- Package Spec generated