Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pexpect2.3 or pexpect4.8 + python2.7 unicode error #659

Open
sahandesilva opened this issue Sep 12, 2020 · 4 comments
Open

pexpect2.3 or pexpect4.8 + python2.7 unicode error #659

sahandesilva opened this issue Sep 12, 2020 · 4 comments

Comments

@sahandesilva
Copy link

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 ?

@EnigmaticCypher
Copy link

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).

@bsolomon1124
Copy link

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.

@Red-M
Copy link
Member

Red-M commented Nov 27, 2023

PRs are welcome to resolve issues.

@Jamim
Copy link

Jamim commented Dec 17, 2023

PRs are welcome to resolve issues.

I've recently submitted a PR that brings back basic Python 2.7 support:

But I don't think it resolves this particular issue, so some additional work might be needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants