HI all 

I am not the too technical guy, but thinking about the new way of
controlling the flow instead of throwing an error.

as of now if we need to break a control and go back exceptions helps,
but it is not a actual way. 

it would be great if we have a control over the frames execution, I mean

A  calls B calls C calls D 

at that point if we think to move directly to B (what error handler do
if that B has the handler defined of the error), changing the frames
instruction pointer to back to the B's position (in python code without
raising an exception) is a really useful for this web applications.

Please excuse me if we have this control already, (can u explain?)

Thanks 
Vinoth

You're talking about adding a non-local goto feature to the language. 
This would be a huge change, and not one that is generally in the
direction that any widespread languages (let alone Python itself) are
going these days.

Please raise this on one of the mailing lists (python-list or
python-ideas), fill out all of the details of how this would work, build
some community support for the feature, write a PEP, and then submit the
PEP to python-dev for consideration.

Actually, Python has non-local gotos already, and in a structured way:
by means of exceptions. I don't understand why it is "not a actual way"
- please do consider using a custom exception for that.

I hope exceptions are not created for that purpose,and it is not the actual*
/*right way i hope. because,

if any of the called methods has the try: except: block, it fails..

and we can't guide other coders, "Don't use try: except:" as it is the
language neutral power.

But it is easy to implement.  Just do as we do in case of exception, but in
a user defined way. I hope.

Thanks
Vinoth

On Tue, Jun 30, 2009 at 2:41 AM, Martin v. Löwis <report@bugs.python.org>wrote:

>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> Actually, Python has non-local gotos already, and in a structured way:
> by means of exceptions. I don't understand why it is "not a actual way"
> - please do consider using a custom exception for that.
>
> ----------
> nosy: +loewis
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue6367>
> _______________________________________
>

So there is a language feature there already that solves your problem
exactly, and you don't want to use it? Exceptions are *exactly* the
right way to provide non-local gotos in a structured manner.

I'm opposed to any change to the language because the desired feature is
already there. Use it. Don't tell that it is the wrong way, it is
exactly the right way.

HI

Exceptions are doing exactly the right way. but what I am telling is a new
way of flow control which no languages currently having.

On Tue, Jun 30, 2009 at 12:14 PM, Martin v. Löwis <report@bugs.python.org>wrote:

>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> So there is a language feature there already that solves your problem
> exactly, and you don't want to use it? Exceptions are *exactly* the
> right way to provide non-local gotos in a structured manner.
>
> I'm opposed to any change to the language because the desired feature is
> already there. Use it. Don't tell that it is the wrong way, it is
> exactly the right way.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue6367>
> _______________________________________
>