A humerous link sent by Harry Percival, related to this discussion:
http://cube-drone.com/comics/c/encapsulation
--
Jonathan Hartleytart...@tartley.comhttp://tartley.com
Made out of meat. +1 507-513-1101twitter/skype: tartley
___
pyt
> I agree that pip is even more appropriate than Anaconda.
Note that you can `pip install` packages from PyPI into a conda
environment, so you can install Anaconda and use it for packages that are
otherwise hard to install on windows and then use pip for everything else.
On Wed, Feb 1, 2017 at 2:
On 02/01/2017 01:05 AM, Steve - Gadget Barnes wrote:
On 01/02/2017 04:25, Jonathan Hartley wrote:
Thanks all.
Hansel - Thank you, that makes sense. I actually already do a mini
version of that at the place I'm leaving, but devs are only using
Linux/Mac host machines, and we only a Linux VM. It
On 01/02/2017 04:25, Jonathan Hartley wrote:
> Thanks all.
>
> Hansel - Thank you, that makes sense. I actually already do a mini
> version of that at the place I'm leaving, but devs are only using
> Linux/Mac host machines, and we only a Linux VM. It's reassuring to hear
> that sort of setup is
Thanks all.
Hansel - Thank you, that makes sense. I actually already do a mini
version of that at the place I'm leaving, but devs are only using
Linux/Mac host machines, and we only a Linux VM. It's reassuring to hear
that sort of setup is still feasible when extended to Windows hosts, and
Wi
It should be possible to have your Python app/s in docker containers (which
can be run anywhere via VirtualBox or natively where available) and also
run your windows Dev VMs via VirtualBox. Then this setup can be replicated
across Mac/Linux/Win. That's your Dev environment. Then in production you
h
Lots of good thoughts so far, thanks to everyone.
Anand, I deeply appreciate your contributions, but what exactly did you
mean by: "set up Linux containers but make things available on Windows" ?
On 01/31/2017 10:26 AM, Anand Kumria wrote:
I'd probably start with utilising setting up Linux V
Hi
To add to the other good avice that's been given:
You might want to look into NSSM, the Non Sucking Service Manager, to wrap
your python services into Windows services.
It makes it a doddle on Windows to wrap almost any application as a
service. We have wrapped some node services and some oth
I'd probably start with utilising setting up Linux VMs / containers but
make things available on Windows.
Keep in mind that .Net (and thus C#, F#) also run on Linux as well, and
those VMs / containers tend to be cheaper overall.
A
On 31/01/17 15:02, Jonathan Hartley wrote:
> Hey all,
>
> I'm jo
Hi Jonathan,
Congrats on the new role.
One thing I'd observe is that in my (outdated and limited) experience,
writing a windows service is much harder than writing a Linux daemon if it
has to acknowledge and interact with the desktop environment - see
https://lostechies.com/keithdahlby/2011/08/13
If people on the internet agree with you does it help you win arguments :),
if so you should definitely use linux...
One potentially interesting alternative is the UNIX implementation on
windows 10. I've no experience, but would be interested in others'
(including yours).
I would throw two additi
Hey all,
I'm joining a small company with an existing service-based
infrastructure written in C# & F#, on Windows Server on AWS.
They want me to write some new services in Python. I'm wondering whether
to host these Python services on Linux or on Windows.
In favour of Linux:
L1. I'm by fa
12 matches
Mail list logo
