News for hackers. Stuff that matters.
Re:Python 3 in 2016 by retrogradeorbit on Thursday February 18, 2016 @06:37AM (#11125083)
Re:Python 3 in 2016 by new_hackers on Thursday February 18, 2016 @02:36PM (#11128625)
this +1000

The python users I've encountered fall generally into two camps:

1) The engineer/scientist/researcher/hacker type that has python installed on their snowflake machine, and has a whole bunch of packages installed to make their flavor of snowcones. These users just want python to work, find joy in the syntax, and in general get their work done.

2) the developer that is trying to deploy the same thing to many machines. This is a pain. Often you end up with users from camp 1 trying to do this and you end up with a global python install with batteries and the kitchen sink included that is a dependency for a whole bunch of "server" apps. you update a package (because "my special snowcone needs it") and you break something else that you didn't know to test. This is a nightmare. With pip and venv it is easier to manage this, but I still see that relocatable venv is "experimental" when you read the help. IMHO, the python 3 community needs to make it very, very easy to distribute and deploy my special snowcone maker and all its dependencies to a system without python already installed, and not stomp on anybody elses snowcone maker in the process.

Re:Python 3 in 2016 by monkmartinez on Thursday February 18, 2016 @08:17AM (#11125481)
This should be the #1 comment/resource on this thread IMO.
Re:Python 3 in 2016 by zanny on Thursday February 18, 2016 @10:31AM (#11126430)
I recently started writing a few Qt applications, and was strongly considering PyQt - I mean, why wouldn't I? The syntax is cleaner and I can get more work done faster using Python than C++.

I spent a few days going back and forth - comparing the performance, design time, etc of both - and in the end I'm just using Qt's JS JIT for dynamic list comprehensions and other things C++ is bad at. In the end, the fact that distributing on everything but Linux would have been reduced to having to bundle CPython in was just a deal breaker.

Linux isn't really bad for deployment, though. You can use the SUSE OBS to build packages for all the major platforms besides Arch, and since my main desktop is Arch, I'm building my software with PKGBUILD's from the get-go.

Re:Python 3 in 2016 by witty_username on Thursday February 18, 2016 @10:43AM (#11126519)
Python isn't very big (about 10-20 MB or so). What's the problem with bundling CPython?
Re:Python 3 in 2016 by kweks on Thursday February 18, 2016 @10:45AM (#11126541)
I've written a production app in Python 3 + QT4 (PySide as opposed to PyQT) - I've bundled with cxfreed, and it's great.

Fully cross-platform.. easy to distribute. Quite nice all around.

Re:Python 3 in 2016 by mixmastamyk on Thursday February 18, 2016 @01:38PM (#11128092)
That page dismisses py2exe, but I've used it successfully for over a decade. On unix it is as simple as:

  sudo pip install [package/repo]
Re:Python 3 in 2016 by elktea on Thursday February 18, 2016 @05:52PM (#11130012)
Except, you often need a full compiler toolchain for all the c dependencies. Then you need to make sure you have the required header files. Then you try and deploy to a small EC2 instance and run out of RAM building lxml or similar.
Re:Python 3 in 2016 by mixmastamyk on Thursday February 18, 2016 @07:31PM (#11130584)
If your requirements are advanced, make packages on your dev box then deploy those:

https://nylas.com/blog/packaging-deploying-python

Re:Python 3 in 2016 by elktea on Thursday February 18, 2016 @11:13PM (#11131486)
It's an interesting idea, thanks.