New submission from Rich:
Launching IDLE from the start menu has no effect, no windows open.
Command line Python still works. Reinstalling Python does not fix the
problem.
I haven't changed my system configuration since everything was working.
Any ideas for things to check to fix this
Rich added the comment:
I'm on 32-bit Windows Vista, and I installed with the Python 2.5 msi.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1743>
__
___
Rich added the comment:
I've been away for a couple of days, but can replicate everything
Joakim has reported in my abscence. Deleting/renaming recent-files.lst
allows me to launch IDLE (from cmd or Start Menu).
Oddly though, if I close IDLE, copy/paste the contents of the old
recent-
Rich added the comment:
I can't get it to do it again. Unless someone else is still
experiencing the problem, perhaps it was fixed (deliberately or
otherwise) by this month's Vista hotfixes that came down automatically
a couple of days ago.
Thanks for your hel
Rich added the comment:
If you are using Vista, then we discovered that there might be a
problem associated with the recent-files.lst file (usually found
in .idle in the C:\Users\Yourname directory). That's all written down
in Issue 1743.
If that doesn't apply to you then if you sp
Rich added the comment:
Aha! There is no difference in Permissions, but the working recent-
files file isn't "hidden" but the one generated originally by IDLE was.
If I make the one I made "hidden" then IDLE stops working again.
The .idlerc folder has been hidden all al
New submission from Rich:
Issue 1743 might be related to this.
Using "Save As..." in IDLE does work, but if breakpoints.lst is hidden
(which it is when Python generates it) it also generates this error in
the Shell:
Exception in Tkinter callback
Traceback (most recent call last):
New submission from Rich :
This problem is an _extremely_ common one, a problem that almost any Python
project of a reasonable size will encounter.
Given a number of bytes, say 123901842, format this as '123.9MB'.
The reason I strongly think that this should be included in th
Rich added the comment:
Yep, as I mentioned, it should be configurable to use either format.
Localization is an excellent point as well, so, all in all, the optional
arguments to the function are format, significant digits, and delimiter. That's
not an unreasonable amount of configurab
Rich added the comment:
I think bitmath would be overkill to include in its entirety, but maybe there
solution is a good one.
There is also:
https://pypi.python.org/pypi/byteformat/
https://pypi.python.org/pypi/datasize
https://pypi.python.org/pypi/hurry.filesize
https://pypi.python.org/pypi
New submission from Rich Marinaccio:
I have been using python for Civilization IV map scripting, and I
believe I have found a small problem with the randint function. Once in
a blue moon, randint(a,b) returns b + 1, rather than a >= N <= b. I
have seen this behavior a few times. Here
Rich Marinaccio added the comment:
I have been using python for Civilization IV map scripting, and I
believe I have found a small problem with the randint function. Once in
a blue moon, randint(a,b) returns b + 1, rather than a <= N <= b. I
have seen this behavior a few times. Here
Rich Marinaccio added the comment:
I've done some more testing and I can't get this to repeat with randint
alone. It must be an issue with combination of the len() function used
as a parameter to randint. The above code is in a loop that further
down will del preshuffle[randIndex].
Rich Marinaccio added the comment:
To be clear, I am not using multi-threading in my particular module. I
can't explain this behavior with my code alone. The issue is
complicated by the fact that my module is called by Civ IV, and I have
no idea what the game is doing behind the scen
Rich Marinaccio added the comment:
What was happening before was I was getting an index out of range error
every so often, so then I put in the ValueError catch to see what was
going on. I was surprised to see that randIndex was the same as len
(preshuffle). I have some further catches in
Change by Rich rauenzahn :
--
nosy: +rrauenza
___
Python tracker
<https://bugs.python.org/issue43833>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Michael Rich :
Hi, a web server can be incorrectly bound to an already in-use socket when
binding a HTTPServer on windows. The issue is discussed here:
https://stackoverflow.com/questions/51090637/running-a-python-web-server-twice-on-the-same-port-on-windows-no-port
New submission from Rich Rauenzahn :
Using 64bit python for windows downloaded from python.org on 64bit windows 7.
Python Version 3.2.2
Tk version 8.5
IDLE version 3.2.2
When stepping through code the corresponding line in the editor does not
highlight with the code steps. The windows does
Rich Rauenzahn added the comment:
Yes, the source box was checkmarked.
Not the first one to encounter this as well:
http://python.6.n6.nabble.com/IDLE-not-highlighting-current-line-while-debugging-on-Win-td2113345.html
--
___
Python tracker
<h
New submission from Rich Jones :
If I try to create a symlink which already exists, I get a FileExistsError. In
this error message, the explanatory arrow is pointing in the wrong direction.
This gave us a big scare in our logs!
Example:
```
$ ls
HELLO.txt
$ python3
Python 3.7.0 (default
Rich Jones added the comment:
@Larry - that would be an acceptable solution!
I'm here because I encountered this error independently. I explain why the
arrow is a problem here: https://bugs.python.org/issue35367
The issue is that the '->' notation is already used by the
New submission from Rich Healey :
64 bit pythons fail on 64 bit Windows 7.
The crash happens with python 2.6 and 3.1 in 64 bit mode. 3.1 was a
clean install after the issue presented itself.
I'm not 100% sure how best to help with the problem, I've attached the
dump from window
Rich Healey added the comment:
I'm not 100% sure.
I have a x64 machine running Windows 2008. I will check if it's in the
log now.
I will also check if it's in the debug trace for x86 python (which works).
RESULTS:
I get the LuaPriv initialised line on x86 python on my win7
Rich Healey added the comment:
I think that dump may be incorrect because it does not have all the
symbols. I will checkout source for latest 3.x trunk and attempt to
build 64 bit binaries.
--
___
Python tracker
<http://bugs.python.org/issue7
Rich Healey added the comment:
No action- the interpreter fails to start.
Or do you mean what changed to make it break? I'm not sure. It used to
work but I don't believe I changed anything on my system.
--
___
Python trac
Rich Healey added the comment:
By running the python.exe (either by double clicking it, typing it's
path into a cmd shell or by opening it in a debugger).
I tried to create a 64 bit build of the source tree which DID start, but
the hoops I had to jump through to build it with VC++ Ex
Rich Healey added the comment:
Nope- 2.6.4 fails in the same way.
--
___
Python tracker
<http://bugs.python.org/issue7206>
___
___
Python-bugs-list mailin
Rich Healey added the comment:
They did at first for me, and then something changed.
They now don't start. I don't have the skills to properly diagnose why,
all I can get out of my debuggers is that something is happening in
ntdll.dll
Not necessarily pointing fault at Python per
Rich Healey added the comment:
Carey I can send you the steps I used to create the dump if you like so we
can check if it's the same issue?
--
___
Python tracker
<http://bugs.python.org/i
Rich Healey added the comment:
Download the debugging suite from
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx#
Open windbg
Press Ctrl + E to load an executable
Select your python binary
Step through by typing g in the text box at the bottom of the Command
window.
The
Rich Healey added the comment:
I've done some more fiddling with the debugger, once I discovered the
Windows symbol servers, and a tool called application verifier some
things started to fall into place.
LuaPriv takes care of user privelidges, the program runs fine when I run
Rich Healey added the comment:
I have an apology to make for wasting your time.
Further investigation demonstrates that it was evidently fiddling with
the Application Verifier that broke everything (although I installed it
during my debugging attempts- I'm guessing that something else
Rich Healey added the comment:
I looked into it a bit further.
With some trial and error I narrowed the source of the problem to be the
'KernelModeDriverInstall' option under compatibility. I believe this
isn't a problem, because python shouldn't be trying to install driv
New submission from Rich Rauenzahn:
This came up on StackOverflow: http://stackoverflow.com/a/37903779/2077386
I wanted to bring it to your attention in case it hasn't been notice before.
It turns out that if you pass a fileobject (i.e.,
ConfigParser().read(open("foo"))) Co
Rich Rauenzahn added the comment:
Given that write() accepts a fileobject, but read() accepts a list of strings
or a string (and readfp() is the one that accepts a fileobject instead), this
seems like it could be a common enough error that just iterating over the
fileobject could be
Rich Rauenzahn added the comment:
Thank you, lukasz. That's the answer I anticipated -- I can appreciate the
backwards compatibility aspect very much.
Regarding the docs, the docs say:
"Attempt to read and parse a list of filenames, returning a list of filenames
which were su
36 matches
Mail list logo
