On Mon, Feb 20, 2017 at 1:46 PM, Amber Brown
wrote:
> As such, I would like to remove support for these Python versions. Using
> recent statistics (https://langui.sh/2016/12/09/data-driven-decisions/)
> we can infer that Python 3.3 is on the whole uncommon, despite it being the
> default Python 3
On 22/02/17 20:59, Cory Benfield wrote:
The permitted C dependencies *for dynamic linking* are tiny, sure.
But those libraries may statically link as they please. The likely
scenario for most such packages is that they statically link whatever
they need. This is the approach taken by some that I
Debian 9 (Stretch) is in final freeze and will become the new stable
release very soon (a month or so?). By the time we drop 3.4 support,
Stretch will be current stable, so my recommendation would be to upgrade to
Stretch when it comes available, and use the Python 3.5 it ships with.
Alternatively,
> On 22 Feb 2017, at 18:16, Phil Mayers wrote:
>
> #2 seems useful now that I know about it but - correct me if I'm wrong - the
> manylinux1 permitted C dependencies are super-tiny, and would not permit e.g.
> cryptography or psycopg2?
Depends.
The permitted C dependencies *for dynamic linki
On 22/02/17 17:42, Hynek Schlawack wrote:
I have to disagree here: I don’t want build tools of any kind in my
final containers therefore I build my artifacts separately no matter
what language. Of course you can just build the venv on your build
Agreed, 100%. Apologies if I gave you the impr
On 22/02/17 17:35, Steve Waterbury wrote:
On 02/22/2017 12:23 PM, Phil Mayers wrote:
On 22/02/17 15:00, Steve Waterbury wrote:
Have you considered the 'conda' package manager?
I've never come across it. It looks too big for me to give a quick
opinion on, but I'll bear it in mind. Thanks for
On Tue, Feb 21, 2017 at 2:27 AM, Hynek Schlawack wrote:
>
> 3.3 should die immediately. 3.4 should follow ASAP.only the latest two
> or so are worth supporting.
>
Debian Jessie (which also means Raspbian Jessie, which is my primary
concern) uses Python 3.4, so I would hope that Python 3.4 suppo
>> I don’t see how that’s tedious since a compute does that for me.
>> Although I don’t see any value at wheeling them (and some packages
>> cannot be wheeled); my CI builds a venv and puts it into a container.
>> There’s nothing tedious about it at all.
> I find the idea of running throwaway envir
>>> So my problem is that while my protocol stack spins up very nicely and
>>> trivially easy using the twistd daemon, the standard python3-twisted
>>> package for 14.04 is wy behind and doesn't include twistd (!), and I
>>> haven't found a good backport. I'd also like to avoid doing thing
On 02/22/2017 12:23 PM, Phil Mayers wrote:
On 22/02/17 15:00, Steve Waterbury wrote:
Have you considered the 'conda' package manager?
I've never come across it. It looks too big for me to give a quick
opinion on, but I'll bear it in mind. Thanks for the pointer.
"Anaconda" is huge; conda is
On 22/02/17 15:00, Steve Waterbury wrote:
Have you considered the 'conda' package manager?
I've never come across it. It looks too big for me to give a quick
opinion on, but I'll bear it in mind. Thanks for the pointer.
___
Twisted-Python mailing
On 22/02/17 13:06, Jean-Paul Calderone wrote:
Ah! They are now, maybe you haven't seen them?
Check out https://github.com/pypa/manylinux and
https://github.com/pypa/python-manylinux-demo
I had not seen this. Thanks, this looks like a big leap forward.
A lot of people seem to be thinking th
On 22/02/17 12:49, Hynek Schlawack wrote:
That’s why you should use a build server and not ship build
environments.
Which we do.
I don’t see how that’s tedious since a compute does that for me.
Although I don’t see any value at wheeling them (and some packages
cannot be wheeled); my CI build
>
>> So my problem is that while my protocol stack spins up very nicely and
>> trivially easy using the twistd daemon, the standard python3-twisted package
>> for 14.04 is wy behind and doesn't include twistd (!), and I haven't
>> found a good backport. I'd also like to avoid doing things
On 02/22/2017 07:08 AM, Phil Mayers wrote:
On 22/02/17 11:12, Glyph Lefkowitz wrote:
I'm tempted to launch into a diatribe about namespacing, containers, and
application isolation generally, but before I do - why is it that you
/want/ to use the system Python environment? Had you just not
cons
On Wed, Feb 22, 2017 at 7:08 AM, Phil Mayers
wrote:
> On 22/02/17 11:12, Glyph Lefkowitz wrote:
>
> I'm tempted to launch into a diatribe about namespacing, containers, and
>> application isolation generally, but before I do - why is it that you
>> /want/ to use the system Python environment? Ha
>> I'm tempted to launch into a diatribe about namespacing, containers, and
>> application isolation generally, but before I do - why is it that you
>> /want/ to use the system Python environment? Had you just not
>> considered the option of virtual environments?
> Awesome though it is, virtualen
On 22/02/17 11:12, Glyph Lefkowitz wrote:
I'm tempted to launch into a diatribe about namespacing, containers, and
application isolation generally, but before I do - why is it that you
/want/ to use the system Python environment? Had you just not
considered the option of virtual environments?
i could be totally wrong, and please correct me if i am, but try this:
target: this will give you a current twisted / python installation and
keep the packages seperate from the system ones
# 1. install a package called virtualenv and pip on your system
apt install virtualenv pip
# 2. create a
> On Feb 21, 2017, at 9:28 AM, Dave Curtis wrote:
>
> Hi, so for my first post to the list I am going to ask a somewhat lame
> question. Apologies if this is not the right list -- clues welcome.
This is totally the right list. All discussion of Twisted is welcome!
> So my problem is that wh
20 matches
Mail list logo
