You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use sftp through pexpect2.3 on python2.7. I can spawn a sftp connections successfully and do any sftp operation for files having filenames in the ascii range but as soon as it operates on filenames having Unicode characters operations fail. I see the same behaviour with pepxect4.8+python2.7.
for instance when pexpect4.8 is used, when I issue the command
ls -l test2™.txt
pexpect returns(I print logs to stdout using child.logfile = sys.stdout),
ls -l test2.txt No such file <----- see '™' is missing
I'm wandering what causes this issue ?
The text was updated successfully, but these errors were encountered:
Given that Python 2.7 has been in End of Life status for almost a year now, I doubt you're going to get much help here. It is highly likely that this package will focus on supporting current versions of Python. (Though maintainers, if you do still wish to support 2.7, it may be a good idea to explicitly state the current support status somewhere).
Then maintainers should remove [bdist_wheel] universal=1 from setup.cfg and 'Programming Language :: Python :: 2.7' from setup.py. The 4.x releases in no way support Python2, it appears.
I use sftp through pexpect2.3 on python2.7. I can spawn a sftp connections successfully and do any sftp operation for files having filenames in the ascii range but as soon as it operates on filenames having Unicode characters operations fail. I see the same behaviour with pepxect4.8+python2.7.
for instance when pexpect4.8 is used, when I issue the command
ls -l test2™.txt
pexpect returns(I print logs to stdout using child.logfile = sys.stdout),
ls -l test2.txt No such file <----- see '™' is missing
I'm wandering what causes this issue ?
The text was updated successfully, but these errors were encountered: