pythondialog-users — Discussions for users and developers

Re: [Pythondialog-users] pythondialog is not dead!

[Chris D. <ch...@si...>]

Thanks for the offer, but I am no longer interested in becoming a maintainer
of pythondialog.  (I moved jobs a few months ago, and I no longer use
pythondialog.)

All the best,

Chris.

On 30 March 2010 08:51, Peter Åstrand <as...@ce...> wrote:

>
>  I think this is partly my fault. I've been a poor maintainer for the last
>> years, and I can now see that I've not even responded to the request from
>> Chris Dew to step in as a maintainer. Sorry for that - I haven't kept track
>>
> ...
>
>  I can see that Chris Dew uses git. This is not my cup of tee either - I
>> prefer Subversion - but it's way batter than nothing.
>>
> ...
>
>> I think that the best solution for pythondialog would be that someone like
>> Chris Dew took over the Sourceforge project, migrated to Subversion, and
>> then incorporated the various patches floating around, for example your 2.09
>> changes.
>>
>
> Chris, are you still interested in to step in as a maintainer, or a
> "co-maintainer"? In that case, I can make you an admin of the SF project.
>
> We should also migrate away from CVS. If Subversion is fine, I can help
> with this. If you really want to use GIT, that's OK as well, but in that
> case I cannot help with the migration; I have a hard time using git for
> daily operations :-)
>
>
>
> Best regards, ---
> Peter Åstrand           ThinLinc Chief Developer
> Cendio AB               http://www.cendio.com
> Wallenbergs gata 4
> 583 30 Linköping        Phone: +46-13-21 46 00
>



-- 

http://www.finalcog.com/

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

> I think this is partly my fault. I've been a poor maintainer for the last 
> years, and I can now see that I've not even responded to the request from 
> Chris Dew to step in as a maintainer. Sorry for that - I haven't kept track 
...
> I can see that Chris Dew uses git. This is not my cup of tee either - I 
> prefer Subversion - but it's way batter than nothing.
...
> I think that the best solution for pythondialog would be that someone like 
> Chris Dew took over the Sourceforge project, migrated to Subversion, and then 
> incorporated the various patches floating around, for example your 2.09 
> changes.

Chris, are you still interested in to step in as a maintainer, or a 
"co-maintainer"? In that case, I can make you an admin of the SF project.

We should also migrate away from CVS. If Subversion is fine, I can help 
with this. If you really want to use GIT, that's OK as well, but in that 
case I cannot help with the migration; I have a hard time using git for 
daily operations :-)


Best regards, 
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

>I've never been much interested in the SF infrastructure. Current
>status is not the best I could imagine, and actually worse than it
>used to be: full of ads, and the project overview page
>(http://sourceforge.net/projects/pythondialog/) doesn't even contain
>the word "bug" (yes, I know where to find it). BTW, the "home page"
>http://pythondialog.sourceforge.net/ could well use some update...

I don't love Sourceforge either, but it works, and it's a de facto
standard. One has learned to work around it's strangeness.

But if anyone insists on moving to some other hosting, that's fine
with me.


Regards, 
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

>Hi, Peter.
>
>Firstly, thanks for writing pythondialog.

Hi! Actually, I didn't write it from the beginning; I've only done
some development work on it.


>I forked pythondialog to github after having several emails ignored by the
>both of the maintainers on sourceforge for many months.
>
>Several other patches were also being ignored.  I needed these patches and 
>I
>had extra functionality to add myself (a password field, iirc).
>
>Ignoring people who want to help with an opensource project is
> offensive.  At least tell them that their patches are unworthy to be
> added to the project and (possibly) how they could improve them.  If
> you can't spare the time to read email, just put a notice on the
> project page to let people know that they should not expect a
> response to any email.

I apologize.

The problem might partly be that I haven't considered myself to be the
only developer; "umdenken" is also still an admin, but he isn't active
any longer either, I think.

Best regards, 
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

(Trying to catch up...)

Florent Rougon  wrote:

>> Btw, does anyone have the email adress to Chris Dew? I've failed to find 
>it.
>
>I put in Cc the e-mail address he used on Sept. 16, 2008.

Thanks!


>OK. I wrote that because
>http://pypi.python.org/pypi?%3Aaction=search&term=pythondialog&submit=search
>listed you as the Author, but the Owner must be "paulproteus" indeed
>(not contacting him before we get out of the current mess, though).

Sounds great.



>> You don't use any kind of version control system? This is really bady, 
>IMO. I
>> tend to avoid software that lacks proper version control.
>
>Ahem. I did try to commit version 2.09 to the svn repos I set up in
>2004, but the operation hung. Maybe some dump/reload cycle of the DB
>would be needed. However:

Are you talking about an Sourceforge SVN repo, or something else? Do
you still have this problem? If SVN doesn't work for you, you can
always use something else; there are plenty of VC systems available...


>About the "really bady" part: you are free to avoid using my software if
>you are not confident about its quality. Although concerning

Sure, that's the beauty of Open Source. However, as I said, it might
be confusing if we have multiple "forks" using the same project
name. And as always, I think we should avoid forks, and instead try to
cooperate, unless there are any fundamental disagreements.


>I am a careful and rational person, and for such simple things as
>pythondialog, version control brings basically nothing to me. I don't
>make modifications "just to see if it is going to fix $bug", with the
>intent of rolling back if not. I keep previous versions on my hard
>drive, and I make backups on offline media. This is basic version
>control. When I do an involved modification, I make a backup copy
>beforehand, etc. The software I write, be it public or not, usually
>has relatively few bugs once I declare it usable. I don't think the
>pythondialog case makes an exception here. You are free to disagree,
>but please provide some evidence then.

Yes, I disagree :-) IMHO, you can't do any kind of serious development
work without version control. For example, if you add some new
feature, you want of course to see the "diff" between the new version
and the old version, which lacks this feature. You can certainly do
this by making a new copy of the software every time, but that is
certainly not more practical than use a real VC.


To summarize: Using a version control system is a requirement for
me. If future collaboration/cooperation will be done without one, I'm
afraid you have to count me out.


>> I *hate* version numbers like 2.09.
>
>It is your entire right, however I am not sure how rational it is.

There are many arguments against that scheme. For example, try to read
the version number "two zero nine" on the phone. The guy listening
will most likely interpret this as 2.0.9. Another argument: prefixing
numbers with zero usually indicates octal numbers.


>I am definitely *not* confusing 2.1 and 2.10 (in version string
>context).

But other persons or software might.


>As said, 2.09 sorts better in directory listings (until, of course,
>2.99) and shouldn't confuse anyone, since 09 == 9 in numeric
>context. I didn't intend to prolonge this scheme ad vitam æternam,
>but the sorting argument plus remaining consistent with previous
>numbers made me think that waiting for 2.10 before switching
>transparently to the more conventional versioning scheme was a
>perfectly sane course of action.

Sure, I could buy that approach, but the Sourceforge project has a
file release, done 6 years ago, called "2.7". Switching *back* to use
the zero prefix doesn't make any sense, so I don't think we should
make any new release on Sourceforge using that old version scheme.

Best regards,
Peter Åstrand

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

> Erm... Peter, are you reading the list?

Sorry, no. I'll subscribe and try to catch up on monday.


Rgds, 
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00

Re: [Pythondialog-users] pythondialog is not dead!

[Florent R. <fl...@vi...>]

Erm... Peter, are you reading the list?

-- 
Florent

Re: [Pythondialog-users] pythondialog is not dead!

[Florent R. <fl...@vi...>]

Chris Dew <ch...@si...> wrote:

> Apologies Florent. I'm really confused - you're not an admin on your
> own project? Oh well, don't worry.

This is in indeed the case. pythondialog is not my "own project" in the
sense that the initial version was written by Robb Shecter. Otherwise,
yes. So, it existed on SourceForge even before I started to work on it.

I've never been much interested in the SF infrastructure. Current status
is not the best I could imagine, and actually worse than it used to be:
full of ads, and the project overview page
(http://sourceforge.net/projects/pythondialog/) doesn't even contain the
word "bug" (yes, I know where to find it). BTW, the "home page"
http://pythondialog.sourceforge.net/ could well use some update...

When I maintained pythondialog in 2002-2004, Google did the proper job
of pointing to my web page where up-to-date info and tarballs were
located. So, I didn't bother asking for SF admin permissions to Robb.
When I handed over the project in 2004, I've been cooperative by making
my web page explain the situation and point to the SF page immediately.

The PyPI situation is even more... pythonesque (in the Monty Python
sense -> nonsensical): exactly *none* of the present or past maintainers
of pythondialog has the right to change the information at
http://pypi.python.org/pypi/pythondialog/. :-)

> I've deleted the github repository, to save any confusion.
>
> All the best for the future of pythondialog.

Thank you.

-- 
Florent

Re: [Pythondialog-users] pythondialog is not dead!

[Chris D. <ch...@si...>]

Apologies Florent.  I'm really confused - you're not an admin on your own
project?  Oh well, don't worry.

I've deleted the github repository, to save any confusion.

All the best for the future of pythondialog.

Chris.

On 16 March 2010 16:04, Florent Rougon <fl...@vi...> wrote:

> Hi,
>
> Chris Dew <ch...@si...> wrote:
>
> > Hi, Peter.
>
> Florent. I'm Florent.
>
> > Firstly, thanks for writing pythondialog.
> >
> > I forked pythondialog to github after having several emails ignored by
> the
> > both of the maintainers on sourceforge for many months.
>
> As written earlier, I am aware of this. As I am not admin of the SF
> project, I did not receive any of these emails. As far as SF stuff is
> concerned, I only read this mailing-list.
>
> > I'm happy to remove the git repo, in order to remove confusion.  Does the
> > new release support password fields (and the other patches submitted to
> > sourceforge)?
>
> Yes, it supports every dialog widget except --tailboxbg (for the dialog
> version in Debian unstable, i.e. 1.1-20100119 as of now).
>
> I reviewed the patches at
> http://github.com/chrisdew/pythondialog/commits/master
>
>  -> patch for labels of Yes or No buttons: added in version 2.10
>  -> "Fix for dialog hang on guage close": as said, it is a workaround,
>     and the problem is likely not to be reproducible with versions 2.09
>     and later. If it is, I am much interested in a way to reproduce it.
>     Thus, patch not applied.
>  -> patch to add --form and --passwordform support: I had already
>     implemented something equivalent in 2.09, except for --insecure
>     (global dialog option). Version 2.10 has support for --insecure.
>
> That is all I can see on your branch. As for the people who are still
> using Xdialog, I incorporated Peter's "use_stdout" keyword argument to
> Dialog.__init__ and _strip_xdialog_newline() method in pythondialog
> 2.10, so they should be happy too.
>
> [ The only thing that might cause a change in Peter's private code, if
>  any (based on my inspection of version 2.7), is that I chose the
>  terminology "(child_output_rfd, child_output_wfd)" instead of
>  "(child_rfd, child_wfd)", because the latter was confusing IMHO. When
>  seeing "child_rfd", you could think it is the pipe read end used by
>  the father process to obtain dialog's output (which was the case in
>  version 2.7), but you could also think it is the pipe read end used by
>  the child process to read input from the father process (as when
>  dialog reads input for --gauge). Same thing with write ends.
>
>  We have 2 sets of read/write fds in dialog.py:
>
>    - one for dialog's output, which I called child_output_[rw]fd in
>      version 2.10 and corresponds to dialog's stderr (normal case) or
>      stdout (workaround for Xdialog's incompatibility);
>
>    - one for dialog's input, which is used in gauge_start (called
>      "child_stdin_[rw]fd") and in progressbox (no pipe created here, fd
>      directly passed to Dailog._perform() with the new
>      "redir_child_stdin_from_fd" keyword argument. ]
>
> --
> Florent
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>



-- 

http://www.finalcog.com/

Re: [Pythondialog-users] pythondialog is not dead!

[Florent R. <fl...@vi...>]

Hi,

Chris Dew <ch...@si...> wrote:

> Hi, Peter.

Florent. I'm Florent.

> Firstly, thanks for writing pythondialog.
>
> I forked pythondialog to github after having several emails ignored by the
> both of the maintainers on sourceforge for many months.

As written earlier, I am aware of this. As I am not admin of the SF
project, I did not receive any of these emails. As far as SF stuff is
concerned, I only read this mailing-list.

> I'm happy to remove the git repo, in order to remove confusion.  Does the
> new release support password fields (and the other patches submitted to
> sourceforge)?

Yes, it supports every dialog widget except --tailboxbg (for the dialog
version in Debian unstable, i.e. 1.1-20100119 as of now).

I reviewed the patches at
http://github.com/chrisdew/pythondialog/commits/master

  -> patch for labels of Yes or No buttons: added in version 2.10
  -> "Fix for dialog hang on guage close": as said, it is a workaround,
     and the problem is likely not to be reproducible with versions 2.09
     and later. If it is, I am much interested in a way to reproduce it.
     Thus, patch not applied.
  -> patch to add --form and --passwordform support: I had already
     implemented something equivalent in 2.09, except for --insecure
     (global dialog option). Version 2.10 has support for --insecure.

That is all I can see on your branch. As for the people who are still
using Xdialog, I incorporated Peter's "use_stdout" keyword argument to
Dialog.__init__ and _strip_xdialog_newline() method in pythondialog
2.10, so they should be happy too.

[ The only thing that might cause a change in Peter's private code, if
  any (based on my inspection of version 2.7), is that I chose the
  terminology "(child_output_rfd, child_output_wfd)" instead of
  "(child_rfd, child_wfd)", because the latter was confusing IMHO. When
  seeing "child_rfd", you could think it is the pipe read end used by
  the father process to obtain dialog's output (which was the case in
  version 2.7), but you could also think it is the pipe read end used by
  the child process to read input from the father process (as when
  dialog reads input for --gauge). Same thing with write ends.

  We have 2 sets of read/write fds in dialog.py:

    - one for dialog's output, which I called child_output_[rw]fd in
      version 2.10 and corresponds to dialog's stderr (normal case) or
      stdout (workaround for Xdialog's incompatibility);

    - one for dialog's input, which is used in gauge_start (called
      "child_stdin_[rw]fd") and in progressbox (no pipe created here, fd
      directly passed to Dailog._perform() with the new
      "redir_child_stdin_from_fd" keyword argument. ]

-- 
Florent

Re: [Pythondialog-users] pythondialog is not dead!

[Chris D. <ch...@si...>]

Hi, Peter.

Firstly, thanks for writing pythondialog.

I forked pythondialog to github after having several emails ignored by the
both of the maintainers on sourceforge for many months.

Several other patches were also being ignored.  I needed these patches and I
had extra functionality to add myself (a password field, iirc).

Ignoring people who want to help with an opensource project is offensive.
 At least tell them that their patches are unworthy to be added to the
project and (possibly) how they could improve them.  If you can't spare the
time to read email, just put a notice on the project page to let people know
that they should not expect a response to any email.

I'm happy to remove the git repo, in order to remove confusion.  Does the
new release support password fields (and the other patches submitted to
sourceforge)?

All the best,

Chris.


On 16 March 2010 11:14, Florent Rougon <fl...@vi...> wrote:

> [ Please don't Cc me, I am already subscribed to the list, thank you. ]
>
> Hello,
>
> Peter Åstrand <as...@ce...> wrote:
>
> > This is all nice and so, but I think we are confusing our users by having
> at
> > least three different "forks" of the project:
> >
> > * Your version
> >
> > * The Sourceforge one
> >
> > * The fork by Chris Dew.
>
> Oops. I do read the mailing-list, but had forgotten the mail where Chris
> Dew announced his reluctant forking of pythondialog to github
> (<e6a...@ma...> from
> Sept. 16, 2008). My fault for that. 2008 was a bad period, and since
> there were no follow-ups to Chris' announcement, it went out of my
> memory. In my enthousiasm updating pythondialog again, I see I also
> implemented --form myself, which he had already implemented at that
> time. Point taken.
>
> > I think this is partly my fault. I've been a poor maintainer for the last
> > years, and I can now see that I've not even responded to the request from
> > Chris Dew to step in as a maintainer. Sorry for that - I haven't kept
> track of
> > the mailing list very well. Please always use my direct email for such
> > important issues.
>
> According to Chris' mail, this is indeed the reason why he did the fork
> to github.
>
> > Btw, does anyone have the email adress to Chris Dew? I've failed to find
> it.
>
> I put in Cc the e-mail address he used on Sept. 16, 2008.
>
> >> ----> Peter, would you be so kind to give me ownership on PyPI? Thanks
> >>      in advance. Similarly with SourceForge, BTW...
> >
> > I don't have access to PyPI. The Package Index Owner is "paulproteus".
> You'll
> > need to contact him. But first of all, I think we should think a little
> bit
> > about merging our 3 forks...
>
> OK. I wrote that because
>
> http://pypi.python.org/pypi?%3Aaction=search&term=pythondialog&submit=search
> listed you as the Author, but the Owner must be "paulproteus" indeed
> (not contacting him before we get out of the current mess, though).
>
> >> The new version is available here:
> >>
> >>  http://people.via.ecp.fr/~flo/projects/pythondialog/dist/
> >
> > You don't use any kind of version control system? This is really bady,
> IMO. I
> > tend to avoid software that lacks proper version control.
>
> Ahem. I did try to commit version 2.09 to the svn repos I set up in
> 2004, but the operation hung. Maybe some dump/reload cycle of the DB
> would be needed. However:
>
> About the "really bady" part: you are free to avoid using my software if
> you are not confident about its quality. Although concerning
> pythondialog, I am afraid that if you actually rip out every line I
> wrote, you won't find much remaining (I would expect: a few lines of the
> demo from Robb Shecter, and the Xdialog patches).
>
> I am a careful and rational person, and for such simple things as
> pythondialog, version control brings basically nothing to me. I don't
> make modifications "just to see if it is going to fix $bug", with the
> intent of rolling back if not. I keep previous versions on my hard
> drive, and I make backups on offline media. This is basic version
> control. When I do an involved modification, I make a backup copy
> beforehand, etc. The software I write, be it public or not, usually has
> relatively few bugs once I declare it usable. I don't think the
> pythondialog case makes an exception here. You are free to disagree, but
> please provide some evidence then.
>
> About version control: of course, it is pretty much vital when several
> people work on the same project. It might be the case here, but ignoring
> Chris' activity, this has not been the view I had when publishing 2.09.
>
> [ However, when only a careful person works on a relatively simple
>  program, version control is useless bloat, frankly. Especially if, a
>  couple of years after being declared as the state-of-the-art of
>  version control software, long-term replacement of the venerable CVS,
>  these "things" are publically qualified as completely obsoleted by the
>  new VCSes, people still using them being said to be "nuts", as seen
>  very recently on lwn.net, in a long discussion mainly about Hg and
>  git. ]
>
> > I can see that Chris Dew uses git. This is not my cup of tee either -
> > I prefer Subversion - but it's way batter than nothing.
>
> Personally, I don't care much. If I work alone, I don't need any of
> these for something simple enough. If not, I am OK with either svn, Hg
> or git (I don't know Hg nor git, but am ready to learn either of these).
>
> > I think that the best solution for pythondialog would be that someone
> like
> > Chris Dew took over the Sourceforge project, migrated to Subversion, and
> then
> > incorporated the various patches floating around, for example your 2.09
> > changes.
>
> The version on http://github.com/chrisdew/pythondialog, as well as that
> on Sourceforge, which has been uploaded to Debian, have seen the
> ChangeLog file **disappear**. When such an important file manages to
> slip out of the releases for more than 5 years, please allow me to
> express my scepticism concerning the actual benefits of "good version
> control practices" in order to ensure top-quality in small projects.
>
> Modern tools don't replace love, care and talent. This has been shown
> many times in arts, craftman's trade, engineering, building...
>
> More prosaically, regarding commit
>
> http://github.com/chrisdew/pythondialog/commit/58be2752c85f63da91f6f2cea5190caab23fece7
> in particular, I'd like to see a test case where the bug is reproducible
> with pythondialog 2.09, because:
>
>         # Close the pipe that we are using to feed dialog's stdin
>         try:
>             p["stdin"].close()
> +            # Doesn't always die on pipe closure
> +            try:
> +                os.kill(p["pid"], signal.SIGTERM)
> +            except:
> +                pass
>
> looks to me more like a workaound than a fix of the root cause. In fact,
> it may well be that this change in version 2.09:
>
>        * dialog.py(__call_program): new close_fds option causing the
>        child process to close the specified file descriptors before the
>        execve(2) system call. This is useful for instance to have the
>        child close an end of a pipe he isn't going to use. Without that,
>        deadlocks could happen because of the child never seeing EOF from
>        the pipe.
>
> as documented in my ChangeLog file, does fix the root cause of the
> problem. Version control with workarounds, or no version control but
> fixing of root causes, which one is more "really bady", according to
> you?
>
> > We are still using Xdialog. Others might as well. I think that just
> removing
> > Xdialog support is totally wrong. If the goal is to remove it, we should
> start
> > by deprecating it in 1 or 2 releases. We can't just suddenly remove it.
>
> Okay, okay, as said, if people are still using it and the patches don't
> impact too much the code, keeping them is fine with me.
>
> >>  [1] Yeah, I know very well it is the same as 2.9 (in the most
> >>      common/sane versioning scheme), but I started this way years ago,
> >>      and 2.09 / 2.10 / etc. sort much better than 2.9 in lexicographic
> >>      order, which is always pleasant in a directory listing such as:
> >
> > I *hate* version numbers like 2.09.
>
> It is your entire right, however I am not sure how rational it is. I am
> definitely *not* confusing 2.1 and 2.10 (in version string context). As
> said, 2.09 sorts better in directory listings (until, of course, 2.99)
> and shouldn't confuse anyone, since 09 == 9 in numeric context. I didn't
> intend to prolonge this scheme ad vitam æternam, but the sorting
> argument plus remaining consistent with previous numbers made me think
> that waiting for 2.10 before switching transparently to the more
> conventional versioning scheme was a perfectly sane course of action.
>
> --
> Florent
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>



-- 

http://www.finalcog.com/

Re: [Pythondialog-users] pythondialog is not dead!

[Florent R. <fl...@vi...>]

[ Please don't Cc me, I am already subscribed to the list, thank you. ]

Hello,

Peter Åstrand <as...@ce...> wrote:

> This is all nice and so, but I think we are confusing our users by having at
> least three different "forks" of the project:
>
> * Your version
>
> * The Sourceforge one
>
> * The fork by Chris Dew.

Oops. I do read the mailing-list, but had forgotten the mail where Chris
Dew announced his reluctant forking of pythondialog to github
(<e6a...@ma...> from
Sept. 16, 2008). My fault for that. 2008 was a bad period, and since
there were no follow-ups to Chris' announcement, it went out of my
memory. In my enthousiasm updating pythondialog again, I see I also
implemented --form myself, which he had already implemented at that
time. Point taken.

> I think this is partly my fault. I've been a poor maintainer for the last
> years, and I can now see that I've not even responded to the request from
> Chris Dew to step in as a maintainer. Sorry for that - I haven't kept track of
> the mailing list very well. Please always use my direct email for such
> important issues.

According to Chris' mail, this is indeed the reason why he did the fork
to github.

> Btw, does anyone have the email adress to Chris Dew? I've failed to find it.

I put in Cc the e-mail address he used on Sept. 16, 2008.

>> ----> Peter, would you be so kind to give me ownership on PyPI? Thanks
>>      in advance. Similarly with SourceForge, BTW...
>
> I don't have access to PyPI. The Package Index Owner is "paulproteus". You'll
> need to contact him. But first of all, I think we should think a little bit
> about merging our 3 forks...

OK. I wrote that because
http://pypi.python.org/pypi?%3Aaction=search&term=pythondialog&submit=search
listed you as the Author, but the Owner must be "paulproteus" indeed
(not contacting him before we get out of the current mess, though).

>> The new version is available here:
>>
>>  http://people.via.ecp.fr/~flo/projects/pythondialog/dist/
>
> You don't use any kind of version control system? This is really bady, IMO. I
> tend to avoid software that lacks proper version control.

Ahem. I did try to commit version 2.09 to the svn repos I set up in
2004, but the operation hung. Maybe some dump/reload cycle of the DB
would be needed. However:

About the "really bady" part: you are free to avoid using my software if
you are not confident about its quality. Although concerning
pythondialog, I am afraid that if you actually rip out every line I
wrote, you won't find much remaining (I would expect: a few lines of the
demo from Robb Shecter, and the Xdialog patches).

I am a careful and rational person, and for such simple things as
pythondialog, version control brings basically nothing to me. I don't
make modifications "just to see if it is going to fix $bug", with the
intent of rolling back if not. I keep previous versions on my hard
drive, and I make backups on offline media. This is basic version
control. When I do an involved modification, I make a backup copy
beforehand, etc. The software I write, be it public or not, usually has
relatively few bugs once I declare it usable. I don't think the
pythondialog case makes an exception here. You are free to disagree, but
please provide some evidence then.

About version control: of course, it is pretty much vital when several
people work on the same project. It might be the case here, but ignoring
Chris' activity, this has not been the view I had when publishing 2.09.

[ However, when only a careful person works on a relatively simple
  program, version control is useless bloat, frankly. Especially if, a
  couple of years after being declared as the state-of-the-art of
  version control software, long-term replacement of the venerable CVS,
  these "things" are publically qualified as completely obsoleted by the
  new VCSes, people still using them being said to be "nuts", as seen
  very recently on lwn.net, in a long discussion mainly about Hg and
  git. ]

> I can see that Chris Dew uses git. This is not my cup of tee either -
> I prefer Subversion - but it's way batter than nothing.

Personally, I don't care much. If I work alone, I don't need any of
these for something simple enough. If not, I am OK with either svn, Hg
or git (I don't know Hg nor git, but am ready to learn either of these).

> I think that the best solution for pythondialog would be that someone like
> Chris Dew took over the Sourceforge project, migrated to Subversion, and then
> incorporated the various patches floating around, for example your 2.09
> changes.

The version on http://github.com/chrisdew/pythondialog, as well as that
on Sourceforge, which has been uploaded to Debian, have seen the
ChangeLog file **disappear**. When such an important file manages to
slip out of the releases for more than 5 years, please allow me to
express my scepticism concerning the actual benefits of "good version
control practices" in order to ensure top-quality in small projects.

Modern tools don't replace love, care and talent. This has been shown
many times in arts, craftman's trade, engineering, building...

More prosaically, regarding commit
http://github.com/chrisdew/pythondialog/commit/58be2752c85f63da91f6f2cea5190caab23fece7
in particular, I'd like to see a test case where the bug is reproducible
with pythondialog 2.09, because:

         # Close the pipe that we are using to feed dialog's stdin
         try:
             p["stdin"].close()
+            # Doesn't always die on pipe closure
+            try:
+                os.kill(p["pid"], signal.SIGTERM)
+            except:
+                pass

looks to me more like a workaound than a fix of the root cause. In fact,
it may well be that this change in version 2.09:

	* dialog.py(__call_program): new close_fds option causing the
	child process to close the specified file descriptors before the
	execve(2) system call. This is useful for instance to have the
	child close an end of a pipe he isn't going to use. Without that,
	deadlocks could happen because of the child never seeing EOF from
	the pipe.

as documented in my ChangeLog file, does fix the root cause of the
problem. Version control with workarounds, or no version control but
fixing of root causes, which one is more "really bady", according to
you?

> We are still using Xdialog. Others might as well. I think that just removing
> Xdialog support is totally wrong. If the goal is to remove it, we should start
> by deprecating it in 1 or 2 releases. We can't just suddenly remove it.

Okay, okay, as said, if people are still using it and the patches don't
impact too much the code, keeping them is fine with me.

>>  [1] Yeah, I know very well it is the same as 2.9 (in the most
>>      common/sane versioning scheme), but I started this way years ago,
>>      and 2.09 / 2.10 / etc. sort much better than 2.9 in lexicographic
>>      order, which is always pleasant in a directory listing such as:
>
> I *hate* version numbers like 2.09.

It is your entire right, however I am not sure how rational it is. I am
definitely *not* confusing 2.1 and 2.10 (in version string context). As
said, 2.09 sorts better in directory listings (until, of course, 2.99)
and shouldn't confuse anyone, since 09 == 9 in numeric context. I didn't
intend to prolonge this scheme ad vitam æternam, but the sorting
argument plus remaining consistent with previous numbers made me think
that waiting for 2.10 before switching transparently to the more
conventional versioning scheme was a perfectly sane course of action.

-- 
Florent

Re: [Pythondialog-users] pythondialog is not dead!

[Peter Å. <as...@ce...>]

Hi, see comments below.

> Well, there has been a long time without any pythondialog release. I
> guess no bug had to be fixed. :)
>
> I am happy to announce version 2.09[1], with enough improvements to
> warrant an announcement here (see the ChangeLog excerpt at the end of

This is all nice and so, but I think we are confusing our users by having 
at least three different "forks" of the project:

* Your version

* The Sourceforge one

* The fork by Chris Dew.

I think this is partly my fault. I've been a poor maintainer for the last 
years, and I can now see that I've not even responded to the request from 
Chris Dew to step in as a maintainer. Sorry for that - I haven't kept 
track of the mailing list very well. Please always use my direct email for 
such important issues.

Btw, does anyone have the email adress to Chris Dew? I've failed to find 
it.



> ----> Peter, would you be so kind to give me ownership on PyPI? Thanks
>      in advance. Similarly with SourceForge, BTW...

I don't have access to PyPI. The Package Index Owner is "paulproteus". 
You'll need to contact him. But first of all, I think we should think a 
little bit about merging our 3 forks...


> The new version is available here:
>
>  http://people.via.ecp.fr/~flo/projects/pythondialog/dist/

You don't use any kind of version control system? This is really bady, 
IMO. I tend to avoid software that lacks proper version control.

I can see that Chris Dew uses git. This is not my cup of tee either - I 
prefer Subversion - but it's way batter than nothing.


I think that the best solution for pythondialog would be that someone like 
Chris Dew took over the Sourceforge project, migrated to Subversion, and 
then incorporated the various patches floating around, for example your 
2.09 changes.


> This catering for Xdialog's incompatibilities with dialog is the only
> pythondialog regression I would expect since version 2.7 (the one on
> SourceForge). Since I am not sure anyone is still using Xdialog, and
> since it presents itself as a _drop-in_ replacement for dialog after
> all, I'd prefer not doing the change if it turns out to be useless.
> However, in case people are *still* using that, I can put it back: it
> wasn't that invasive.

We are still using Xdialog. Others might as well. I think that just 
removing Xdialog support is totally wrong. If the goal is to remove it, we 
should start by deprecating it in 1 or 2 releases. We can't just suddenly 
remove it.



>
>  [1] Yeah, I know very well it is the same as 2.9 (in the most
>      common/sane versioning scheme), but I started this way years ago,
>      and 2.09 / 2.10 / etc. sort much better than 2.9 in lexicographic
>      order, which is always pleasant in a directory listing such as:

I *hate* version numbers like 2.09.



Best regards, 
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00

[Pythondialog-users] pythondialog is not dead!

[Florent R. <fl...@vi...>]

[ Cc'ing Adam Cécile because I don't know if he's subscribed here, and
  it would be nice to have pythondialog updated for squeeze. ]

Hello,

Well, there has been a long time without any pythondialog release. I
guess no bug had to be fixed. :)

I am happy to announce version 2.09[1], with enough improvements to
warrant an announcement here (see the ChangeLog excerpt at the end of
this mail). Basically, every dialog widget is now supported, except for
tailboxbg[2]. This is with the dialog version in Debian unstable, i.e.
1.1-20100119. In addition to support for new widgets, I improved the
internal function _call_program() and the demo (note: if you ever
managed to smile at the previous demo, STAY AWAY FROM THE NEW VERSION:
the jokes contained therein are EVEN MORE LETHAL. You've been warned).

This means I am resuming work on the project, and taking back
ownership... well, so long as I am given back the keys! I updated the
metadata in setup.py to have the Trove classifiers and all, but am
unfortunately not allowed to upload it to PyPI:

  % ./setup.py register
  running register
  Using PyPI login from /home/flo/.pypirc
  Server response (403): You are not allowed to store 'pythondialog'
  package information

Grrrr...

----> Peter, would you be so kind to give me ownership on PyPI? Thanks
      in advance. Similarly with SourceForge, BTW...

The new version is available here:

  http://people.via.ecp.fr/~flo/projects/pythondialog/dist/

with online documentation here:

  http://people.via.ecp.fr/~flo/2002/pythondialog/pythondialog.html

[ The old URLs I used years ago
  (http://people.via.ecp.fr/~flo/2002/pythondialog/dist/ & Co) are still
  valid, but I eventually decided to get rid of this silly naming
  scheme. It may be fine for blog entries or short-term stuff, but not
  for longer-term projects. ]


Future directions
-----------------

As I wrote on http://people.via.ecp.fr/~flo/index.en.xhtml#pythondialog:

  Next things on my TODO list are Python 3 support and properly dealing
  with Unicode strings. For now, non-ASCII characters are supported if
  you encode them before passing them to pythondialog (for instance, to
  UTF-8; of course, the terminal in use must support that encoding).
  However, I think it would be nice to be able to directly use Unicode
  strings, but since this area has seen significant changes between
  Python 2 and Python 3, I don't think it is worth investigating the
  issue before the port to Python 3.


Note to Xdialog users (still anyone out there?)
-----------------------------------------------

I didn't include the use_stdout trick for Xdialog compatibility, because
my impression is that Xdialog is pretty much dead. It still relies on
GTK+ 1.2... and is not in Debian unstable anymore (probably for this
very reason).

This catering for Xdialog's incompatibilities with dialog is the only
pythondialog regression I would expect since version 2.7 (the one on
SourceForge). Since I am not sure anyone is still using Xdialog, and
since it presents itself as a _drop-in_ replacement for dialog after
all, I'd prefer not doing the change if it turns out to be useless.
However, in case people are *still* using that, I can put it back: it
wasn't that invasive.


Changes since version 2.06
--------------------------

2010-03-14  Florent Rougon  <fl...@vi...>

	* Release 2.09.

	* dialog.py: new supported widgets: editbox, inputmenu, mixedform,
	mixedgauge, pause, passwordform, progressbox.

	* demo.py: general improvements, such as:
	    - hopefully more helpful dialog when the user fails to select
	      a file in fselect;
	    - since actually selecting a file with this widget is already
	      boring after the second time, the widget can be exited by
	      pressing Esc or the Cancel button (in which case the parts
	      of the demo that need the file path will be skipped).
	    - replace a few calls to Dialog.scrollbox() by calls to
	      Dialog.msgbox(), since the latter provides nice automatic
	      line wrapping.

	* demo.py: support GNU-style option passing with getopt.py; you
	can use --help to get a list of available options
	* demo.py: no need to change a global variable anymore to switch
	the demo to "fast mode", just use --fast
	* demo.py: add --test-suite mode, mainly for developers: it
	tests *all* widgets, not only those included in the "default
	mode", and automatically enables "fast mode".

	* dialog.py(__call_program): make the function more generic. stdin
	redirection doesn't involve automatic pipe(2) creation in
	__call_program() anymore; instead, __call_program expects a file
	descriptor when it is asked to redirect dialog's stdin (parameter
	'redir_child_stdin_from_fd').

	The caller may still decide to create a pipe and pass its file
	descriptor for reading as the 'redir_child_stdin_from_fd'
	parameter, but the new possibility of redirecting dialog's stdin
	from an arbitrary file descriptor allows for instance to redirect
	it from an existing file, network socket... This is used to
	implement --progressbox cleanly.

	This change has the additional benefit of simplifying the API,
	since __call_program()'s return value is always a 2-element tuple
	now.

	* dialog.py(__call_program): new close_fds option causing the
	child process to close the specified file descriptors before the
	execve(2) system call. This is useful for instance to have the
	child close an end of a pipe he isn't going to use. Without that,
	deadlocks could happen because of the child never seeing EOF from
	the pipe.

	* dialog.py: use warnings.warn(..., DeprecationWarning) for
	obsolete functions.

	* dialog.py: remove convoluted syntax *(<list>,) that was used at
	several places. I don't see any use for this syntax anymore, and
	changing it to simply <list> didn't make the universe collapse (so
	far).

	* dialog.py: prefix attributes for internal use (such as
	Dialog._call_program) with a single underscore instead of a double
	one: we don't need the name mangling here. These underscores in
	dialog.py are just an indication that the attribute is "internal"
	and thus subject to API changes, etc. Thanks to Peter Åstrand for
	pointing this out.

	* setup.py:
	  - improve the long description, use ReStructuredText
	  - add Trove classifiers
	  - add download_url

	* Review and update README, TODO...

2010-02-19  Florent Rougon  <fl...@vi...>

	* dialog.py: add support for --dselect
	* dialog.py: add support for DIALOG_ITEM_HELP
	* demo.py: small fixes

2009-10-31  Florent Rougon  <fl...@vi...>

	* Released 2.08, skipping version 2.07 to avoid creating confusion
	with the 2.7 version released by Peter Åstrand in 2004.

2009-02-04  Florent Rougon  <fl...@vi...>

	* Add support for --form.

	* dialog.py(__call_program): compute the argument list before
	forking, otherwise things get difficult to understand if this
	computation raises an exception.


Footnotes
---------

  [1] Yeah, I know very well it is the same as 2.9 (in the most
      common/sane versioning scheme), but I started this way years ago,
      and 2.09 / 2.10 / etc. sort much better than 2.9 in lexicographic
      order, which is always pleasant in a directory listing such as:

        http://people.via.ecp.fr/~flo/projects/pythondialog/dist/

  [2] tailboxbg looks a bit annoying to support because of the
      --and-widget way of "multiplexing" widgets.

-- 
Florent

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Chris D. <ch...@si...>]

I've reluctantly forked pythondialog to github -
http://github.com/chrisdew/pythondialog/wikis - so that I can produce a 2.8
release.  I tried many times to get in contact with the project admins on
sourceforge, but with no success.

If anyone is interested in contributing, please join the project on github.

I have merged the three patches to 2.7 (from sourceforge), and the demo
still runs ;-)  There is no test suite, beyond the demo, so I hesitate to
call this production-ready.

Regards,

Chris.


2008/1/25 jose mari - gmail <jos...@gm...>

>
> El lun, 19-11-2007 a las 23:49 +0100, Jose Mari escribió:
> > Hi,
> > sorry, in last days I not usually read my e-mail.
> >
> > I think that pythondialog needs some ligth modifications to be similar
> > to dialog, modifications like --form, etc..
> >
> > In the last month I'm working in a project that uses pythondialog and
> > I have been making some modifications, but I'm not sure
> > that  they are important.
> > In my opinion, python dialog would have use a dialog to emulate 'all'
> > functions of original dialog, and (thanks python) correct 'dialog'
> > limitations.
> >
> > If you are interesested in these changes I will be send.
> >
> > In other reason, I think that a code using pythondialog would be
> > compatible with tools like xdialog and zenity, but them have serious
> > limitations (p.e forms).
> >
> > But, thank for your great work. I will be use pythondialog for a long
> time.
> >
> >
> > PS: sorry for my english :-(
> >
> > On Oct 19, 2007 8:32 AM, Chris Dew <cm...@go...> wrote:
> > > Is this still an active project?
> > >
> > > I would like to see a 2.8 release incorporating the '--form patch'
> which I
> > > have submitted 1814393 (and other contributed patches which have been
> > > waiting in sourceforge for 6 months and 48 years ;-) respectively).
> > >
> > > I am willing to produce the 2.8 release, if the current maintainers
> have
> > > lost interest.
> > >
> > > Jose MAri: I may have produced the patch for which your are looking.
>  (I
> > > think there may still be a line of debugging code in there somewhere -
> I'd
> > > not use it in production until it's tested/released.)
> > >
> > > Florent: I don't think Jose had produced a patch - it seemed like a
> feature
> > > request to me.
> > >
> > > Regards,
> > >
> > > Chris.
> > >
> > >
> > >
> > >
> > >
> > > [Pythondialog-users] project active? From: Jose Mari <josemari.mor@gm...> -
> > > 2006-06-30 07:32
> > >
> > >  Attachments: Message as HTML
> > >  <pythondialog-users@li...>Hi,
> > >  I'm using 'pythondialog' to redesign a menu dialogs with bash.
> > >
> > >  Looking the source code I haven't found a form function like 'dialog
> > >  --form', and I patched your code with a function that implements this.
> > >
> > >  Would you like to upload this patch???
> > >
> > >  Thanks!
> > >
> > >
> > >  - Jose MAri -
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Re: [Pythondialog-users] project active? From: Florent Rougon <flo@vi...>
> -
> > > 2006-08-04 15:11
> > >
> > >  Hi,
> > >
> > >  "Jose Mari" <josemari.mor@gm...> wrote:
> > >
> > >  > I'm using 'pythondialog' to redesign a menu dialogs with bash.
> > >  > Looking the source code I haven't found a form function like
> =A0'dialog
> > >  > --form', and I patched your code with a function that implements
> this.
> > >  > Would you like to upload this patch???
> > >
> > >  Ummm, well... obviously, nothing happens on sf.net anymore.
> > >
> > >  I could start maintaining again pythondialog on
> > >  http://people.via.ecp.fr/~flo/ <http://people.via.ecp.fr/%7Eflo/>,
> provided that it isn't too much work
> >  (when I gave the maintainership hat to Peter Astrand, he was using it
> > >  with xdialog, which wasn't perfectly compatible with cdialog, and I
> > >  wasn't personally interested in working around these
> incompatibilities,
> > >  so as I wasn't able to spend enough time on it, I decided to let him
> > >  adopt pythondialog). Maybe I should use another name, such as
> > >  fpythondialog, to avoid confusion. Oh well.
> > >
> > >  Anyway, if you want your patch to be included (after review), you
> should
> > >  send it...
> > >
> > >  --=20
> > >  Florent
> > >
> > >
> > >
> -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > _______________________________________________
> > > Pythondialog-users mailing list
> > > Pyt...@li...
> > > https://lists.sourceforge.net/lists/listinfo/pythondialog-users
> > >
> > >
>
> Hi,
>
> At the end... whereis the last modified version? (maybe 2.8). In sf.net
> is the 2.7+patches version, but not 2.8.
>
> Yesterday, I downloaded the last version of 'dialog', and surprise...
> has a lot of new feature, one a bit interesting: --editbox.
>
> I think that it's util to add some new features, and in next days I will
> write some code to extend the last 'pythondialog' from the last version
> of dialog.
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[jose m. - g. <jos...@gm...>]

El lun, 19-11-2007 a las 23:49 +0100, Jose Mari escribió:
> Hi,
> sorry, in last days I not usually read my e-mail.
> 
> I think that pythondialog needs some ligth modifications to be similar
> to dialog, modifications like --form, etc..
> 
> In the last month I'm working in a project that uses pythondialog and
> I have been making some modifications, but I'm not sure
> that  they are important.
> In my opinion, python dialog would have use a dialog to emulate 'all'
> functions of original dialog, and (thanks python) correct 'dialog'
> limitations.
> 
> If you are interesested in these changes I will be send.
> 
> In other reason, I think that a code using pythondialog would be
> compatible with tools like xdialog and zenity, but them have serious
> limitations (p.e forms).
> 
> But, thank for your great work. I will be use pythondialog for a long time.
> 
> 
> PS: sorry for my english :-(
> 
> On Oct 19, 2007 8:32 AM, Chris Dew <cm...@go...> wrote:
> > Is this still an active project?
> >
> > I would like to see a 2.8 release incorporating the '--form patch' which I
> > have submitted 1814393 (and other contributed patches which have been
> > waiting in sourceforge for 6 months and 48 years ;-) respectively).
> >
> > I am willing to produce the 2.8 release, if the current maintainers have
> > lost interest.
> >
> > Jose MAri: I may have produced the patch for which your are looking.  (I
> > think there may still be a line of debugging code in there somewhere - I'd
> > not use it in production until it's tested/released.)
> >
> > Florent: I don't think Jose had produced a patch - it seemed like a feature
> > request to me.
> >
> > Regards,
> >
> > Chris.
> >
> >
> >
> >
> >
> > [Pythondialog-users] project active? From: Jose Mari <josemari.mor@gm ...> -
> > 2006-06-30 07:32
> >
> >  Attachments: Message as HTML
> >  <pythondialog-users@li...>Hi,
> >  I'm using 'pythondialog' to redesign a menu dialogs with bash.
> >
> >  Looking the source code I haven't found a form function like 'dialog
> >  --form', and I patched your code with a function that implements this.
> >
> >  Would you like to upload this patch???
> >
> >  Thanks!
> >
> >
> >  - Jose MAri -
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Re: [Pythondialog-users] project active? From: Florent Rougon <flo@vi...> -
> > 2006-08-04 15:11
> >
> >  Hi,
> >
> >  "Jose Mari" <josemari.mor@gm...> wrote:
> >
> >  > I'm using 'pythondialog' to redesign a menu dialogs with bash.
> >  > Looking the source code I haven't found a form function like =A0'dialog
> >  > --form', and I patched your code with a function that implements this.
> >  > Would you like to upload this patch???
> >
> >  Ummm, well... obviously, nothing happens on sf.net anymore.
> >
> >  I could start maintaining again pythondialog on
> >  http://people.via.ecp.fr/~flo/, provided that it isn't too much work
>  (when I gave the maintainership hat to Peter Astrand, he was using it
> >  with xdialog, which wasn't perfectly compatible with cdialog, and I
> >  wasn't personally interested in working around these incompatibilities,
> >  so as I wasn't able to spend enough time on it, I decided to let him
> >  adopt pythondialog). Maybe I should use another name, such as
> >  fpythondialog, to avoid confusion. Oh well.
> >
> >  Anyway, if you want your patch to be included (after review), you should
> >  send it...
> >
> >  --=20
> >  Florent
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Pythondialog-users mailing list
> > Pyt...@li...
> > https://lists.sourceforge.net/lists/listinfo/pythondialog-users
> >
> >

Hi,

At the end... whereis the last modified version? (maybe 2.8). In sf.net
is the 2.7+patches version, but not 2.8.

Yesterday, I downloaded the last version of 'dialog', and surprise...
has a lot of new feature, one a bit interesting: --editbox.

I think that it's util to add some new features, and in next days I will
write some code to extend the last 'pythondialog' from the last version
of dialog.

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Jose M. <jos...@gm...>]

Hi,
sorry, in last days I not usually read my e-mail.

I think that pythondialog needs some ligth modifications to be similar
to dialog, modifications like --form, etc..

In the last month I'm working in a project that uses pythondialog and
I have been making some modifications, but I'm not sure
that  they are important.
In my opinion, python dialog would have use a dialog to emulate 'all'
functions of original dialog, and (thanks python) correct 'dialog'
limitations.

If you are interesested in these changes I will be send.

In other reason, I think that a code using pythondialog would be
compatible with tools like xdialog and zenity, but them have serious
limitations (p.e forms).

But, thank for your great work. I will be use pythondialog for a long time.


PS: sorry for my english :-(

On Oct 19, 2007 8:32 AM, Chris Dew <cm...@go...> wrote:
> Is this still an active project?
>
> I would like to see a 2.8 release incorporating the '--form patch' which I
> have submitted 1814393 (and other contributed patches which have been
> waiting in sourceforge for 6 months and 48 years ;-) respectively).
>
> I am willing to produce the 2.8 release, if the current maintainers have
> lost interest.
>
> Jose MAri: I may have produced the patch for which your are looking.  (I
> think there may still be a line of debugging code in there somewhere - I'd
> not use it in production until it's tested/released.)
>
> Florent: I don't think Jose had produced a patch - it seemed like a feature
> request to me.
>
> Regards,
>
> Chris.
>
>
>
>
>
> [Pythondialog-users] project active? From: Jose Mari <josemari.mor@gm ...> -
> 2006-06-30 07:32
>
>  Attachments: Message as HTML
>  <pythondialog-users@li...>Hi,
>  I'm using 'pythondialog' to redesign a menu dialogs with bash.
>
>  Looking the source code I haven't found a form function like 'dialog
>  --form', and I patched your code with a function that implements this.
>
>  Would you like to upload this patch???
>
>  Thanks!
>
>
>  - Jose MAri -
>
>
>
>
>
>
>
>
>
>
> Re: [Pythondialog-users] project active? From: Florent Rougon <flo@vi...> -
> 2006-08-04 15:11
>
>  Hi,
>
>  "Jose Mari" <josemari.mor@gm...> wrote:
>
>  > I'm using 'pythondialog' to redesign a menu dialogs with bash.
>  > Looking the source code I haven't found a form function like =A0'dialog
>  > --form', and I patched your code with a function that implements this.
>  > Would you like to upload this patch???
>
>  Ummm, well... obviously, nothing happens on sf.net anymore.
>
>  I could start maintaining again pythondialog on
>  http://people.via.ecp.fr/~flo/, provided that it isn't too much work
>  (when I gave the maintainership hat to Peter Astrand, he was using it
>  with xdialog, which wasn't perfectly compatible with cdialog, and I
>  wasn't personally interested in working around these incompatibilities,
>  so as I wasn't able to spend enough time on it, I decided to let him
>  adopt pythondialog). Maybe I should use another name, such as
>  fpythondialog, to avoid confusion. Oh well.
>
>  Anyway, if you want your patch to be included (after review), you should
>  send it...
>
>  --=20
>  Florent
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>
>

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Florent R. <flo...@fr...>]

Of course, I meant Google, not SourceForge.

-- 
Florent

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Florent R. <flo...@fr...>]

Hi,

"Noah Slater" <ns...@by...> wrote:

>> Does any one have any objections to moving this to google code hosting?
>> What benefits would that bring?

FWIW, I have no objection to your moving the project on SourceForge.
Sorry, I am not going to review any patch, the reason being health, not
time.

-- 
Florent

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Noah S. <ns...@by...>]

> Does any one have any objections to moving this to google code hosting?
> What benefits would that bring?

SourceForge is slow, bloated and full of adverts.

Google hosting is snappy, light weight yet featureful and easy to use.

> Noah: thanks for your interest - are there specific features which you would
> like to add?

Not sure about features yet as I am not ready to integrate into my own
project but could develop the build system for the package and manage
getting it into PiPy and Debian/Ubuntu.

-- 
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Chris D. <ch...@si...>]

Does any one have any objections to moving this to google code hosting?
What benefits would that bring?

Peter =C5strand and Robb Shecter: are you interested in maintaining this
project?  If not, I am happy to take over for a while (either forking to
google code or on sf.net).  Could you reply within a couple of weeks please=
?


Noah: thanks for your interest - are there specific features which you woul=
d
like to add?

Regards,

Chris.

On 09/11/2007, Noah Slater <ns...@by...> wrote:
>
> > Could you give me ('chrisdew') whatever permissions I need on sf.net in
> > order to produce a 2.8 release, after reviewing the recently contribute=
d
> > patches?
>
> If this project is being taken over by a new maintainer - why not move
> it somewhere that provides a better service than SourceForge, such as
> Google Gode Hosting?
>
> I might be interesting in pitching in on this project - but would
> prefer it hosted at Google.
>
> --
> Noah Slater <http://www.bytesexual.org/>
>
> "Creativity can be a social contribution, but only in so
> far as society is free to use the results." - R. Stallman
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Noah S. <ns...@by...>]

> Could you give me ('chrisdew') whatever permissions I need on sf.net in
> order to produce a 2.8 release, after reviewing the recently contributed
> patches?

If this project is being taken over by a new maintainer - why not move
it somewhere that provides a better service than SourceForge, such as
Google Gode Hosting?

I might be interesting in pitching in on this project - but would
prefer it hosted at Google.

-- 
Noah Slater <http://www.bytesexual.org/>

"Creativity can be a social contribution, but only in so
far as society is free to use the results." - R. Stallman

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Chris D. <ch...@si...>]

Thanks for your reply, I understand that you have no time to work on this
project.

Could you give me ('chrisdew') whatever permissions I need on sf.net in
order to produce a 2.8 release, after reviewing the recently contributed
patches?

Regards,

Chris.

On 29/10/2007, Florent Rougon <f.r...@fr...> wrote:
>
> Hi,
>
> "Chris Dew" <cm...@go...> wrote:
>
> > Is this still an active project?
>
> [...]
>
> > I am willing to produce the 2.8 release, if the current maintainers have
> > lost interest.
>
> [...]
>
> > Florent: I don't think Jose had produced a patch - it seemed like a
> feature
> > request to me.
>
> I cannot work at all on the project in the forseeable future, sorry.
>
> --
> Florent
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Pythondialog-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythondialog-users
>

Re: [Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Florent R. <f.r...@fr...>]

Hi,

"Chris Dew" <cm...@go...> wrote:

> Is this still an active project?

[...]

> I am willing to produce the 2.8 release, if the current maintainers have
> lost interest.

[...]

> Florent: I don't think Jose had produced a patch - it seemed like a feature
> request to me.

I cannot work at all on the project in the forseeable future, sorry.

-- 
Florent

[Pythondialog-users] Status of Project? New '--form patch' available for incorporation.

[Chris D. <cm...@go...>]

Is this still an active project?

I would like to see a 2.8 release incorporating the '--form patch' which I
have submitted 1814393 (and other contributed patches which have been
waiting in sourceforge for 6 months and 48 years ;-) respectively).

I am willing to produce the 2.8 release, if the current maintainers have
lost interest.

Jose MAri: I may have produced the patch for which your are looking.  (I
think there may still be a line of debugging code in there somewhere - I'd
not use it in production until it's tested/released.)

Florent: I don't think Jose had produced a patch - it seemed like a feature
request to me.

Regards,

Chris.



*[Pythondialog-users] project
active?<https://sourceforge.net/mailarchive/message.php?msg_name=6cc459b50606300032n3703ee28x2e87e268523c3551%40mail.gmail.com>
*
From: Jose Mari <josemari.mor@gm...> - 2006-06-30 07:32

*Attachments:* Message as
HTML<https://sourceforge.net/mailarchive/attachment.php?list_name=pythondialog-users&message_id=6cc459b50606300032n3703ee28x2e87e268523c3551%40mail.gmail.com&counter=1>
  <pythondialog-users@li...>Hi,
I'm using 'pythondialog' to redesign a menu dialogs with bash.

Looking the source code I haven't found a form function like 'dialog
--form', and I patched your code with a function that implements this.

Would you like to upload this patch???

Thanks!


- Jose MAri -




     *Re: [Pythondialog-users] project
active?<https://sourceforge.net/mailarchive/message.php?msg_name=8764h8tu2m.fsf%40florent.maison>
   *
   From: Florent Rougon <flo@vi...> - 2006-08-04 15:11
      Hi,

   "Jose Mari" <josemari.mor@gm...> wrote:

   > I'm using 'pythondialog' to redesign a menu dialogs with bash.
   > Looking the source code I haven't found a form function like
   =A0'dialog
   > --form', and I patched your code with a function that implements
   this.
   > Would you like to upload this patch???

   Ummm, well... obviously, nothing happens on sf.net anymore.

   I could start maintaining again pythondialog on
   http://people.via.ecp.fr/~flo/,
<http://people.via.ecp.fr/%7Eflo/,>provided that it isn't too much
work
   (when I gave the maintainership hat to Peter Astrand, he was using it
   with xdialog, which wasn't perfectly compatible with cdialog, and I
   wasn't personally interested in working around these
   incompatibilities,
   so as I wasn't able to spend enough time on it, I decided to let him
   adopt pythondialog). Maybe I should use another name, such as
   fpythondialog, to avoid confusion. Oh well.

   Anyway, if you want your patch to be included (after review), you
   should
   send it...

   --=20
   Florent