Deleting Read Only Nodes in a Reference?

[psy-delacy]

Hopefully this isn't the typical "I have a read only node that I can't delete!" post (researching this issue has lead me to lots of those) -

My problem is that I'm referencing a rig that has a few scripts running on it, and the script calls for deletion.  Technically, the census seems to be you can't delete anything on a reference, but this script deletes most of the nodes, just not all.  The read-only-cannot-delete-nodes are all either orient or parent constraints, so it's not choosing what to delete based on type, and they are all linking back to the same bones and controllers, so I'm confused.  Anyone know why some of these nodes are special?

Also, anyone know how to force delete in a reference using a script (although for that I'll probably have to post in the MEL section)?

[joojaa]

You really can not do this very well. Because basically the idea is that you shouldn't be able to do so. Even if you partially can do this (so your relying on a mistake a d thus should not eb able to do it). So even if you could get it to work you shouldnt rely on this because its quite safe to say that in future you can not do this. So bascially your doing something thats outside of your contract of what should work.

Unload the reference.