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

Let's drop support for Python 2.6 #295

Closed
whart222 opened this issue Dec 28, 2017 · 5 comments
Closed

Let's drop support for Python 2.6 #295

whart222 opened this issue Dec 28, 2017 · 5 comments

Comments

@whart222
Copy link
Member

I don't see any meaningful reason to continue support for Python2.6, but let's start a conversation here about this possible change.

I've seen evidence that we're spending time supporting this version of Python without deriving any meaningful utility.

@hugovk
Copy link

hugovk commented Jan 4, 2018

Here's the pip installs for pyomo from PyPI for the last month (via pypinfo --percent --pip --markdown pyomo pyversion) -- no Python 2.6.

python_version percent download_count
2.7 54.4% 1,141
3.5 20.6% 433
3.6 20.1% 421
3.4 4.7% 99
3.7 0.1% 3

@whart222
Copy link
Member Author

whart222 commented Jan 4, 2018

@hugovk Nice! I didn't realize that would could get that info from that data store.

@hugovk
Copy link

hugovk commented Jan 4, 2018

Yeah, you can get all sorts of things out of it, see https://github.com/ofek/pypinfo for some other interesting examples.

@whart222 whart222 added this to To Do in Pyomo 5.6 Release Jan 24, 2018
@ghackebeil
Copy link
Member

I'm trying to think of things that we can start doing in code once we officially drop support for 2.6 (hoping others will add to the list). A few things that come to mind:

  1. Alternative (and much faster) dict initialization syntax: {key:1.5 for key in range(10)}
  2. Instead of nesting with blocks one can simply separate with arguments with a comma, which allows reducing the number of indentation levels needed (e.g., with A() as a, B() as b:)

@whart222 whart222 removed this from Nominations in Pyomo 5.6 Release Jan 25, 2018
@whart222 whart222 added this to Nominated in Pyomo 5.4 Release via automation Jan 25, 2018
@whart222 whart222 moved this from Nominated to Accepted in Pyomo 5.4 Release Jan 25, 2018
@whart222 whart222 moved this from Accepted to In progress in Pyomo 5.4 Release Jan 25, 2018
@hugovk
Copy link

hugovk commented Jan 25, 2018

Reasons for dropping Python 2.6

General

Code

@whart222 whart222 removed this from In progress in Pyomo 5.4 Release Jan 29, 2018
@whart222 whart222 added this to Nominations in Pyomo 5.6 Release via automation Jan 29, 2018
@whart222 whart222 moved this from Nominations to In Progress in Pyomo 5.6 Release Apr 15, 2018
@whart222 whart222 moved this from In Progress to Pending Review in Pyomo 5.6 Release Apr 15, 2018
Pyomo 5.6 Release automation moved this from Pending Review to Done Apr 26, 2018
Pyomo Design Discussions automation moved this from To Do to Done Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

4 participants