Skip to content

Support pyxl #829

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

Closed
JukkaL opened this issue Aug 19, 2015 · 5 comments
Closed

Support pyxl #829

JukkaL opened this issue Aug 19, 2015 · 5 comments
Labels

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Aug 19, 2015

Pyxl uses a custom source file encoding. Somehow get it to work.

@o11c
Copy link
Contributor

o11c commented Aug 24, 2015

If the encoding is installed, shouldn't it Just Work™ since the parser operates directly on decoded unicode objects?

Or are there python2-specific issues with how parsing works? I admit I'm operating from a python3 perspective.

The "mess with builtins" is the nastier part IMO.

@o11c
Copy link
Contributor

o11c commented Aug 24, 2015

Or wait, is the issue "how to use both coding: mypy and coding: pyxl" ? In that case, I think it's possible to modify the lookup to do multi-stage encoding with coding:mypy-pyxl ...

@JukkaL JukkaL removed the hack label Jun 7, 2016
@JelleZijlstra
Copy link
Member

I'm guessing this is no longer an issue, but somebody at Dropbox should confirm.

@gvanrossum
Copy link
Member

Oh man, we're really not very good at closing issues when they're fixed. This was fixed by https://github.com/gvanrossum/pyxl3 over two years ago.

@emmatyping
Copy link
Member

@gvanrossum perhaps we should adopt @msullivan's proposal in #4849? That would certainly help :)

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

No branches or pull requests

5 participants