Hello,

here is the patch which includes the documentation modification asked by Eli:

> In that case, I suggest to say it is deprecated and kept for backward
> compatibility, and advise which alternative should be used instead.

+ This function is maintained for backward compatibility and is now deprecated
+ in favor of @code{gdb.BreakpointEvent.breakpoints()}.


Thanks,

Kevin

--

2011-04-30  Kevin Pouget  <kevin.pouget@st.com>

	Handle multiple breakpoint hits in Python interface:
	* gdb.texinfo (Events In Python): Indicate that multiple breakpoint
	may have been hit and rename the variable to breakpoints.

2011-04-30  Kevin Pouget  <kevin.pouget@st.com>

	Handle multiple breakpoint hits in Python interface:
	* python/py-bpevent.c (create_breakpoint_event_object): Rename C/Python
	variable to breakpoints.
	* python/py-stopevent.c (emit_stop_event): Return a Python tuple of
	bps instead of single breakpoint. Fix some space typos.
	* python/py-stopevent.c (create_breakpoint_event_object): Rename
	variable to breakpoints.

2011-04-30  Kevin Pouget  <kevin.pouget@st.com>

	Handle multiple breakpoint hits in Python interface:
	* gdb.python/py-events.exp: Set a duplicate breakpoint and check its
	presence.
	* gdb.python/py-events.py (breakpoint_stop_handler): Browse all the
	breakpoint hits.


On Fri, May 27, 2011 at 4:09 PM, Tom Tromey <tromey@redhat.com> wrote:
>
> >>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
>
> Kevin> I put back the breakpoint attribute in addition to the "breakpoints"
> Kevin> sequence and added in the documentation that it was "legacy support",
> Kevin> is it okay for you?
>
> Yes.
>
> Many of your patches seem ready to me.  A couple still may need doc
> review.  IIRC, your paperwork isn't done yet, so at this point we must
> wait for that.  I don't recall when you sent things in, if it has been a
> while you might consider pinging the FSF copyright clerk.
>
> Tom