pywin32-bugs Mailing List for Python for Windows Extensions (Page 33)
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
Menu
▾
▴
pywin32-bugs — Automated tracker notifications (not for bug reports!)
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(24) |
May
(19) |
Jun
(15) |
Jul
(43) |
Aug
(39) |
Sep
(25) |
Oct
(43) |
Nov
(19) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(21) |
Feb
(18) |
Mar
(14) |
Apr
(80) |
May
(56) |
Jun
(24) |
Jul
(30) |
Aug
(17) |
Sep
(36) |
Oct
(106) |
Nov
(38) |
Dec
(30) |
| 2005 |
Jan
(14) |
Feb
(14) |
Mar
(48) |
Apr
(28) |
May
(49) |
Jun
(23) |
Jul
(9) |
Aug
(13) |
Sep
(28) |
Oct
(21) |
Nov
(8) |
Dec
(26) |
| 2006 |
Jan
(56) |
Feb
(33) |
Mar
(33) |
Apr
(18) |
May
(16) |
Jun
(9) |
Jul
(24) |
Aug
(16) |
Sep
(14) |
Oct
(37) |
Nov
(38) |
Dec
(22) |
| 2007 |
Jan
(7) |
Feb
(16) |
Mar
(11) |
Apr
(15) |
May
(15) |
Jun
(8) |
Jul
(24) |
Aug
(26) |
Sep
(18) |
Oct
(11) |
Nov
(20) |
Dec
(1) |
| 2008 |
Jan
(19) |
Feb
(55) |
Mar
(7) |
Apr
(35) |
May
(66) |
Jun
(38) |
Jul
(26) |
Aug
(5) |
Sep
(25) |
Oct
(25) |
Nov
(18) |
Dec
(18) |
| 2009 |
Jan
(25) |
Feb
(38) |
Mar
(29) |
Apr
(25) |
May
(5) |
Jun
(11) |
Jul
(16) |
Aug
(16) |
Sep
(16) |
Oct
(1) |
Nov
(15) |
Dec
(33) |
| 2010 |
Jan
(13) |
Feb
(11) |
Mar
(1) |
Apr
(24) |
May
(26) |
Jun
(19) |
Jul
(22) |
Aug
(51) |
Sep
(38) |
Oct
(39) |
Nov
(25) |
Dec
(27) |
| 2011 |
Jan
(40) |
Feb
(31) |
Mar
(21) |
Apr
(42) |
May
(11) |
Jun
(16) |
Jul
(20) |
Aug
(14) |
Sep
(6) |
Oct
(8) |
Nov
(34) |
Dec
(7) |
| 2012 |
Jan
(60) |
Feb
(24) |
Mar
(6) |
Apr
(28) |
May
(41) |
Jun
(15) |
Jul
(14) |
Aug
(25) |
Sep
(30) |
Oct
(18) |
Nov
(30) |
Dec
(9) |
| 2013 |
Jan
(3) |
Feb
(8) |
Mar
(17) |
Apr
(23) |
May
(34) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:59:52
|
Patches item #3048869, was opened at 2010-08-20 04:53 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048869&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: F1 auto keyword help; Interact with edit lines Initial Comment: F1 keyword help F1: Python Help Ctrl+F1: PythonWin Alt+F1: MSDN Numpy & wx quick debugging and trying things out (Ctrl-Enter Debugger can be used also after that:) Ctrl-K : interact with marked editor lines in Interactive (in __main__) Ctrl-E : exectued marked editor lines in Interactive (in __main__) (works also while in debugger;) ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:59 Message: Thanks! But I think I'd prefer to see most of the help functionality in pywin/framework/help.py which already has support for the help menus. If we have support for the keyboard for these new help files, the menu should probably get them too (which the short-cut keys included) - but that might make things ugly given many people may not have wx or numpy installed. I wonder how hard it would be to refactor some of that and only show menu items if the help file is installed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048869&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:55:32
|
Patches item #3048845, was opened at 2010-08-20 04:05 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048845&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: correct tracebacks for errors in default.cfg Initial Comment: for pywin/scintilla/config.py ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:55 Message: Thanks! checking in config.py; new revision: 1.10; previous revision: 1.9 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048845&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:52:11
|
Patches item #3048854, was opened at 2010-08-20 04:22 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048854&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: mdi_pychecker_update.patch Initial Comment: few things didn't work smooth ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:52 Message: I just changed scriptutils.JumpToDocument to return None on error and your recent patch changed it to return the view object on success - so I think the second part of this patch is no longer needed. What is the first part for? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048854&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:49:42
|
Patches item #3048858, was opened at 2010-08-20 04:30 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048858&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: correct_package_sub_import_and_pyx_support.patch Initial Comment: modules deep in a package tree were not correctly imported upon Ctrl-I (Menu/File/Import) .pyx / Cython / PyRex (with auto pyximport) cannot be also imported / loaded. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:49 Message: Checked in with a minor tweak - thanks .Checking in CHANGES.txt; new revision: 1.56; previous revision: 1.55 Checking in pythonwin/pywin/framework/scriptutils.py; new revision: 1.26; previous revision: 1.25 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048858&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:40:22
|
Patches item #3048860, was opened at 2010-08-20 04:35 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048860&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: debugger_run_basestrings.patch Initial Comment: sometimes required. (maybe the other Ctrl-Enter gebugger patch needs this, as there is now unicode flowing from scintilla...) ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:40 Message: Thanks! Checking in debugger.py; new revision: 1.26; previous revision: 1.25 done ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048860&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-25 07:37:37
|
Patches item #3048863, was opened at 2010-08-20 04:38 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048863&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: better_doc_calltips.patch Initial Comment: certain doc strings with leading white space line (wxPython etc) didn't say anything in PythonWin call tips ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 17:37 Message: thanks! Checking in CHANGES.txt; new revision: 1.55; previous revision: 1.54 Checking in Pythonwin/pywin/idle/CallTips.py; new revision: 1.6; previous revision: 1.5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048863&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-24 22:56:13
|
Bugs item #3052431, was opened at 2010-08-25 04:13 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3052431&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Ian Hobson (ianhobson) Assigned to: Nobody/Anonymous (nobody) Summary: Still a problem Initial Comment: I have just had this same problem when re-installing Python on Windows 7 64 bit (although installing 32 bit python). ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-08-25 08:56 Message: Please add a comment to the original bug - I've no idea what is still a problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3052431&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-24 18:13:07
|
Bugs item #3052431, was opened at 2010-08-24 18:13 Message generated for change (Tracker Item Submitted) made by ianhobson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3052431&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ian Hobson (ianhobson) Assigned to: Nobody/Anonymous (nobody) Summary: Still a problem Initial Comment: I have just had this same problem when re-installing Python on Windows 7 64 bit (although installing 32 bit python). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3052431&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-20 15:45:22
|
Patches item #1446700, was opened at 2006-03-09 20:32 Message generated for change (Settings changed) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=1446700&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted >Resolution: Out of Date Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: 4 (+1) Patches to speed up edit-help-debug-run-cycle Initial Comment: Patches: 4 (+1) Patches to speed up the edit-help-debug-run-cycle significantly ================================ pywin.framework.interact : * Ctrl-RETURN in interactive window executes the command directly in debugger ( very nice to speedup edit-run-cycle 2x; don't know how to live without; very helpful also to enter quickly into source code of imported modules ) pywin.scintilla.view : * Ctrl-E : "Execute region" : runs code snippet (auto-unindented), which is marked currently in editor, in interactive namespace ( very nice to speedup edit-run-cycle 2x; don't know how to live without; ) ( similar to Python mode in XEmacs: "Execute Region" ) ( executes currently in __main__.__dict__ ; to be consistent during debugging the current interp-namespace should be used; found no easy link to get this namespace ) * Ctrl-Y : context senitive Python help for smartly guessed words/funcs around cursor in "c:/python23/Doc/Python23.chm" ( is hardwired as of now :-( . should take the CHM-location out of registry ) ( should be put to Ctrl-F1 and maybe to a framework module; Don't know how to bind keys like Ctrl-F1 ) * Ctrl-Q : context senitive PythonWin help for smartly guessed words/funcs around cursor parallel in hf= "c:/python23/lib/site-packages/pywin32.chm" and hf=r"C:\Programme\Microsoft Visual Studio\MSDN98\98VSa\1033\msdnvs6a.col" (hard wiring still to be virtualized; ) ( win32help.HtmlHelp doesn't raise if file non-existing, but returns 0; not checked/no error action as of now ) pywin.mfc.docview , pywin.framework.intpyapp : * repairs the fatal call from pywin.mfc.docview.DocTemplate._SetupSharedMenu_ into a framework module ( that problem crashed py2exe'd apps without Pythonwin framework, but which use the DocTemplate ) ================= apply: cd C:/python23/lib/site-packages/pythonwin/pywin patch -b -p 4 <pywrk.diff created with: diff -ur . /iBase/python/pywin-framework-patched-files >pywrk.diff ---------------------------------------------------------------------- >Comment By: kxroberto (kxroberto) Date: 2010-08-20 17:45 Message: was replaced by 3048869 , 3048851 ---------------------------------------------------------------------- Comment By: kxroberto (kxroberto) Date: 2007-01-03 15:19 Message: Logged In: YES user_id=972995 Originator: YES pywin32_rkdev2.patch is updated & more clean. It loads the help files already as configured in the registry etc. The "Ctrl-RETURN debugger" (from interactive statement), and the "execute region" functions are more stable and clear now. Still not done are the keybindings for Ctrl-F1/Ctrl-Shift-F1 .. - as I have difficulties to figure out how to get this. Feature Request: Maybe there could be a new * Menu\\Interactive which has the * Menu\\Interactive\\History Back\tCtrl-Up * Menu\\Interactive\\History Forward\tCtrl-Down * Menu\\Interactive\\Debug Statement\tCtrl-RETURN * Menu\\Interactive\\--- * Menu\\Interactive\\Execute Marked Code Region/Line\tCtrl-E * Menu\\Interactive\\Interact Marked Code Region/Line\tCtrl-K and * Menu\\Help\\Python Manuals\tF1 * Menu\\Help\\PythonWin Reference\tShift-F1 * Menu\\Help\\Context Help Python\tCtrl-F1 * Menu\\Help\\Context Help PythonWin\tCtrl-Shift-F1 (mostly in order to announce the key bindings comfortably.) PS: And a strange frequent framework bug (around "SCIMarkerDeleteAll") is addressed though I don't know why "getattr(self.GetEditorView(),'SCIMarkerDeleteAll',None)" can at all return a None - but it actually did so. File Added: pywin32_rkdev2.patch ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2006-03-22 23:28 Message: Logged In: YES user_id=14198 OK, thanks. I'll try and get back to this - I obviously have a lot on my plate though, and getting this ready to check in isn't going to be an insignificant amount of time. ---------------------------------------------------------------------- Comment By: kxroberto (kxroberto) Date: 2006-03-22 12:59 Message: Logged In: YES user_id=972995 I'll probably not enhance the patch myself. The main remaining difficulties are to get the right key bindings (Ctrl-F1/Ctrl-Shitf-F1 ..) work and for Ctrl-ENTER-debug to get the virtual interactive globals from somewhere. I didn't grasp the required concepts in reasonable time. ======== Ctrl-Shift-Enter : also acceptable - but pressing [Ctrl]+[Enter] for '\'+'n' - thats a habit or :-) ========= help files from registry: found its just 2 lines: import regutil hf = regutil.GetRegisteredHelpFile("Main Python Documentation") import regutil hf = regutil.GetRegisteredHelpFile("Pythonwin Reference") ========== launching 2 helpfiles Pywin & MSDN in a row: thats maybe not a regular behavior, just practical for me: I often need to lookup the windows constants and other basics in parallel, as they are not in the pywin CHM. For a streamlined pythonwin: Maybe just drop the call to MSDN helpfile - or later a more expensive solution: menu item "Menu/help/Context sensitive help .." to add/see user definable key+helpfile pairs. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2006-03-22 11:00 Message: Logged In: YES user_id=14198 Interesting - this has potential! :) * I'm not that keen on adopting Ctrl+Enter - that is what I personally use for 'insert \n into code' - how about Ctrl+Shift+Enter * OnKeyCtrlE - print statements should be removed, but a nice concept! * hf="c:/python23/Doc/Python23.chm" etc - as you say, "hard wiring still to be virtualized" - please do! :) The block: + else: + hf=r"C:\Programme\Microsoft Visual Studio\MSDN98\98VSa\1033\msdnvs6a.col" + win32help.HtmlHelp(0, hf, win32help.HH_DISPLAY_INDEX, word) + hf= "c:/python23/lib/site-packages/pywin32.chm" + win32help.HtmlHelp(0, hf, win32help.HH_DISPLAY_INDEX, word) doesn't look right as it calls HtmlHelp twice. It would be great to work out how to do that help properly! * re "repairs the fatal call from pywin.mfc.docview.DocTemplate._SetupSharedMenu_" - can you be more specific about the problem you see? I'm not that happy with that patch - a patch that just changes all refernces to _SetupSharedMenu, rather than "injecting" it, would be preferred. I'm happy to see the interest, and hope you can update your patch! Just the .diff file is fine (.patch is my preference, but either is fine :) - no need to .zip, nor to attach the modified files. Cheers, Mark ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=1446700&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:53:41
|
Patches item #3048869, was opened at 2010-08-19 20:53 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048869&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: F1 auto keyword help; Interact with edit lines Initial Comment: F1 keyword help F1: Python Help Ctrl+F1: PythonWin Alt+F1: MSDN Numpy & wx quick debugging and trying things out (Ctrl-Enter Debugger can be used also after that:) Ctrl-K : interact with marked editor lines in Interactive (in __main__) Ctrl-E : exectued marked editor lines in Interactive (in __main__) (works also while in debugger;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048869&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:38:14
|
Patches item #3048863, was opened at 2010-08-19 20:38 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048863&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: better_doc_calltips.patch Initial Comment: certain doc strings with leading white space line (wxPython etc) didn't say anything in PythonWin call tips ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048863&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:35:11
|
Patches item #3048860, was opened at 2010-08-19 20:35 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048860&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: debugger_run_basestrings.patch Initial Comment: sometimes required. (maybe the other Ctrl-Enter gebugger patch needs this, as there is now unicode flowing from scintilla...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048860&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:30:09
|
Patches item #3048858, was opened at 2010-08-19 20:30 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048858&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: correct_package_sub_import_and_pyx_support.patch Initial Comment: modules deep in a package tree were not correctly imported upon Ctrl-I (Menu/File/Import) .pyx / Cython / PyRex (with auto pyximport) cannot be also imported / loaded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048858&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:22:39
|
Patches item #3048854, was opened at 2010-08-19 20:22 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048854&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: mdi_pychecker_update.patch Initial Comment: few things didn't work smooth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048854&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:15:54
|
Patches item #3048851, was opened at 2010-08-19 20:15 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048851&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: ctrl-enter-debug-into-interactive-statement.patch Initial Comment: quickly debug into things from the interactive. Ctrl+Enter = Enter with control ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048851&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:10:31
|
Patches item #3048850, was opened at 2010-08-19 20:10 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048850&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: runs PYTHONSTARTUP (as any comfortabl interactive should do) Initial Comment: -> framwork/interact.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048850&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:05:41
|
Patches item #3048845, was opened at 2010-08-19 20:05 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048845&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: correct tracebacks for errors in default.cfg Initial Comment: for pywin/scintilla/config.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048845&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-08-19 18:02:31
|
Patches item #3048829, was opened at 2010-08-19 20:02 Message generated for change (Tracker Item Submitted) made by kxroberto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048829&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: finally supports non-US keyboards (CallTips etc) Initial Comment: comfort for the whole world .. patch for keycodes.py in pywin/scintilla ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3048829&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-24 20:16:29
|
Feature Requests item #3005507, was opened at 2010-05-21 15:01 Message generated for change (Settings changed) made by kf7xm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3005507&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Accepted >Priority: 2 Private: No Submitted By: Airdrik (airdrik) Assigned to: Nobody/Anonymous (nobody) Summary: adodbapi distinguishing of datetime and date Initial Comment: In MS SQL server, there are two date types: datetime and smalldatetime; datetime has a time component and smalldatetime does not. in adodbapi, they both come in as basically the same type and adodbapi converts them both to python's datetime.date if the time component is 0 or to datetime.datetime otherwise. This leads to possible type differences if a datetime column sometimes has a time component of midnight, and sometimes has other times (for some strange reason datetime.date and datetime.datetime are not comparable). I would prefer that sql datetime get converted to python datetime.datetime (regardless of if the time component), and sql smalldatetime get converted to python datetime.date (with the exception that sql null get converted to None regardless). Part of the problem of distinguishing these types is that the type_code of both datetime and smalldatetime is 135 (adDBTimeStamp), however they can be distinguished by the scale field of .description - the scale on datetime is 3, whereas the scale on smalldatetime is 0. ---------------------------------------------------------------------- Comment By: Vernon Cole (kf7xm) Date: 2010-07-24 14:15 Message: This "feature" has bitten me, too. I like your proposed solution and will investigate using it. -- Vernon ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3005507&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-24 20:15:52
|
Feature Requests item #3005507, was opened at 2010-05-21 15:01 Message generated for change (Comment added) made by kf7xm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3005507&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Airdrik (airdrik) Assigned to: Nobody/Anonymous (nobody) Summary: adodbapi distinguishing of datetime and date Initial Comment: In MS SQL server, there are two date types: datetime and smalldatetime; datetime has a time component and smalldatetime does not. in adodbapi, they both come in as basically the same type and adodbapi converts them both to python's datetime.date if the time component is 0 or to datetime.datetime otherwise. This leads to possible type differences if a datetime column sometimes has a time component of midnight, and sometimes has other times (for some strange reason datetime.date and datetime.datetime are not comparable). I would prefer that sql datetime get converted to python datetime.datetime (regardless of if the time component), and sql smalldatetime get converted to python datetime.date (with the exception that sql null get converted to None regardless). Part of the problem of distinguishing these types is that the type_code of both datetime and smalldatetime is 135 (adDBTimeStamp), however they can be distinguished by the scale field of .description - the scale on datetime is 3, whereas the scale on smalldatetime is 0. ---------------------------------------------------------------------- >Comment By: Vernon Cole (kf7xm) Date: 2010-07-24 14:15 Message: This "feature" has bitten me, too. I like your proposed solution and will investigate using it. -- Vernon ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3005507&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-23 12:38:47
|
Bugs item #3033529, was opened at 2010-07-23 08:38 Message generated for change (Tracker Item Submitted) made by jaraco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3033529&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jason R. Coombs (jaraco) Assigned to: Nobody/Anonymous (nobody) Summary: error in GetClipboardData - handle invalid on GlobalLock Initial Comment: A long time ago, a user reported problems getting a bitmap from the Windows clipboard: http://mail.python.org/pipermail/python-win32/2001-May/000056.html The tail end of that thread indicates that the patch was applied, but I see in the current code base, the NotImplementedError is not raised for CF_BITMAP. Instead, if I get the original error if I attempt to get a bitmap from the clipboard: # after hitting PrtScn to put a bitmap on the clipboard >>> import win32clipboard as wclip >>> wclip.OpenClipboard() >>> result = wclip.GetClipboardData(wclip.CF_BITMAP) Traceback (most recent call last): File "<stdin>", line 1, in <module> pywintypes.error: (6, 'GetClipboardData:GlobalLock', 'The handle is invalid.') If win32clipboard doesn't support the CF_BITMAP for GetClipboardData, it should provide a useful message indicating such, rather than a surprising message about an invalid handle. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3033529&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-20 21:43:59
|
Bugs item #2907614, was opened at 2009-12-02 09:27 Message generated for change (Comment added) made by urban_dk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2907614&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: marvin greenberg (marvingreenberg) Assigned to: Nobody/Anonymous (nobody) Summary: PYWIN32 not identifying current WINVER correctly (v214) Initial Comment: I'm building python from source, then using that build to build pywin32 from source (to satisfy some requirements of our build environment). This succeeds fine when the build machine is XP SP2 with VIsualStudio VC90, but when the installed dev env is VC80 it fails. Python builds and installs fine. PYWIN32 builds, but as it builds there are a variety of messages "Unable to import verstamp, no version info will be added" Googling seems to indicate this issue has been resolved, and there is not any error copying, e.g. pywintypes, like "copying build\temp.win32-2.6\Release\win32\src\pywintypes26.lib -> build\temp.win32-2.6\Release\pywintypes.lib" When PYWIN32 gets to trying to build win32process extensions, I get win32/src/win32process_py2_swig.cpp(2635) : error C2065: 'THREAD_MODE_BACKGROUND_BEGIN' : undeclared identifier win32/src/win32process_py2_swig.cpp(2637) : error C2065: 'THREAD_MODE_BACKGROUND_END' : undeclared identifier I also get warnings like: "cl : Command line warning D9002 : ignoring unknown option '/YXPyWinTypes.h' PyACL.cpp" Which all seems to imply WINVER is being set to the wrong value. And indeed early in the build process, I see "Found version 0x500 in C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\WinResrc.h" Now my VIsual Studio IDE is up to date, and XP SP2 should be 0x500. Is this some problem with how I'm building PYWIN32 preventing some internal logic from correctly identifying the build platform? Is there some way to force PYWIN32 to target a specific windows platform? (I've tried setting CL to /DWINVER=0x502 to no avail) My actual command line, run under cygwin (yes...) is: export PATH='/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/IDE:/cygdrive/c/Program Files/Microsoft Visual Studio 8/vc/bin:/cygdrive/c/Program Files/Microsoft Visual Studio 8/vc/vcpackages:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools/bin/prerelease:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools/bin:/cygdrive/c/Program Files/Microsoft Visual Studio 8/SDK/v2.0/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/usr/bin'; /cygdrive/c/buildhome/all/xp-vc80/python-vtrunk-2.6.4/build/python setup.py install using the local built and installed python. ---------------------------------------------------------------------- Comment By: Brad Johnson (urban_dk) Date: 2010-07-20 14:43 Message: I get the "undeclared identifier" errors as well, turns out it is because the Platform SDK provided with VS2003 does not include those #defines. I think the earliest Platform SDK that defines them is the Vista SDK, which is "not recommended" for use with VS2003. It is my understanding that VS2003 is required for building the extension for Python 2.5 and earlier. ---------------------------------------------------------------------- Comment By: marvin greenberg (marvingreenberg) Date: 2009-12-03 06:07 Message: Unsupported configuration. ---------------------------------------------------------------------- Comment By: marvin greenberg (marvingreenberg) Date: 2009-12-03 06:06 Message: I sort of suspected that would be the response, but completely understand. I was hoping this might have been some simple oversight (which hope had been essentially extinguished after looking at the complexity of setup.py). Thanks. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-12-02 13:43 Message: Note that Python 2.,6 is officially built using VS2008. Re not finding the SDK, you may need to set the MSSDK environment variable to point at your SDK. ---------------------------------------------------------------------- Comment By: marvin greenberg (marvingreenberg) Date: 2009-12-02 13:16 Message: There is a typo above -- the expected winver for XP SP2 is 0x502. ---------------------------------------------------------------------- Comment By: marvin greenberg (marvingreenberg) Date: 2009-12-02 10:25 Message: Debugging setup.py a bit, find_platform_sdk_dir() is returning None. None of the registry keys or paths exists. Windows.h is only found under the Microsoft Visual Studio 8/VC/PlatformSDK/Include ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2907614&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-20 17:19:14
|
Bugs item #3028647, was opened at 2010-07-12 16:24 Message generated for change (Comment added) made by rupole You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: pythonwin keeps opening new processes (no dde on Win64) Initial Comment: Every time I run "pythonwin foo", PythonWin opens a new process and a new window. Previously it would open "foo" in any existing process, MDI style. I'm not sure what the culprit is, since I just installed PythonWin build 214. I also just started running Windows 7 64bit (I was previously on 32bit). ---------------------------------------------------------------------- >Comment By: Roger Upole (rupole) Date: 2010-07-20 12:19 Message: Good catch, apparently it just needs to be reenabled for x64 builds. The only changes I had in the project file were some irrelevant linker options. ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-07-19 18:33 Message: I got it to work! All I had to do was this: --- ..\pywin32.orig\setup.py 2010-07-19 16:22:14.034760000 -0700 +++ setup.py 2010-07-19 16:31:44.885410800 -0700 @@ -1837,7 +1837,7 @@ optional_headers=['afxres.h']), WinExt_pythonwin("dde", pch_header="stdafxdde.h", depends=["win32/src/stddde.h", "pythonwin/ddemodule.h"], - platforms=['win32'], + platforms=['win32', 'win-amd64'], optional_headers=['afxres.h']), ] # win32ui is large, so we reserve more bytes than normal ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-07-19 18:03 Message: What modifications need to be made to the project file? ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2010-07-13 04:32 Message: The dde module will build for amd64 using a modified project file, but I haven't tried to integrate the necessary changes into the setup script yet. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-07-12 19:34 Message: This is because the DDE module hjasn't been ported to the 64bit world. It may be fixed in the future (probably by re-implementing the functionality using something other than DDE), but I really wouldn't hold my breath for me to get a round tuit for this specific problem... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-19 23:33:32
|
Bugs item #3028647, was opened at 2010-07-12 21:24 Message generated for change (Comment added) made by ghazel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: pythonwin keeps opening new processes (no dde on Win64) Initial Comment: Every time I run "pythonwin foo", PythonWin opens a new process and a new window. Previously it would open "foo" in any existing process, MDI style. I'm not sure what the culprit is, since I just installed PythonWin build 214. I also just started running Windows 7 64bit (I was previously on 32bit). ---------------------------------------------------------------------- >Comment By: Greg Hazel (ghazel) Date: 2010-07-19 23:33 Message: I got it to work! All I had to do was this: --- ..\pywin32.orig\setup.py 2010-07-19 16:22:14.034760000 -0700 +++ setup.py 2010-07-19 16:31:44.885410800 -0700 @@ -1837,7 +1837,7 @@ optional_headers=['afxres.h']), WinExt_pythonwin("dde", pch_header="stdafxdde.h", depends=["win32/src/stddde.h", "pythonwin/ddemodule.h"], - platforms=['win32'], + platforms=['win32', 'win-amd64'], optional_headers=['afxres.h']), ] # win32ui is large, so we reserve more bytes than normal ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-07-19 23:03 Message: What modifications need to be made to the project file? ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2010-07-13 09:32 Message: The dde module will build for amd64 using a modified project file, but I haven't tried to integrate the necessary changes into the setup script yet. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-07-13 00:34 Message: This is because the DDE module hjasn't been ported to the 64bit world. It may be fixed in the future (probably by re-implementing the functionality using something other than DDE), but I really wouldn't hold my breath for me to get a round tuit for this specific problem... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-07-19 23:03:16
|
Bugs item #3028647, was opened at 2010-07-12 21:24 Message generated for change (Comment added) made by ghazel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) >Summary: pythonwin keeps opening new processes (no dde on Win64) Initial Comment: Every time I run "pythonwin foo", PythonWin opens a new process and a new window. Previously it would open "foo" in any existing process, MDI style. I'm not sure what the culprit is, since I just installed PythonWin build 214. I also just started running Windows 7 64bit (I was previously on 32bit). ---------------------------------------------------------------------- >Comment By: Greg Hazel (ghazel) Date: 2010-07-19 23:03 Message: What modifications need to be made to the project file? ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2010-07-13 09:32 Message: The dde module will build for amd64 using a modified project file, but I haven't tried to integrate the necessary changes into the setup script yet. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-07-13 00:34 Message: This is because the DDE module hjasn't been ported to the 64bit world. It may be fixed in the future (probably by re-implementing the functionality using something other than DDE), but I really wouldn't hold my breath for me to get a round tuit for this specific problem... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3028647&group_id=78018 |
2 messages has been excluded from this view by a project administrator.
