On Tue, Oct 25, 2011 at 3:52 PM, Daniel Hyams wrote:
> For small bugfixes, am I supposed to fork from v1.1.x, or master?
I say 'master' (Mike's been pushing some things to v1.1.x, but as he
said in a comment to #551, "Pushed to v1.1.x since this is pretty
serious yet simple-to-fix bug -- it shou
On Tuesday, October 25, 2011, Daniel Hyams wrote:
> For small bugfixes, am I supposed to fork from v1.1.x, or master?
>
V1.1.x is the maintenance branch. Master is for new features. When
bugfixes are made and merged to v1.1.x, we then merge it to master.
Ben Root
--
For small bugfixes, am I supposed to fork from v1.1.x, or master?
--
Daniel Hyams
dhy...@gmail.com
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is grow
Daniel -
Yes that works. In my case - I hate to edit any existing third party
code bases - or it bites me later when I upgrade.
For now - I simply do my own dead reference clean up externally when
doing the deletes. Really, that would be the same as just doing a
disconnect - but for othe
I've run into this same issue in the past, and have it "fixed" in my
own local copy of matplotlib. I just placed a check to make sure that
cid actually was in the callbacks for s before deleting it.
That is quite possibly a band-aid; I never looked far enough in to
see. But it is possibly anothe
Here is a bit more detail and a simple example.
The example below places red squares in an axes. When the user clicks on an
existing red square - another square is created and added. When the user hits
any key a square is deleted from the axes. The error is triggered by clicking
on the red sq
