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

Comments

Projects
None yet
3 participants
@item4
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

This comment has been minimized.

Contributor

item4 commented Feb 3, 2016

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

@mitsuhiko

This comment has been minimized.

Member

mitsuhiko commented Feb 4, 2016

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

This comment has been minimized.

techdragon commented Feb 29, 2016

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

@mitsuhiko

This comment has been minimized.

Member

mitsuhiko commented Feb 29, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment