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

Landscape and python 3 #137

Closed
renefritze opened this issue Jul 8, 2015 · 6 comments
Closed

Landscape and python 3 #137

renefritze opened this issue Jul 8, 2015 · 6 comments
Milestone

Comments

@renefritze
Copy link
Member

Landscape.io does not support python 3 at this time, so there will be (are already in #134) misreported issues due to that. So the question is whether to disable it or just keep that in mind. I vote against disabling it.

@sdrave
Copy link
Member

sdrave commented Jul 8, 2015

Hmm, not sure. Do they have plans to support Python 3 in the not so distant future?

@renefritze
Copy link
Member Author

FAQ say it's the most requested feature and in progress... so maybe.

@sdrave
Copy link
Member

sdrave commented Jul 14, 2015

IMHO, a tool which tells me for every I have made things worse is not very helpful. I would vote for disabling Landscape after the Python 3 transition until they have Python 3 support.

@sdrave sdrave added this to the 0.4 milestone Jul 14, 2015
@ftalbrecht
Copy link
Contributor

Agreed!

@renefritze
Copy link
Member Author

Tracked down the relevant landscape issue. I very much doubt we'll see it supporting 3 soon.

@renefritze
Copy link
Member Author

I've also disabled watching this repo on the landscape.io site and revoked theri access token.

renefritze added a commit that referenced this issue Oct 22, 2015
sdrave pushed a commit that referenced this issue May 4, 2016
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

3 participants