public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
* Some Python (and other) questions
@ 2000-10-02  7:17 Kirby, Dave
  2000-10-02 10:41 ` Syd Polk
  0 siblings, 1 reply; 4+ messages in thread
From: Kirby, Dave @ 2000-10-02  7:17 UTC (permalink / raw)
  To: 'sourcenav@sourceware.cygnus.com'

I have recently upgraded to 4.5.2 for its Python support, and have some
questions.

Firstly, the python support seems to be only partial - nothing shows up in
the class view and the Xref and Include tabs are greyed out.  However the
information for the classes, methods etc are in the database since they can
be seen in the Retriever view, so what gives?  Is this a bug in the python
parser?

Secondly, has anyone tried creating python wrappers for the SN  APIs?  This
would make it easy to write scripts for analysing the information in the DB
(as suggested by a previous poster) and for creating parsers written in
python.  I may have a go myself when I have time, but dont dont want to
duplicate the work if someone else has already done it.  It should be easy
using SWIG, and this would also enable the APIs to be called from TCL, Perl,
Guile etc.


Lastly, why doesnt the mailing list digest set the 'Reply To' field?  It is
a minor point, but it would make the list much easier to use.


	Dave K

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Some Python (and other) questions
  2000-10-02  7:17 Some Python (and other) questions Kirby, Dave
@ 2000-10-02 10:41 ` Syd Polk
  2000-10-02 12:22   ` Thomas Heller
  0 siblings, 1 reply; 4+ messages in thread
From: Syd Polk @ 2000-10-02 10:41 UTC (permalink / raw)
  To: Kirby, Dave, 'sourcenav@sourceware.cygnus.com'

At 03:14 PM 10/2/00 +0100, Kirby, Dave wrote:

>I have recently upgraded to 4.5.2 for its Python support, and have some
>questions.
>
>Firstly, the python support seems to be only partial - nothing shows up in
>the class view and the Xref and Include tabs are greyed out.  However the
>information for the classes, methods etc are in the database since they can
>be seen in the Retriever view, so what gives?  Is this a bug in the python
>parser?

You need to ask the original author.

>Secondly, has anyone tried creating python wrappers for the SN  APIs?  This
>would make it easy to write scripts for analysing the information in the DB
>(as suggested by a previous poster) and for creating parsers written in
>python.  I may have a go myself when I have time, but dont dont want to
>duplicate the work if someone else has already done it.  It should be easy
>using SWIG, and this would also enable the APIs to be called from TCL, Perl,
>Guile etc.

We welcome the contributiions.


>Lastly, why doesnt the mailing list digest set the 'Reply To' field?  It is
>a minor point, but it would make the list much easier to use.

None of the sources.redhat.com lists do this that I am aware.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Some Python (and other) questions
  2000-10-02 10:41 ` Syd Polk
@ 2000-10-02 12:22   ` Thomas Heller
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Heller @ 2000-10-02 12:22 UTC (permalink / raw)
  To: Kirby, Dave, sourcenav, Syd Polk

> >I have recently upgraded to 4.5.2 for its Python support, and have some
> >questions.
> >
> >Firstly, the python support seems to be only partial - nothing shows up
in
> >the class view and the Xref and Include tabs are greyed out.  However the
> >information for the classes, methods etc are in the database since they
can
> >be seen in the Retriever view, so what gives?  Is this a bug in the
python
> >parser?
>
> You need to ask the original author.
Ok, so here we go:

The python parser is modeled after pyclrbr.py, with the improvement
that it also finds global variables (apart from classes, methods
and functions).
No xref info at all (simply because I have no idea how to do this).
No import statements are parsed, so no include info is generated.

>
> >Secondly, has anyone tried creating python wrappers for the SN  APIs?
This
> >would make it easy to write scripts for analysing the information in the
DB
> >(as suggested by a previous poster) and for creating parsers written in
> >python.  I may have a go myself when I have time, but dont dont want to
> >duplicate the work if someone else has already done it.  It should be
easy
> >using SWIG, and this would also enable the APIs to be called from TCL,
Perl,
> >Guile etc.

Thoma

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Some Python (and other) questions
@ 2000-10-03  0:56 dave.banham
  0 siblings, 0 replies; 4+ messages in thread
From: dave.banham @ 2000-10-03  0:56 UTC (permalink / raw)
  To: sourcenav

>>Lastly, why doesnt the mailing list digest set the 'Reply To' field?  It is
>>a minor point, but it would make the list much easier to use.

>None of the sources.redhat.com lists do this that I am aware.

The reason for this (I guess), and the setting of the 'reply to' field, in the
non-digest version, to the originating author rather than the SN mailing list
e-mail address, is to avoid automated 'out of the office', etc. replies junking
up the list and everyone's e-mail. If you want to reply to the list you must
explicitly set the 'send-to' field to that of the list otherwise you will just
be replyingto the original author - off-line.

As a member of several other mailing lists which do not do this, I can attest to
the amount of automated junk that I receive. So please Red Hat do not change
this policy!

Regards
Dave Banham




^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2000-10-03  0:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-10-02  7:17 Some Python (and other) questions Kirby, Dave
2000-10-02 10:41 ` Syd Polk
2000-10-02 12:22   ` Thomas Heller
2000-10-03  0:56 dave.banham

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).