Re: Python mode failures with xemacs

Andreas Röhler writes: Looking at your bug tracker is not our job. If there were a volunteer to maintain our python-modes package, it would be his or her job. That's why we give external maintainers so much privilege and power over their packages. They take care of maintaining contact between XEmacs and package upstream -- and besides the minimal skills needed to type "cp upstream.el xemacs-version.el; cvs commit", that is our *only* requirement for a package maintainer, although it's nice if they can provide some development knowledge and effort, too -- and they need as much freedom to do that work as we can give them. When a package is listed with "XEmacs Development Team" as maintainer, that means that there is nobody willing to do that work, but the XEmacs Dev Team will put in some effort to address bugs reported to us. So if you want attention to a particular bug, you need to report it here (or on the tracker). If it's something you can and will provide a workaround or internal fix for, the discussion can take place on whichever tracker is more convenient for your purposes. But if it's primarily something you wish XEmacs would change, if it's not on an XEmacs channel, the reality is it's not going to get enough attention. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta