6 ms·
IMO that's the wrong approach. The correct one would be: "Hey, you know all the software you want to pay me to write? It will be in Python 3 now".
by oblio 10y ago
IMO that's the wrong approach. The correct one would be: "Hey, you know all the software you want to pay me to write? It will be in Python 3 now".
- geocar 10y agoI'm not going to work for free.
- scrollaway 10y agoYou are not reading what the person you are replying to is saying.
- geocar 10y agoI said I cannot invoice the customer "convert perfectly good codebase to python3", and I said I'm not working for free. The only other option I can see you might be suggesting is to defraud my customer by converting that codebase to python3 but say I was doing something else. I don't want the reputation of being one of those people.
- SpaceManiac 10y agoI believe the path being suggested is: write new software in Python 3, or at least in a 3-friendly way.
- geocar 10y agoThat's easy to say, but Python3 isn't good enough: * Python3 is slower than Python2 * Twisted still doesn't work in Python3 * Division changed. And so on. I'm not improving Python3 since I don't get any return on it, so I'll simply use a different language for new projects. However you might want to reconsider: Other people parsed it the same way -- and one person even thought it was a good thing that they got to charge again.
- minitech 10y agoIf you write new software in Python 3, why does it matter if division changed?
- geocar 10y agoFirst, it presupposes I'm going to write new software in Python 3 rather than justifying why I should write new software in python 3. Second, it matters because I'm thinking about python4 and python5. I've already been through this and got burned moving from python1.5 to python2, and python3 has been very uncomfortable thus far. Thirdly, it matters because I work in a lot of mature (multi-decade) codebases, and figuring out what division is supposed to mean twenty five years into development is disconcerting. Then when I'm simply not convinced python is a good investment anymore, this quippy attitude here is extremely off-putting. Do you really want to know why I don't like python as much as I used to? Or are you trying to justify your decision to further invest?
- minitech 10y ago> First, it presupposes I'm going to write new software in Python 3 rather than justifying why I should write new software in python 3. It does, because that’s what you were responding to: > I believe the path being suggested is: write new software in Python 3, or at least in a 3-friendly way. I assumed your list was a list of reasons not to write new software in Python 3, and found division oddly out of place.
- geocar 10y ago> It does, because that’s what you were responding to: I believe the path being suggested is: write new software in Python 3, or at least in a 3-friendly way. You're mistaken. Start at the top of the thread again[1]. The question is whether I (or anyone else) should even bother with Python3. [1]: https://news.ycombinator.com/item?id=13061570 https://news.ycombinator.com/item?id=13061570
- scrollaway 10y ago
- HelloNurse 10y agoThe other, complementary correct approach is "Hey, you know all the software we paid you to write? We'll pay you to port it to Python 3 because we don't like running two different interpreters". And with tools and decent Unicode handling etc. in the original version, the update will be done inexpensively and on time.
- guitarbill 10y agoI consider Python 3 a huge benefit for a similar reason: I can avoid or charge $$$ for people still using 2.6 (e.g. on ancient RHEL). There's always somebody. 2.6 is pretty sucky, not to mention unsupported by the PSF. If you support 2.7, some "clever" manager or client will say that 2.6 support surely isn't so unreasonable. It is. 2.7 is legacy only now IMO.
- lima 10y agoI'm happily using and deploying Python 3.6 on CentOS 6 using pyenv. You don't have to use the system Python unless there's a policy requiring you to do so.
- guitarbill 10y agoI agree, and EPEL works fine on RHEL, too. But it wouldn't be enterprise without some BS rules. Hence why compatibility "issues" are such a blessing for detecting enterprise BS early on.
- lima 10y agoYou can get a more recent Python from Software Collections, too: https://www.softwarecollections.org/en/scls/?search=python https://www.softwarecollections.org/en/scls/?search=python Up to Python 3.5 and 3.6 will probably follow shortly after release. This is blessed and QA'd by Red Hat themselves, so it's as good as it gets. "My distro only has Python 2" has to be one of the worst excuses not to use Python 3 :-) Obvious exception are systems tools (did you know that Ansible modules have to compatible with Python 2.4 since that's what CentOS 5 uses?). But those are the absolute minority.