Where to report bugs?

[ack]

Hi all,

Still enjoying working with Reinteract very much, but sadly I've found
a pair of bugs which I would like to report, but I'm a little confused
as to where to do this.

As far as I know, there are two places which show issues related to
Reinteract:

http://www.reinteract.org/trac/

and

https://bugzilla.gnome.org/enter_bug.cgi?product=reinteract
(which is mentioned in the Wiki)

Before reading the Wiki, I already created an account on Trac, but I
can't seem to find a way to open new tickets.
Does this mean that all bugs should go to Bugzilla?

Kind regards,
-ack

P.S.: To not keep you in suspense, one of the bugs concerns Reinteract
stalling on recalculation and giving a traceback when recalculating:

def f((a, b), c): # Yes, that's a tupled pair of parameters :-)
print a, b, c

The other bug concerns a module which uses __import__ and requires
somewhat more space to explain.

[Robert Schroll]

On 11/20/2011 12:22 AM, ack wrote:
> Before reading the Wiki, I already created an account on Trac, but I
> can't seem to find a way to open new tickets.
> Does this mean that all bugs should go to Bugzilla?

Yes, bugs should go on Bugzilla. The whole Trac site will be going away
soon.

> P.S.: To not keep you in suspense, one of the bugs concerns Reinteract
> stalling on recalculation and giving a traceback when recalculating:
>
> def f((a, b), c): # Yes, that's a tupled pair of parameters :-)
> print a, b, c

My immediate reaction was, that can't be valid syntax. I guess I've
learned my new thing for the day.

My guess, unfettered by evidence at the moment, is that this syntax
confuses Reinteract as it tries to figure out what mutations the code
will cause.

Robert

[ack]

On 20 nov, 07:29, Robert Schroll <rschr...@gmail.com> wrote:
> On 11/20/2011 12:22 AM, ack wrote:
>
> > Before reading the Wiki, I already created an account on Trac, but I
> > can't seem to find a way to open new tickets.
> > Does this mean that all bugs should go to Bugzilla?
>
> Yes, bugs should go on Bugzilla.  The whole Trac site will be going away
> soon.

Thanks!

> > P.S.: To not keep you in suspense, one of the bugs concerns Reinteract
> > stalling on recalculation and giving a traceback when recalculating:
>
> > def f((a, b), c): # Yes, that's a tupled pair of parameters :-)
> >      print a, b, c
>
> My immediate reaction was, that can't be valid syntax.  I guess I've
> learned my new thing for the day.

Yes, I agree it's somewhat unusual syntax (I discovered it by
accident :-) ) but it appears to be valid Python.
I guess it could be quite useful though, as the function takes as
first parameter any sequence which is exactly two items long.
So, no need to do something like:

def f(a, b):
if len(a) != 2:
# barf...

and testing whether a is iterable and such.

-ack

[ack]

Thanks Robert for creating patches for these bugs so quickly! :-)

Kind regards,
ack