I've never used robocopy -- never heard about it until your post --
but it sounded funny to me that it should need to use drive letter
mappings. Microsoft has been moving away from them since MS DOS days.
Sure enough, this shiny new command line utility can be used with
server share names as well
Hi!
Could you also please try wscript.exe win32com\test\testInterp.vbs
This is OK. BUT, if I add this line:
import win32ui
in the script
C:\Python26\Lib\site-packages\win32com\servers\interp.py
the test give the (allways same) error.
I tried on :
Python 2.6.5 with Windows 7
Hi,
I want to know the target path of a windows shortcut. How do i read the
short cut retrieve the actual target path it is pointing to? I
searched the internet all the documents I found there refer to use
Win32com.shell or win32com.client module but was not satisfied with the
solutions
On 04/03/2011 12:27, Ayaskanta Swain wrote:
Thank you for sending me the link. I tried it by copying the
“shortcut_target(filename)” function into my script. But it does the
same thing as I had mentioned in my previous e-mail. i.e It returns me
the target path correctly if the target exists
I probably forgot to include my sig, which means listen all of us like
a hive queen instead of like a bullish king.
--
According to theoretical physics, the division of spatial intervals as
the universe evolves gives rise to the fact that in another timeline,
your interdimensional counterpart
Well, Here is how I have implemented in my script. Please take a look
let me know whether I am doing something wrong. Mine is a
Windows-XP(SP3), 32-bit system.
# Reads the windows shortcut returns the target path
def shortcut_target (shortcutfile):
link = pythoncom.CoCreateInstance (
Hi,
As I don't see any CLI tool other then hex editor, I thought on writing
small script that will display byte distribution from file content
So I thought on this:
-
counter = {}
for bytes in open('c:\\temp\\bin.dat', rb).read():
counter[bytes] =
Greg Ewing wrote:
I recently tried running PyGUI on Python 3 using
pywin32 build 216, and a couple of things are
not working quite the same way as they were with
Python 2 and build 213.
1) The default font used for control labels etc.
is slightly smaller.
2) When I calculate the width of
What a nifty script! I love it!
Here's my version. I tested using a 800 KByte image file and it runs
in a blink. Dictionary access in Python is very fast.
code
counter = {}
for bytes in open('c:\\temp\\16.jpg', rb).read():
try:
counter[bytes] += 1
except KeyError:
Thanks guys for your input
As I need this for larger files (couple of tens even hundrets of MB) I
tested your suggestion and it seems that dict method is fastest.
I ended with this:
import sys
try:
counter = {}
for bytes in open(sys.argv[1], rb).read():
Ghostly wrote:
Thanks guys for your input
As I need this for larger files (couple of tens even hundrets of MB) I
tested your suggestion and it seems that dict method is fastest.
I decided to find out, so I ran timeit on both schemes using a 2MB
file. The two methods are within 1% of each
Tim Roberts wrote:
Are you running this on a different computer?
No, it's the same computer. I can run 2.x and 3.x versions
of the same test side by side, and the 2.x one has normal
sized text whereas the 3.x one has tiny text.
Oddly, it only seems to affect text drawn by the standard
win32
12 matches
Mail list logo
