|
Should also put in big bold letters at the top when the OP was last updated and keep it updated. IMO the problem with these huge threads/ops is that I click one one and see it posted in 20xx and think "hmm okay I'm just gonna assume everything is outdated."
|
# ? Mar 6, 2017 08:08 |
|
|
# ? Apr 27, 2024 08:06 |
|
I've been using Visual Studio Code a bunch for things lately, might be worth putting that in the IDEs section since it's the hotness and people might already be using it? They have a Python page and that Code Runner extension is real nice too
|
# ? Mar 6, 2017 10:34 |
|
baka kaba posted:I've been using Visual Studio Code a bunch for things lately, might be worth putting that in the IDEs section since it's the hotness and people might already be using it? They have a Python page and that Code Runner extension is real nice too It's nice and I use it for quick and dirty edits when I don't want to load PyCharm, or I'm on a computer I don't have access to PyCharm. I would probably not call it an IDE (especially for macOS). It's really more of a language aware editor.
|
# ? Mar 6, 2017 13:30 |
|
VC Code feels like a faster Atom.
Dominoes fucked around with this message at 14:16 on Mar 6, 2017 |
# ? Mar 6, 2017 14:11 |
|
Boris Galerkin posted:Should also put in big bold letters at the top when the OP was last updated and keep it updated. IMO the problem with these huge threads/ops is that I click one one and see it posted in 20xx and think "hmm okay I'm just gonna assume everything is outdated." Just look at the last edited date?
|
# ? Mar 6, 2017 14:31 |
|
Thermopyle posted:Just look at the last edited date? I know that and you know that, but it doesn't send out the message that the op is keeping the thread up to date (or, if it's a date far in the past, that they aren't doing so). Basically it adds confidence on the part of the reader who might not think to check the last edited date.
|
# ? Mar 6, 2017 14:41 |
|
is the new thread going to be backwards compatible with this thread?
|
# ? Mar 6, 2017 15:24 |
|
Hammerite posted:I know that and you know that, but it doesn't send out the message that the op is keeping the thread up to date (or, if it's a date far in the past, that they aren't doing so). Basically it adds confidence on the part of the reader who might not think to check the last edited date. Yes, I was giving the poster advice on how to solve the problem with threads that don't have what he asked for.
|
# ? Mar 6, 2017 15:29 |
|
Thread's up. Still looking for additions and edits.
|
# ? Mar 6, 2017 15:36 |
|
flosofl posted:It's nice and I use it for quick and dirty edits when I don't want to load PyCharm, or I'm on a computer I don't have access to PyCharm. Sure, I meant more as a 'stuff you can develop with' section - it has a decent amount going on though, I think for a lot of people it does what they'd want from PyCharm without being as overwhelming. Just a suggestion anyways!
|
# ? Mar 6, 2017 16:08 |
|
Dominoes posted:Thread's up. https://pymotw.com/3/ http://ironpython.net/ still technically exists!
|
# ? Mar 6, 2017 18:53 |
Dominoes posted:Thread's up. Maybe add some stuff about Python 2 vs. Python 3? Someone new to the language is bound to have questions about it, since it comes up fairly often in Python discussions, and there is still a lot of Python 2 code floating around out there (particularly in scientific circles). Even if the section is just "Python 3 is better and you should definitely use it and here is why", it's probably worth having that section IMO.
|
|
# ? Mar 6, 2017 23:14 |
|
I have some Flask code:code:
Edit - Is this the best way? code:
huhu fucked around with this message at 03:14 on Mar 7, 2017 |
# ? Mar 7, 2017 03:10 |
|
huhu posted:I have some Flask code: I'm pretty sure anything inside {{}} is just Python, so normal string concatenation applies. Use a + for ease.
|
# ? Mar 7, 2017 04:33 |
|
VikingofRock posted:Maybe add some stuff about Python 2 vs. Python 3? Someone new to the language is bound to have questions about it, since it comes up fairly often in Python discussions, and there is still a lot of Python 2 code floating around out there (particularly in scientific circles). Even if the section is just "Python 3 is better and you should definitely use it and here is why", it's probably worth having that section IMO. Dominoes fucked around with this message at 10:43 on Mar 7, 2017 |
# ? Mar 7, 2017 10:39 |
|
Just use the short blurbs y'all sent me when I asked a couple of weeks ago. Super short, no politics, etc.
|
# ? Mar 7, 2017 14:14 |
I think it's important to mention that Python has a split userbase and, since a lot of codebases remain on python 2, many popular packages are available for 2.7. We can just say "this thread assumes you're talking about python 3 in unless you specify otherwise". It seems like due diligence, and not overly political.
|
|
# ? Mar 7, 2017 19:03 |
|
OK
|
# ? Mar 7, 2017 19:05 |
Dominoes posted:I deliberately omitted that; too political.If anything, it would be a note about missing features etc when working with old codebases. Fair enough--I didn't realize this was still a political issue within the python community. I figured most serious python programmers had switched over to 3 at this point unless they were working with a legacy codebase which used python 2. Are there large numbers of people who advocate 2 over 3?
|
|
# ? Mar 7, 2017 19:14 |
|
For some reason Enthought (their product Canopy is basically like Anaconda) only supports Python2. I've asked their sales people in the past why they haven't moved to Python3 and their answer was basically "we think scientists still prefer and use 2" I don't think that it's political any longer, now it's just personal preference / legacy vs new code
|
# ? Mar 7, 2017 19:40 |
QuarkJets posted:For some reason Enthought (their product Canopy is basically like Anaconda) only supports Python2. I've asked their sales people in the past why they haven't moved to Python3 and their answer was basically "we think scientists still prefer and use 2" Okay, that's more similar to how I thought it was (I'm also in science academia). Mostly to me it seems like academics use python 2 because that's what's provided by default by Mac OS, CentOS, and Ubuntu, and that's like 99% of what your code is going to be running on.
|
|
# ? Mar 7, 2017 19:52 |
|
QuarkJets posted:For some reason Enthought (their product Canopy is basically like Anaconda) only supports Python2. Edited to reflect that!
|
# ? Mar 7, 2017 20:17 |
|
.
|
# ? Mar 7, 2017 20:47 |
|
The internet is very vocal about python 3 but there is a lot of python 2 development still going on. PyPI download statistics from ~1 year ago (apparently you can't get them anymore) puts python 2.7 somewhere in the ballpark of 10x more popular than all versions of python 3 combined. Pycharm's developer survey from last year is a bit better, but still comes out 60/40 in favor of 2.
|
# ? Mar 7, 2017 20:58 |
|
The point about Python2 coming packaged with many linux distros is also a good one. It's a little surprising, but there you have it. Someone starts off learning with their system python and eventually when they start looking at package managers like Anaconda the question of "do I use Python2 or Python3" has already been answered for them
|
# ? Mar 7, 2017 23:41 |
|
VikingofRock posted:Okay, that's more similar to how I thought it was (I'm also in science academia). Mostly to me it seems like academics use python 2 because that's what's provided by default by Mac OS, CentOS, and Ubuntu, and that's like 99% of what your code is going to be running on. That's my experience as well in academia. Outside of a very narrow group of people and/or field I honestly don't think that academics even know there's a python 2 and python 3, all they know is there is a "python" with numpy and sympy etc and that's that. At the end of the day there's basically only two things that matter: 1) does my code work, and 2) does it run on my laptop and/or hpc cluster. Most people aren't going to care about writing reusable library code to do the things they need to do. They're perfectly fine with one giant script.py file where they manually go in and comment/uncomment out lines of code to run different scripts and such. Either that or old school style script_do_x.py and script_do_x_with_different_y.py, where they are just copies of each other save for some inputs. That's non-CS academia for you.
|
# ? Mar 8, 2017 08:25 |
|
Love it that we now have 2 python threads. Feels just like real life!
|
# ? Mar 8, 2017 09:12 |
9-Volt Assault posted:Love it that we now have 2 python threads. Feels just like real life! Don't worry, I'm sure this thread will get end-of-lifed in
|
|
# ? Mar 8, 2017 09:31 |
|
|
# ? Apr 27, 2024 08:06 |
|
9-Volt Assault posted:Love it that we now have 2 python threads. Feels just like real life! There's a joke about the GIL in there somewhere.
|
# ? Apr 22, 2017 14:31 |