Thursday, March 08, 2018

Re: [NEW] devel/py-q

On 2018/03/08 07:27, Remi Pointel wrote:
> On 03/07/18 22:24, Klemens Nanni wrote:
> > On Wed, Mar 07, 2018 at 04:02:48PM +0100, Remi Pointel wrote:
> > > $ pkg_info py-q
> > > Information for inst:py-q-2.6
> > >
> > > Comment:
> > > quick-and-dirty debugging output for tired programmers
> > >
> > > Required by:
> > > floss-1.5.0
> > >
> > > Description:
> > > Quick and dirty debugging output for tired programmers.
> > Where's the value in that description? I'd really appreciate an actual
> > sentence telling me what this `q' does.
>
> Changed.
>
> > What about Python 3? Does it work? If it explicitly requires Python 2,
> > please set MODPY_VERSION accordingly.
>
> It's python 2 only, and python 2 is our version by default.
>
> > `make test' doesn't pick up tests even though there are nine of them
> > which succeed when run manually.
> >
>
> Thank, it's changed.
>
> Ok?
>
> Cheers,
>
> Remi.

| """Quick and dirty debugging output for tired programmers.
|
| All output goes to /tmp/q, which you can watch with this shell command:
|
| tail -f /tmp/q
|
| If TMPDIR is set, the output goes to $TMPDIR/q.
|
| All output goes to /tmp/q, which you can watch with this shell command:
|
| tail -f /tmp/q

So, this is junk code for debugging that says right in the description
that it's dirty. Writing to a fixed string filename in /tmp, really.
This certainly isn't production quality code.

I don't think this is actually used in floss, it's in setup.py but there
is no "import q". Can you just kill the dep instead?

No comments:

Post a Comment