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

Add highlights section #13

Open
jnoller opened this issue Dec 13, 2011 · 2 comments
Open

Add highlights section #13

jnoller opened this issue Dec 13, 2011 · 2 comments

Comments

@jnoller
Copy link
Contributor

@jnoller jnoller commented Dec 13, 2011

Having a section that shows the improvements python 3 has made - such as stdlib cleanups and adding things like the futures library would be nice. I cover some of this in the downloads section, but I don't think it's as attractive as it could be. We need to highlight the great things that are happening and that have been done.

Users are constantly complaining that there aren't enough "cool things" - when that's actually not true

@kracekumar
Copy link

@kracekumar kracekumar commented Dec 14, 2011

Adding to the point, we can add time taken to run same code in python2.x and python 3.x, later we can add pypy benchmark(Futuristic- getpython2.com focuses on python3, we can omit if this is out of topic).

@jnoller
Copy link
Contributor Author

@jnoller jnoller commented Dec 14, 2011

I think that's pretty far out of the scope for the goals of the site. Benchmarks will be done on http://speed.python.org/

On Wednesday, December 14, 2011 at 10:40 AM, kracekumar wrote:

Adding to the point, we can add time taken to run same code in python2.x and python 3.x, later we can add pypy benchmark(Futuristic- getpython2.com (http://getpython2.com) focuses on python3, we can omit if this is out of topic).


Reply to this email directly or view it on GitHub:
#13 (comment)

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

Successfully merging a pull request may close this issue.

None yet
2 participants