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

Support Python 3 #142

Closed
item4 opened this issue Feb 3, 2016 · 4 comments
Closed

Support Python 3 #142

item4 opened this issue Feb 3, 2016 · 4 comments

Comments

@item4
Copy link
Contributor

item4 commented Feb 3, 2016

@mitsuhiko want someone's PR

Issue

  • Can we use six for keep same operation?
  • Can we use tox for testing?
  • Can we use coveralls for checking coverage?
  • Can lektor's dependencies support py3?
@item4
Copy link
Contributor Author

item4 commented Feb 3, 2016

@mitsuhiko May I know inifile support py3? It's your library. but have any docs.

@mitsuhiko
Copy link
Member

inifile supports Python 3.

Instead of using six please write a custom _compat module like in other libraries. Six pulls in a shitty hack on import hooks and that causes major pain on distribution.

@techdragon
Copy link

@mitsuhiko I assume the futures/futurize path is also a no go for supporting Python 3?.

@mitsuhiko
Copy link
Member

@techdragon i'm fine with anything for as long as the code stays as clean as possible and nothing in python 2 degrades and does not pull in dependencies for achieving this feat.

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

Successfully merging a pull request may close this issue.

3 participants