On Mon, Nov 16, 2015 at 12:48 PM, Alan Gauld
wrote:
>
>
> The correct fix is to exit() from the python3 shell and start it again.
>>
>
> He's tried that and didn't find it satisfactory. That's why
> he wants a "better" workflow.
>
> Alternatively, add some main code at the end of your file and use
On 16/11/15 15:42, Chris Warrick wrote:
On 16 November 2015 at 15:43, Alan Gauld wrote:
Thats not an IDE its just a raw interpreter.
IDLE is a full IDE that includes a debugger.
It’s an awful piece of garbage that pretends to be an IDE.
Would you care to expand. Its been doing a fair impres
On 16 November 2015 at 15:43, Alan Gauld wrote:
> Thats not an IDE its just a raw interpreter.
> IDLE is a full IDE that includes a debugger.
It’s an awful piece of garbage that pretends to be an IDE.
>> I encountered some error in the source , then I fixed it and tried to run
>> the module with
On 16/11/15 09:55, Sajjadul Islam wrote:
Hello forum,
I am trying Python 3.4 on Ubuntu and I am a bit confused with the debugging
scope of python in general.
I wrote a small function and then I tried to run with the following call:
///
import hilbert
hilbert.hilbert(3)
Hello forum,
I am trying Python 3.4 on Ubuntu and I am a bit confused with the debugging
scope of python in general.
I wrote a small function and then I tried to run with the following call:
///
import hilbert
hilbert.hilbert(3)
///
Please note
