From me at crwu.de Mon Oct 17 04:28:47 2016 From: me at crwu.de (Chuanren Wu) Date: Mon, 17 Oct 2016 10:28:47 +0200 Subject: [IPython-dev] Packaging also the debug version ipython_d.exe for MS-Windows Message-ID: Dear developers, is it possible also to package a ipython_d.exe for the debug-version of (officially packaged) python under windows? Since MSVC has different CRTs for debug and released objs, it is not good (perhaps not possible) to mix them. I am relatively new to python, mainly for the reason that I want to provide a binding to my C++ numerical library. With a debug version of ipython_d alongside with the release version is very convenient to debug the binding. Btw, the default numpy packaging for windows has a debug version as well, I did not investigate on how do they achieved that but I think this would not be difficult for ipython. I even don't know whether this request is suitable for a Github ticket, therefore I'd rather send you a email to ask. Best regards C. Wu -------------- next part -------------- An HTML attachment was scrubbed... URL: From takowl at gmail.com Mon Oct 17 07:29:19 2016 From: takowl at gmail.com (Thomas Kluyver) Date: Mon, 17 Oct 2016 12:29:19 +0100 Subject: [IPython-dev] Packaging also the debug version ipython_d.exe for MS-Windows In-Reply-To: References: Message-ID: Hi, I don't think we can easily make such a shortcut, but if you have a debug build of Python, you can launch IPython in it by running: debug-python -m IPython On 17 October 2016 at 09:28, Chuanren Wu wrote: > Dear developers, > > is it possible also to package a ipython_d.exe for the debug-version of > (officially packaged) python under windows? Since MSVC has different CRTs > for debug and released objs, it is not good (perhaps not possible) to mix > them. > I am relatively new to python, mainly for the reason that I want to > provide a binding to my C++ numerical library. With a debug version of > ipython_d alongside with the release version is very convenient to debug > the binding. Btw, the default numpy packaging for windows has a debug > version as well, I did not investigate on how do they achieved that but I > think this would not be difficult for ipython. > > I even don't know whether this request is suitable for a Github ticket, > therefore I'd rather send you a email to ask. > > Best regards > C. Wu > > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at crwu.de Mon Oct 17 08:11:34 2016 From: me at crwu.de (Chuanren Wu) Date: Mon, 17 Oct 2016 14:11:34 +0200 Subject: [IPython-dev] Packaging also the debug version ipython_d.exe for MS-Windows In-Reply-To: References: Message-ID: Hi, thank you for the reply. That seems to work, also with its dependencies. Before the previous email has been launched, I tried `python -m ipython` which didn't work, until I realized that the case matters even on Windows. Best regards C. Wu -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at crwu.de Mon Oct 17 11:56:09 2016 From: me at crwu.de (Chuanren Wu) Date: Mon, 17 Oct 2016 17:56:09 +0200 Subject: [IPython-dev] Packaging also the debug version ipython_d.exe for MS-Windows In-Reply-To: References: Message-ID: Hi, it is still not correct, even after launching `python_d -m IPython` and do nothing except quiting. The following error message is shown: Debug memory block at address p=0000000003C436C0: API 'm' > 3 bytes originally requested > The 7 pad bytes at p-7 are FORBIDDENBYTE, as expected. > The 8 pad bytes at tail=0000000003C436C3 are FORBIDDENBYTE, as > expected. > The block was made by call #1268489 to debug malloc/realloc. > Data at p: 79 0a 00 > Fatal Python error: bad ID: Allocated using API 'm', verified using API 'r' > > Thread 0x000030c4 (most recent call first): > File "C:\Program Files\Python35\lib\threading.py", line 293 in wait > File "C:\Program Files\Python35\lib\threading.py", line 549 in wait > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\core\history.py", > line 834 in run > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\core\history.py", > line 60 in needs_sqlite > File "", line 2 in run > File "C:\Program Files\Python35\lib\threading.py", line 914 in > _bootstrap_inner > File "C:\Program Files\Python35\lib\threading.py", line 882 in _bootstrap > > Current thread 0x00001a0c (most recent call first): > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\utils\py3compat.py", > line 152 in input > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\utils\io.py", > line 172 in ask_yes_no > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\core\interactiveshell.py", > line 3077 in ask_yes_no > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\terminal\interactiveshell.py", > line 426 in interact > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\terminal\interactiveshell.py", > line 440 in mainloop > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\terminal\ipapp.py", > line 348 in start > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\traitlets\config\application.py", > line 596 in launch_instance > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\__init__.py", > line 119 in start_ipython > File > "C:\Users\user1\AppData\Roaming\Python\Python35\site-packages\IPython\__main__.py", > line 14 in > File "C:\Program Files\Python35\lib\runpy.py", line 85 in _run_code > File "C:\Program Files\Python35\lib\runpy.py", line 184 in > _run_module_as_main > Is there any way to fix this issue? Best regards C. Wu 2016-10-17 13:29 GMT+02:00 Thomas Kluyver : > Hi, > > I don't think we can easily make such a shortcut, but if you have a debug > build of Python, you can launch IPython in it by running: > > debug-python -m IPython > > On 17 October 2016 at 09:28, Chuanren Wu wrote: > >> Dear developers, >> >> is it possible also to package a ipython_d.exe for the debug-version of >> (officially packaged) python under windows? Since MSVC has different CRTs >> for debug and released objs, it is not good (perhaps not possible) to mix >> them. >> I am relatively new to python, mainly for the reason that I want to >> provide a binding to my C++ numerical library. With a debug version of >> ipython_d alongside with the release version is very convenient to debug >> the binding. Btw, the default numpy packaging for windows has a debug >> version as well, I did not investigate on how do they achieved that but I >> think this would not be difficult for ipython. >> >> I even don't know whether this request is suitable for a Github ticket, >> therefore I'd rather send you a email to ask. >> >> Best regards >> C. Wu >> >> _______________________________________________ >> IPython-dev mailing list >> IPython-dev at scipy.org >> https://mail.scipy.org/mailman/listinfo/ipython-dev >> >> > > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From takowl at gmail.com Mon Oct 17 11:58:29 2016 From: takowl at gmail.com (Thomas Kluyver) Date: Mon, 17 Oct 2016 16:58:29 +0100 Subject: [IPython-dev] Packaging also the debug version ipython_d.exe for MS-Windows In-Reply-To: References: Message-ID: On 17 October 2016 at 16:56, Chuanren Wu wrote: > Fatal Python error: bad ID: Allocated using API 'm', verified using API 'r' No idea about this, sorry. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidgshi at yahoo.co.uk Mon Oct 17 20:44:31 2016 From: davidgshi at yahoo.co.uk (David Shi) Date: Tue, 18 Oct 2016 00:44:31 +0000 (UTC) Subject: [IPython-dev] Latest updates References: <587947014.37136.1476751471523.ref@mail.yahoo.com> Message-ID: <587947014.37136.1476751471523@mail.yahoo.com> Hello, Where can the latest updates can be found? Regards. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From sburczymuch+ipython at gmail.com Tue Oct 25 13:25:06 2016 From: sburczymuch+ipython at gmail.com (Kossak) Date: Tue, 25 Oct 2016 19:25:06 +0200 Subject: [IPython-dev] Python variables obscur ipdb commands Message-ID: Hi, Is this a bug that python variables obscur ipdb commands? I can't use "n" nor "next" (they return variable value) when there are variables with the same name in the code being debugged. Details are here: http://stackoverflow.com/questions/40224066/ipdb-commands-obscured-by-variables -------------- next part -------------- An HTML attachment was scrubbed... URL: From takowl at gmail.com Tue Oct 25 16:19:42 2016 From: takowl at gmail.com (Thomas Kluyver) Date: Tue, 25 Oct 2016 21:19:42 +0100 Subject: [IPython-dev] Python variables obscur ipdb commands In-Reply-To: References: Message-ID: On 25 October 2016 at 18:25, Kossak wrote: > Is this a bug that python variables obscur ipdb commands? I can't use "n" > nor "next" (they return variable value) when there are variables with the > same name in the code being debugged. Details are here: > http://stackoverflow.com/questions/40224066/ipdb- > commands-obscured-by-variables > It's a feature that was added recently, though I can imagine it may be annoying. Here's the PR that added it: https://github.com/ipython/ipython/pull/9449 Feel free to open an issue asking that it be removed again. I don't have any strong feelings one way or the other, as I don't use the debugger much. Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From H.FANGOHR at soton.ac.uk Tue Oct 25 18:21:44 2016 From: H.FANGOHR at soton.ac.uk (Fangohr H.) Date: Tue, 25 Oct 2016 22:21:44 +0000 Subject: [IPython-dev] Python variables obscur ipdb commands In-Reply-To: References: , Message-ID: <2ABD384A-ED5A-4C9C-B74C-5C7F3E3323DE@soton.ac.uk> I have run into exactly the same problem. It is a difficult call what is better but it is upsetting when 'n' is not moving onto the next statement but prints a value. I'd support deactivating this convenience feature. Or maybe it should not work for variable names that shadow debugger commands? Maybe that is an inoffensive compromise? Best wishes Hans Sent from smartphone On 25 Oct 2016, at 21:20, Thomas Kluyver > wrote: On 25 October 2016 at 18:25, Kossak > wrote: Is this a bug that python variables obscur ipdb commands? I can't use "n" nor "next" (they return variable value) when there are variables with the same name in the code being debugged. Details are here: http://stackoverflow.com/questions/40224066/ipdb-commands-obscured-by-variables It's a feature that was added recently, though I can imagine it may be annoying. Here's the PR that added it: https://github.com/ipython/ipython/pull/9449 Feel free to open an issue asking that it be removed again. I don't have any strong feelings one way or the other, as I don't use the debugger much. Thomas _______________________________________________ IPython-dev mailing list IPython-dev at scipy.org https://mail.scipy.org/mailman/listinfo/ipython-dev From nathan12343 at gmail.com Tue Oct 25 20:39:37 2016 From: nathan12343 at gmail.com (Nathan Goldbaum) Date: Tue, 25 Oct 2016 19:39:37 -0500 Subject: [IPython-dev] Fwd: [Python-ideas] A better interactive prompt In-Reply-To: References: Message-ID: This was just brought up on python-ideas. Perhaps one of the IPython maintainers wants to weigh in? I'd love it if Python could automagically delegate to IPython for interactive sessions if IPython is available. ---------- Forwarded message ---------- From: Paul Moore Date: Tue, Oct 25, 2016 at 4:13 PM Subject: [Python-ideas] A better interactive prompt To: "python-ideas at python.org" I've seen a lot of syntax proposals recently that are based around providing better ways of writing "one liner" styles of code. Typically, the proposals seem to get into trouble because: 1. They duplicate things that can already be done, just not in a single expression/statement. 2. They are seen as over-terse, which is not generally seen as a good thing in Python. However, looking at them from the point of view of someone working at the interactive prompt, they can seem much more attractive. The natural unit of interaction at the command line is the single line. To the extent that (for example) fixing a mistake in a multi-line construct at the command line is a real pain. But these limitations are not inherent to Python - they are problems with the interactive prompt, which is fairly basic[1]. So maybe it's worth looking at the root issue, how to make the interactive prompt easier to use[2]? But that's something of a solved problem. IPython offers a rich interactive environment, for people who find the limitations of the standard interactive prompt frustrating. Would it be worth the standard Python documentation promoting IPython for that role? Maybe even, if IPython is available, allowing the user to configure Python to use it by default as the interactive prompt (a bit like readline, but I dislike the way you can't switch off readline integration if it's installed)? Ideally, if IPython was more readily available, fewer users would be frustrated with Python's existing multi-line constructs. And those that were, would have the option of looking into custom IPython magic commands, before being forced to request language changes. Thoughts? Paul [1] On the other hand, the interactive prompt is a huge part of what makes Python so great - these days, when I have to code in languages that don't have an interactive prompt, it drives me nuts. And even those that do, typically don't have one as good as Python's (in spite of the fact that this whole mail is about needing to improve the Python REPL). [2] My apologies to anyone whose proposal was *not* based around interactive use cases. I'm assuming motives here left, right and centre, so if what I'm saying isn't what you were intending, that's fine. Treat this as an unrelated proposal. _______________________________________________ Python-ideas mailing list Python-ideas at python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sburczymuch+ipython at gmail.com Wed Oct 26 07:04:44 2016 From: sburczymuch+ipython at gmail.com (Kossak) Date: Wed, 26 Oct 2016 13:04:44 +0200 Subject: [IPython-dev] Python variables obscur ipdb commands In-Reply-To: <2ABD384A-ED5A-4C9C-B74C-5C7F3E3323DE@soton.ac.uk> References: <2ABD384A-ED5A-4C9C-B74C-5C7F3E3323DE@soton.ac.uk> Message-ID: I created issue here: https://github.com/ipython/ipython/issues/10037 I also think it would be best if ipdb commands were working reliably all the time. (in all other cases, when python variable is not ipdb command at the same time, we should be able to display it without '!') On Wed, Oct 26, 2016 at 12:21 AM, Fangohr H. wrote: > I have run into exactly the same problem. It is a difficult call what is > better but it is upsetting when 'n' is not moving onto the next statement > but prints a value. > > I'd support deactivating this convenience feature. Or maybe it should not > work for variable names that shadow debugger commands? Maybe that is an > inoffensive compromise? > > Best wishes > > Hans > > Sent from smartphone > > On 25 Oct 2016, at 21:20, Thomas Kluyver l at gmail.com>> wrote: > > On 25 October 2016 at 18:25, Kossak sburczymuch+ipython at gmail.com>> wrote: > Is this a bug that python variables obscur ipdb commands? I can't use "n" > nor "next" (they return variable value) when there are variables with the > same name in the code being debugged. Details are here: > http://stackoverflow.com/questions/40224066/ipdb- > commands-obscured-by-variables > > It's a feature that was added recently, though I can imagine it may be > annoying. Here's the PR that added it: > https://github.com/ipython/ipython/pull/9449 > > Feel free to open an issue asking that it be removed again. I don't have > any strong feelings one way or the other, as I don't use the debugger much. > > Thomas > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: