Hi Barry!
Thanks for your feedback.
> On Mar 25, 2019, at 10:22 AM, Scott, Barry wrote:
>
> We are stuck on python2.7 for the foreseeable future and you will not see us
> in the PyPi stats. We download your release tar ball and build an RPM from it.
> We also have to build python2.7 our selves
> On Mar 25, 2019, at 3:15 AM, Amber Brown wrote:
>
> Hi everyone,
>
> Since the Python 2 EOL date is rapidly approaching, I thought it was time we
> consider dropping Python 2 support.
>
> I personally find that Python 2 compat adds a huge amount of overhead when
> working on and maintaining
My application works on both Python 2.7 and 3. All my and my customer
sites are now on Python 3 (there was a year or so of both), so I've
stopped testing on 2.7, though I haven't done anything deliberate to
break it.
I hope/expect that none of my code changes to make my source compatible
wit
+1
Werner
On 3/25/19 07:22, Scott, Barry wrote:
> On Monday, 25 March 2019 10:15:22 GMT Amber Brown wrote:
>> Hi everyone,
>>
>> Since the Python 2 EOL date is rapidly approaching, I thought it was
>> time we consider dropping Python 2 support.
>>
>> I personally find that Python 2 compat adds a
On Monday, 25 March 2019 10:15:22 GMT Amber Brown wrote:
> Hi everyone,
>
> Since the Python 2 EOL date is rapidly approaching, I thought it was
> time we consider dropping Python 2 support.
>
> I personally find that Python 2 compat adds a huge amount of overhead
> when working on and maintainin
> Interesting library.
>
> It seems that I cannot have a action finish with an error unless I raise an
> exception. That seems limiting, there are lots of cases where I have code
> that hits an error condition and does not raise an exception. For example
> an HTTP request that gets a non 200 statu
On Thursday, 21 March 2019 15:27:35 GMT Itamar Turner-Trauring wrote:
> Python and Twisted's built-in `logging` output a stream of factoids: they’re
> interesting, but you can’t really tell what’s going on.
>
> * Why is your application slow?
> * What caused this code path to be chosen?
> * Why
Hi Amber -
Notwithstanding the fact that VFX/Anim will be stuck on PY2 for a few more
years, this all sounds very reasonable. None of the proposed timelines
would cause problems for my team.
Many thanks
DJM
On Mon, 25 Mar 2019 at 10:15, Amber Brown wrote:
> Hi everyone,
>
> Since the Python 2
On Mon, 25 Mar 2019 at 10:15, Amber Brown wrote:
>
> Hi everyone,
>
> Since the Python 2 EOL date is rapidly approaching, I thought it was
> time we consider dropping Python 2 support.
>
[snip]
> You can find the proposal here, in this handy-dandy Google Doc:
> https://docs.google.com/document/d
On Monday, 25 March 2019 11:15:22 CET Amber Brown wrote:
> One of my rationales is that from some analysis of PyPI download
> statistics, the vast majority of Python 2 users are using old versions
> of Twisted, while nearly all our Python 3 users are on the latest
> version. As such, I believe fre
Hi everyone,
Since the Python 2 EOL date is rapidly approaching, I thought it was
time we consider dropping Python 2 support.
I personally find that Python 2 compat adds a huge amount of overhead
when working on and maintaining Twisted, and think that with the current
maintainer availability
11 matches
Mail list logo
