Bug 1722479 - Review Request: python-pysnooper - Never use print for debugging again
Summary: Review Request: python-pysnooper - Never use print for debugging again
Keywords:
Status: CLOSED DUPLICATE of bug 1720843
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-20 12:53 UTC by Lumír Balhar
Modified: 2019-06-20 13:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-20 13:32:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lumír Balhar 2019-06-20 12:53:48 UTC
Spec URL: https://lbalhar.fedorapeople.org/python-pysnooper.spec
SRPM URL: https://lbalhar.fedorapeople.org/python-pysnooper-0.2.2-1.fc30.src.rpm
Description: PySnooper - Never use print for debugging again! You're trying to figure out why your Python code isn't doing what you think it should be doing. You'd love to use a full-fledged debugger with breakpoints and watches, but you can't be bothered to set one up right now. You want to know which lines are running and which aren't, and what the values of the values of the local variables are. Most people would use print lines, in strategic locations, some of them showing the values of variables. PySnooper lets you do the same, except instead of carefully crafting the right print lines, you just add one decorator line to the function you're interested in. You'll get a play-by-play log of your function, including which lines ran and when, and exactly when local variables were changed.
Fedora Account System Username: lbalhar

Scratch builds:
- rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=35648490
- Fedora 30: https://koji.fedoraproject.org/koji/taskinfo?taskID=35648500

Comment 1 Fabian Affolter 2019-06-20 13:32:45 UTC

*** This bug has been marked as a duplicate of bug 1720843 ***


Note You need to log in before you can comment on or make changes to this bug.