File: README.source

package info (click to toggle)
sentry-python 2.18.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 4,004 kB
  • sloc: python: 55,908; makefile: 114; sh: 111; xml: 2
file content (59 lines) | stat: -rw-r--r-- 2,719 bytes parent folder | download | duplicates (2)
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
This package is maintained with git-buildpackage(1). It follows DEP-14 for
branch naming (e.g. using debian/master for the current version in Debian
unstable due Debian Python team policy).

It uses pristine-tar(1) to store enough information in git to generate bit
identical tarballs when building the package without having downloaded an
upstream tarball first.

When working with patches it is recommended to use "gbp pq import" to import
the patches, modify the source and then use "gbp pq export --commit" to commit
the modifications.

The changelog is generated using "gbp dch" so if you submit any changes don't
bother to add changelog entries but rather provide a nice git commit message
that can then end up in the changelog.

It is recommended to build the package with pbuilder using:

    gbp buildpackage --git-pbuilder

For information on how to set up a pbuilder environment see the git-pbuilder(1)
manpage. In short:

    DIST=sid git-pbuilder create
    gbp clone https://salsa.debian.org/python-team/packages/sentry-python.git
    cd sentry-python
    gbp buildpackage --git-pbuilder


Ignoring additional tests for pytest version >7
===============================================
The source of the Sentry SDK is heavily using pytest for QA. But the upstream
pytest project has done some deeply structural changes whith version 7 which
does provoke some errors messages with the Sentry SDK. The error messages for
each test which isn't running successful is failing with this error message.

/usr/lib/python3/dist-packages/_pytest/runner.py:338: in from_call
    result: Optional[TResult] = func()
/usr/lib/python3/dist-packages/_pytest/runner.py:259: in <lambda>
    lambda: ihook(item=item, **kwds), when=when, reraise=reraise
/usr/lib/python3/dist-packages/pluggy/_hooks.py:265: in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:80: in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
/usr/lib/python3/dist-packages/_pytest/runner.py:154: in pytest_runtest_setup
    item.session._setupstate.setup(item)
/usr/lib/python3/dist-packages/_pytest/runner.py:482: in setup
    assert col in needed_collectors, "previous item was not torn down properly"
E   AssertionError: previous item was not torn down properly

The pytest project is tracking this problem in

https://github.com/pytest-dev/pytest/issues/9621

To not hard depend on any progress of this issue all the tests that are related
to that issue are currently excluded by debian/rules by an extra added variable
PYBUILD_TEST_ARGS_PYTEST7_IGNORE.

 -- Carsten Schoenert <c.schoenert>  Sat, 11 Jun 2022 13:23:00 +0200