Just to confirm that I also have the same incompatibility between ROOT and
OptionParser, such that when I call the -h help I get the help message from
ROOT and not mine!
I'll try to see if the workaround suggested by Tim is also fixing this issue.
Thanks
Antonio
“There are 10 kinds of people. Those that understand binary and those that don’t.”
On Sat, Jun 27, 2009 at 5:22 AM, Alfio Rizzo <Alfio.Rizzo_at_vub.ac.be> wrote:
> >Alfio,
> >
> >there is no need for (unless you wrote your own TApplication):
> >
> >> app.Run()
> >
> >so just removed it and keep the python prompt active.
> >
> >Best regards,
> > Wim
> >--
> >WLavrijsen_at_lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
> >
> >
> >
> HI,
> so your suggestion is totally correct,
> but I realizied that the "weird" problem that I have is due to the reason
> that I am using the OptionParser method to get some parameters.
> So, it somehow conflicts with root options, for instance I have my personal
> -b option that conflicts with ROOT -b to run in batch.
> That's why sometime it works and sometimes not, i.e. if I set this option
> or not..
> So, maybe have I to create 2 script one with the parser and the other with
> sys.argv ? Or just change the -b to -B .....
>
> Thanks
>
> Cheers
> A
>
>
> -----------------------------------------
> Alfio RIZZO
> Vrije Universiteit Brussel
> Faculteit Wetenschappen, Dienst ELEM
> Gebouw G, Bureau 0G-111
> Pleinlaan, 2 B-1050 Brussels BELGIUM
> Tel. +32(0)26293220 Fax +32(0)26293816
> alfio.rizzo_at_vub.ac.be
> -----------------------------------------
>
>
Received on Sat Jun 27 2009 - 08:25:16 CEST
This archive was generated by hypermail 2.2.0 : Sat Jun 27 2009 - 11:50:02 CEST