Jan Lachnitt added the comment:
A related issue exists with cwd: #15533.
--
nosy: +pepalogik
___
Python tracker
<https://bugs.python.org/issue8557>
___
___
Pytho
Jan Lachnitt added the comment:
Nobody responds yet, so I will.
I think that the basic proposal was made by Chris Jerdonek in msg171692 already
on 2012-10-01: First document both behaviors and then discuss the possible
harmonization. I think the proposal was good and further discussion has
Jan Lachnitt added the comment:
@eryksun: Sorry for my late reply, apparently I did not have time to reply in
2017. I see your point, but still I think that Python is conceptually
multi-platform, so its behavior on Linux and Windows should be as much
consistent as possible.
I am not the
Jan Lachnitt added the comment:
Thank Wolfgang Maier for reminding this issue and providing various details and
observations. Having taken a look at my old comments (and at others' comments,
too), I feel that the cwd issue deserves a clearer description.
Let's use the followin
Jan Lachnitt added the comment:
...
print(ctypes.sizeof(ctypes.c_wchar))
_PyObject_Dump=ctypes.pythonapi._PyObject_Dump
_PyObject_Dump.argtypes=(ctypes.py_object,)
print(_PyObject_Dump(dirname))
print(list(dirname))
in Python 3.3.0 64-bit on Windows 8 produces:
2
object : 'D:\\Bug re
Jan Lachnitt added the comment:
On Windows XP 32-bit: 3.2.3 works, 3.3.0 fails.
--
___
Python tracker
<http://bugs.python.org/issue17137>
___
___
Python-bug
Jan Lachnitt added the comment:
Knowing that the problem is related to the internal representation of the
strings, I have written a short script which reproduces the problem. It is this
simple:
import os
name = 'sub-fcc'
wrkdir = 'D:\\Bug reports\\Python\\test'
dirname
Jan Lachnitt added the comment:
print(ascii(struct.name))
print(ascii(struct.name.encode("unicode_internal")))
print(ascii(struct.name.encode("utf-8")))
produces:
'sub-fcc'
b's\x00u\x00b\x00-\x00f\x00c\x00c\x00'
b'sub-fcc'
and
Jan Lachnitt added the comment:
Here is a part of my code (with some comments added):
for struct in ini_structures:
dirname = wrkdir+os.sep+struct.name
if not os.path.isdir(dirname): # This works fine. If the directory
doesn't exist,...
New submission from Jan Lachnitt:
Python 3.3 64-bit seems to compile one of my files incorrectly. Specifically,
os.path.isdir returns True for a nonexistent folder. The important point is
that the code works correctly when it is performed step-by-step in pdb.
Python version:
Python 3.3.0
Jan Lachnitt added the comment:
Hi all,
I have solved the problem by using absolute path of the executable. The reason
why the executable didn't work properly may be that the executable's relative
path was inconsistent with current directory. See the following example (I hav
Jan Lachnitt added the comment:
Hi Chris, thank for your reply, I didn't see it while writing the edit. Does it
mean that on Linux, it will use the cwd?
--
___
Python tracker
<http://bugs.python.org/is
Jan Lachnitt added the comment:
EDIT:
No, it doesn't work fine: the executable reports stack overflow. I thought this
had nothing to do with Python, hence I didn't mention it. But If I run the
executable without Python, THEN it works fine. But this may be another issue.
I'll
Jan Lachnitt added the comment:
Hi,
I am using Python 3.2.3 on Windows XP. I encountered a problem with
subprocess.call when using the cwd parameter. I used Google to look for a
solution and I found this issue in Python tracker. But this issue seems
absolutely reversed!
The subprocess
14 matches
Mail list logo
