Re: [Twisted-Python] process changes causing buildbot failures on win7?

[Hawkie]

It's because the Windows tests (that one) can't cope with spaces in the exe 
name, and now it's in a virtual env, that's popped up. 

The Python 3.5 branch has a fix for this, as the Windows 3.5 builder was the 
first to show this problem. 

-hawkie

On 10 Oct 2015 06:27, Glyph Lefkowitz  wrote:
>
> These failures:
>
>> ===
>>
>> [FAIL]
>>
>> Traceback (most recent call last):
>>
>>   File "C:\Users\Build 
>> Slave\bot-glyph-6\windows7-64-py2.7-select\Twisted\twisted\internet\test\test_process.py",
>>  line 361, in test_systemCallUninterruptedByChildExit
>>
>> self.assertEqual(result, ["Foo\n"])
>>
>>   File "C:\Users\Build 
>> Slave\bot-glyph-6\windows7-64-py2.7-select\Twisted\twisted\trial\_synctest.py",
>>  line 437, in assertEqual
>>
>> super(_Assertions, self).assertEqual(first, second, msg)
>>
>>   File "C:\Python27\Lib\unittest\case.py", line 513, in assertEqual
>>
>> assertion_func(first, second, msg=msg)
>>
>>   File "C:\Python27\Lib\unittest\case.py", line 742, in assertListEqual
>>
>> self.assertSequenceEqual(list1, list2, msg, seq_type=list)
>>
>>   File "C:\Python27\Lib\unittest\case.py", line 724, in assertSequenceEqual
>>
>> self.fail(msg)
>>
>> twisted.trial.unittest.FailTest: Lists differ: [''] != ['Foo\n']
>>
>>
>>
>> First differing element 0:
>>
>>
>>
>> Foo
>>
>>
>>
>>
>>
>> - ['']
>>
>> + ['Foo\n']
>>
>>
>>
>> twisted.internet.test.test_process.ProcessTestsBuilder_IOCPReactorTests.test_systemCallUninterruptedByChildExit
>>
>> twisted.internet.test.test_process.ProcessTestsBuilder_SelectReactorTests.test_systemCallUninterruptedByChildExit
>>
>> twisted.internet.test.test_process.ProcessTestsBuilder_Win32ReactorTests.test_systemCallUninterruptedByChildExit
>>
>>
> have started happening on the buildbot on trunk: 
> https://buildbot.twistedmatrix.com/builders/windows7-64-py2.7/builds/5215/steps/select/logs/problems
>
> soon after this change: http://twistedmatrix.com/trac/changeset/45725
>
> Unfortunately the buildbot was in a kind of unrelated bad state when it 
> landed, and the configuration is a bit different now, so I'm not sure if this 
> is a regression or a configuration error.  But given that the change was 
> about processes, and the failure is in the process test, I thought it might 
> bear some investigation...
>
> -glyph
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Running Trial [wav]: Re: Possible bug

[Hawkie]

This is on Windows - I've linked the relevant ticket earlier (#8025 iirc?) 
which will bring Windows up to par.

-Amber

On 2 Nov 2015 11:09, Glyph Lefkowitz  wrote:
>
>
>> On Oct 31, 2015, at 01:31, Chris Norman  wrote:
>>
> Hi,
> So I went on the net on the off chance that the info I was looking for was 
> easy to obtain, and I found out about trial.
>
> I cloned the git and did:
> python bin/trial twisted
>
> I got the following:
>
>> Is that a trial error or a Twisted test failing?
>>
>> Sorry if this is a stupid question, but (terrible, I know) I've never used 
>> tests before.
>>
>> Another quick google told me that Trial was ported to Python3, so I'm not 
>> sure... If it's a test failing, it's not really telling me where the failure 
>> is.
>
>
> Not _all_ of Twisted has been ported to Python 3, so if you run the full test 
> suite (that's what "trial twisted" does) some of it will fail.
>
> If you want to run the parts that are expected to pass, run `python 
> admin/run-python3-tests´.  If those fail then we have a problem :).
>
> -glyph
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted is removing Python 2.6 support

[Amber "Hawkie" Brown]

Hi everyone,

As mentioned in 
http://twistedmatrix.com/pipermail/twisted-python/2015-March/029258.html , 
Twisted is removing Python 2.6 support. As such, I would like to announce that 
15.3 will be the last release with 2.6 support. After this release, the Python 
2.6 buildbots will be removed from the 'supported' list and most likely retired.

This will remove all buildbot coverage of OS X and RHEL/CentOS. As I've been 
taking point on the buildbots recently, I'm going to be deploying a new CentOS 
7 buildslave which will provide coverage of that platform. That just leaves OS 
X uncovered -- so if you would like to donate buildslaves for this, please send 
me an email.

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] [Twisted-web] Twisted is removing Python 2.6 support

[Amber "Hawkie" Brown]

> On 8 Jun 2015, at 17:27, exar...@twistedmatrix.com wrote:
> 
> On 05:57 am, hawk...@atleastfornow.net wrote:
>> Hi everyone,
>> 
>> As mentioned in http://twistedmatrix.com/pipermail/twisted- 
>> python/2015-March/029258.html , Twisted is removing Python 2.6 support. As 
>> such, I would like to announce that 15.3 will be the last release with 2.6 
>> support. After this release, the Python 2.6 buildbots will be removed from 
>> the 'supported' list and most likely retired.
>> 
>> This will remove all buildbot coverage of OS X and RHEL/CentOS. As I've been 
>> taking point on the buildbots recently, I'm going to be deploying a new 
>> CentOS 7 buildslave which will provide coverage of that platform. That just 
>> leaves OS X uncovered -- so if you would like to donate buildslaves for 
>> this, please send me an email.
> 
> I think this is backwards.  There was basically no strong argument made 
> against dropping Python 2.6 support but there was no case made for dropping 
> OS X support.  I don't think you can remove the only OS X builder from the 
> supported list.  That's equivalent to saying OS X support is being dropped.
> 
> So either the existing OS X slaves need to be upgraded first (I don't see why 
> you wouldn't just do this) or Python 2.6 support (at least on OS X) needs to 
> be retained until someone else volunteers a Python 2.7 OS X slave.
> 
> Jean-Paul
> 
> ___
> Twisted-web mailing list
> twisted-...@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web

Hi JP,

I know that this would leave OS X uncovered -- lukasa, habnabit, and Adi have 
at separate points offered OS X builders of varying OS levels and even Python 
versions, both on the mailing list and in #twisted-dev (where Lukasa answered 
the call from this email and offered a Yosemite builder today), which is why I 
am confident that this will not end up being an issue when 15.3's first 
prerelease is issued.

I think the prevailing reason that we don't have an OS X 2.7 bot is that last 
time OS X hardware was offered, the buildbot was not being actively maintained. 
I've taken up the mantle in some capacity and getting Twisted supported on more 
platforms is my primary goal. And as an OS X user, I have some vested interest 
in it continuing being supported.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] [Twisted-web] Twisted is removing Python 2.6 support

[Amber "Hawkie" Brown]

> On 8 Jun 2015, at 17:57, exar...@twistedmatrix.com wrote:
> 
> On 09:42 am, hawk...@atleastfornow.net wrote:
>> 
>>> On 8 Jun 2015, at 17:27, exar...@twistedmatrix.com wrote:
>>> 
>>> On 05:57 am, hawk...@atleastfornow.net wrote:
 Hi everyone,
 
 As mentioned in http://twistedmatrix.com/pipermail/twisted- 
 python/2015-March/029258.html , Twisted is removing Python 2.6 support. As 
 such, I would like to announce that 15.3 will be the last release with 2.6 
 support. After this release, the Python 2.6 buildbots will be removed from 
 the 'supported' list and most likely retired.
 
 This will remove all buildbot coverage of OS X and RHEL/CentOS. As I've 
 been taking point on the buildbots recently, I'm going to be deploying a 
 new CentOS 7 buildslave which will provide coverage of that platform. That 
 just leaves OS X uncovered -- so if you would like to donate buildslaves 
 for this, please send me an email.
>>> 
>>> I think this is backwards.  There was basically no strong argument made 
>>> against dropping Python 2.6 support but there was no case made for dropping 
>>> OS X support.  I don't think you can remove the only OS X builder from the 
>>> supported list.  That's equivalent to saying OS X support is being dropped.
>>> 
>>> So either the existing OS X slaves need to be upgraded first (I don't see 
>>> why you wouldn't just do this) or Python 2.6 support (at least on OS X) 
>>> needs to be retained until someone else volunteers a Python 2.7 OS X slave.
>>> 
>>> Jean-Paul
>>> 
>>> ___
>>> Twisted-web mailing list
>>> twisted-...@twistedmatrix.com
>>> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
>> 
>> Hi JP,
>> 
>> I know that this would leave OS X uncovered -- lukasa, habnabit, and Adi 
>> have at separate points offered OS X builders of varying OS levels and even 
>> Python versions, both on the mailing list and in #twisted-dev (where Lukasa 
>> answered the call from this email and offered a Yosemite builder today), 
>> which is why I am confident that this will not end up being an issue when 
>> 15.3's first prerelease is issued.
> 
> I'd be even more confident if you don't disable the Python 2.6 OS X builder 
> until a new Python 2.7 OS X builder is set up.  If this turns out to be easy, 
> then nothing has been lost.  If it ends up being hard, then it's much better 
> than having a screwed up 15.3.

15.3 is the last release *with* Python 2.6 support -- that is, the 2.6 builders 
will be on the supported list until at least 15.3 is released. The goal is that 
we have both 2.6 and 2.7 on OS X tested before 15.3's release.

>> I think the prevailing reason that we don't have an OS X 2.7 bot is that 
>> last time OS X hardware was offered, the buildbot was not being actively 
>> maintained. I've taken up the mantle in some capacity and getting Twisted 
>> supported on more platforms is my primary goal. And as an OS X user, I have 
>> some vested interest in it continuing being supported.
> 
> Once again, I'm not really clear on why the existing build slaves aren't just 
> being upgraded.  Why is new hardware required?

I would much prefer to have a new builder to take up the role, migrate the 
buildslave roles, and then upgrade the existing 10.6 slave once we have 
something new working. That way, if something goes wrong during the upgrade, we 
maintain a supported OS X builder.

-

I think I've been failing at communication a bit -- a prerequisite of dropping 
2.6 support has always hinged on getting 2.7 (and optionally 3.3/3.4) builders 
for platforms that only had 2.6. I have a RHEL7 builder in the wings to get 
that platform supported, Debian has 7 & 8 now supported, and there's OS X, 
which I am confident I can get 2.7 builders set up for before 15.3.

- Amber

> 
> Jean-Paul
> 
> ___
> Twisted-web mailing list
> twisted-...@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] [Twisted-web] Twisted is removing Python 2.6 support

[Amber "Hawkie" Brown]

Hi John,

Glyph's discussing the other Mac Mini hosted by the Oregon State University 
Open Source Lab -- the EGH one is the one we upgraded tonight to 10.10 and is 
now our first supported 10.10-py27 builder 
(http://buildbot.twistedmatrix.com/builders/osx10.10-py2.7/builds/6). So 
everything's all good with that :)

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl

> On 8 Jun 2015, at 21:46, John Santos  wrote:
> 
> 
> 
> Hi Glyph,
> 
> Is this the Mac Mini we are hosting for you?  Could I help with anything?
> 
> 
> 
> 
> --
> John Santos
> Evans Griffiths & Hart, Inc.
> 781-861-0670 ext 539
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Unsupported buildbots and future supported platforms

[Amber "Hawkie" Brown]

Glyph and I have been discussing the state of "unsupported" buildbots for the 
Twisted project, and some of the cleanup of unsupported platforms that I've 
been doing. To get the reasons for this, and an idea of the future out, Glyph 
suggested I post to the mailing list.

In the past, a lot of the unsupported buildbots were platforms that we knew 
didn't work. A lot of these have been tested for many months, kept in the 
unsupported list, and not had much progress. We need to focus on the 
unsupported builders that have a path to being supported, and get them onto the 
supported list.

I've now removed broken, absent, or superseded builders, giving us five 
unsupported builders. These are:

- FreeBSD 10.1, Python 3.4 -- Tests almost pass, waiting on 
https://twistedmatrix.com/trac/ticket/7887 to make it all-green. Once it is 
green, it can move to supported.
- OS X 10.6, Python 2.6, cfreactor -- There are only a few failing tests -- 
soon, there'll be a OS X 10.10 cfreactor builder (once we get XCode installed 
on it :) )
- Python 3K Warnings -- Two failures, which are warnings counting -- should be 
trivial.
- Ubuntu Trusty, Python 2.7, wxreactor -- broken, needs fixing
- Ubuntu Trusty, PyPy 2.4. -- 32 failing tests 
http://buildbot.twistedmatrix.com/builders/trusty64-pypy-2.4/builds/132/steps/trial/logs/problems
 . Some are pypy, some are configuration related.

These builders should ideally move into the 'supported' list in the future. To 
do this, we need to:

- Get https://twistedmatrix.com/trac/ticket/7887 reviewed to get the FreeBSD 
10.1 + Python 3.4 builder as a supported platform
- Fix https://twistedmatrix.com/trac/ticket/7931 to make the Python 3K Warnings 
builder pass
- Get a new OS X 10.10 cfreactor builder, to see what failures there are on 
Python 2.7
- Redeploy the wxreactor builder, see what failures there are. I'm planning to 
do this on a newly deployed Ubuntu 15.04 machine when I get time.
- File more tickets in 
https://twistedmatrix.com/trac/query?group=status&milestone=PyPy-support for 
the failures on the PyPy builder and fix them. I'm planning on also doing a 
PyPy 2.6 builder using the aforementioned Ubuntu 15.04 buildbot, using the PPA, 
which should shake out the new dict-sorting bugs.

If you would like to see these builders become supported in the future, please 
do consider helping out! :)

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] New Supported Platforms (FreeBSD 10.1/Python 2.7, OS X 10.10/Python 2.7)

[Amber "Hawkie" Brown]

Hi everyone,

Just so you know, Twisted has had two more builders added to the supported 
list. These are:

- FreeBSD 10.1 with Python 2.7
- Apple OS X 10.10 Yosemite with Python 2.7

Many thanks to Tavendo for the FreeBSD builder and Glyph for updating one of 
our OS X 10.6 builders to 10.10 so that I could get Python 2.7 builds running 
on it.

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Proposal -- Code of Conduct

[Amber "Hawkie" Brown]

> On 21 Jun 2015, at 19:00, Hynek Schlawack  wrote:
> 
>>> I am sure everyone understands that the Twisted community would love more 
>>> diversity. While it is hard to achieve, it should be easy to remove one of 
>>> the obvious blockers -- making underrepresented groups feel more welcome.
>> Thanks for taking this on, Moshe.
> 
> +1
> 
>>> My current draft, including instructions on how to build it, is in 
>>> https://github.com/moshez/twisted-coc . I have intentionally not made the 
>>> built documents available, in an attempt to avoid someone picking them up 
>>> before they're approved by us.
>> 
>> Why isn't this repository either (A) just a simple text file saying "we have 
>> adopted the Django CoC" or (B) a very small fork of something else?  One of 
>> the concerns is licensing; if the text comes via Django, Django credits the 
>> "Speak Up!" project, which is CC-BY, apparently from this repository: 
>> .  Another is... is Twisted 
>> really distinct enough to need its own CoC?  Just s/Django/Twisted might be 
>> good enough?  (Since this is not a fork, figuring out if anything else has 
>> changed is rather tedious, even after having read both ;)).
> 
> I wonder whether it might make sense to just say we adopt 
> https://www.python.org/psf/codeofconduct/ ?
> 
> What I would really love is if we could have our own diversity statement like 
> Django has: https://www.djangoproject.com/diversity/

The Django one is more explicit -- it's rather sad that it needs to be, but it 
does lay out more directly the unacceptable behaviours.

That being said, it's not an unchangeable document -- if it doesn't suit the 
community's needs, we can modify it to suit.

> 
> Cheers,
> —h
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Proposal -- Code of Conduct

[Amber "Hawkie" Brown]

> On 24 Jun 2015, at 10:12, Glyph  wrote:
> 
>>> Why isn't this a fork of an existing CoC?
> 
> I agree that this is a problem.  Django does not appear to have their CoC in 
> an easily-forkable format.  Perhaps we should contact the Django project and 
> ask them to rectify that so that we can make minor tweaks.  We also do need 
> minor tweaks, because the information about contact points for reporting has 
> to be different for different projects.

As a member of the Django CoC committee, I will pass this suggestion on.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Proposal -- Code of Conduct

[Amber "Hawkie" Brown]

Russ has informed me that it's accessible on 
https://github.com/django/djangoproject.com/blob/master/djangoproject/templates/conduct/index.html
 -- so we could potentially fork the repo and make it just that file or so :)

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl

> On 24 Jun 2015, at 12:06, Amber Hawkie Brown  
> wrote:
> 
> 
>> On 24 Jun 2015, at 10:12, Glyph  wrote:
>> 
>>>> Why isn't this a fork of an existing CoC?
>> 
>> I agree that this is a problem.  Django does not appear to have their CoC in 
>> an easily-forkable format.  Perhaps we should contact the Django project and 
>> ask them to rectify that so that we can make minor tweaks.  We also do need 
>> minor tweaks, because the information about contact points for reporting has 
>> to be different for different projects.
> 
> As a member of the Django CoC committee, I will pass this suggestion on.
> 
> - Amber
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] INCOMPATIBLE CHANGE: Removing hotshot from twistd's profiler support

[Amber "Hawkie" Brown]

Hotshot is completely broke, and it doesn't exist in Python 3. It is currently 
the default for twistd and since it doesn't work, we should just sidestep the 
deprecation cycle and remove it, changing the default to something useful.

The ticket with the changes are available on 
https://twistedmatrix.com/trac/ticket/5137 . The branch attached to it removes 
HotshotProfiler and amends the default to be cProfile, which is the most useful 
for users.

In accordance with the policy 
(https://twistedmatrix.com/trac/wiki/CompatibilityPolicy#ProcedureforExceptionstothisPolicy),
 this will remain unmerged for at least a week, and requires three signoffs by 
committers.

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Proposed compat policy change in regards to unmaintained upstream dependencies

[Amber "Hawkie" Brown]

Hi,

Since it's been coming up recently, I'm proposing a change to the compat 
policy, where removing the use of unmaintained/unsupported upstream 
dependencies is an automatic exception.

This was brought up by Glyph in 
https://twistedmatrix.com/trac/ticket/5137#comment:11 -- hotshot is broken, 
unsupported, and unmaintained, and removing something that doesn't work in the 
first place should be able to be done automatically. This was also the case 
with PyPAM -- it didn't even seemingly exist, so the Twisted support code 
couldn't work at all.

So, this email is to get general comment on the scope and possibility of such a 
change. I believe it would be a worthwhile addition to the policy.

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] New Buildbots -- Ubuntu 15.04 & Fedora 22

[Amber "Hawkie" Brown]

Hi everyone,

I've just set up two new pairs of bots -- Ubuntu 15.04 and Fedora 22. They will 
provide the following coverage:

- Ubuntu 15.04 -- Python 2.7, PyPy 2.5.0, Python 3.4
- Fedora 22 -- Python 2.7, PyPy 2.4.0, Python 3.4

The Ubuntu 15.04 (Py2.7) builder is passing and has moved to supported, while 
the Fedora 22 (Py2.7) builder has failing tests (see them at 
https://buildbot.twistedmatrix.com/builders/fedora22-py2.7/builds/0 ). PyPy on 
both platforms fails, and are unsupported builders. Python 3.4 builds for each 
will be set up soon.

These new builders also have their dependencies installed by virtualenv, so the 
versions of the dependencies are now more controllable and should be kept up to 
date as new versions of them are released.

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Benchmarks 2.0

[Amber "Hawkie" Brown]

Hi everyone,

I'm going to be renovating http://speed.twistedmatrix.com/ soon. Because of the 
svn -> git migration, the historical data will be archived, so, if you're 
interested, I'd check it out now.

The new Twisted Speedcenter will have Python 2.7, Python 3.4, and PyPy 2.5, all 
of the standard versions of Python on Ubuntu 15.04. The benchmarks that it will 
be running can be found at https://github.com/twisted-infra/twisted-benchmarks .

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.3.0 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hi everyone!

Another Twisted release cycle dawns, and I bring you the first prerelease of 
Twisted 15.3.

This release is characterised by cleanups and porting, with at least ten 
modules ported to Python 3, and the removal of Lore, Twisted's use of Hotshot, 
and various other smaller deprecated classes and functions. Twisted has also 
shed its usage of "subprojects" -- there is now only one Twisted (long may it 
reign).

The tarball and the newsfile summarising all the changes can be downloaded from 
<http://twistedmatrix.com/Releases/pre/15.3.0pre1/>.

Enjoy, and test! If no issues are found, 15.3 will be released sometime next 
week.

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Benchmarks 2.0

[Amber "Hawkie" Brown]

> On 23 Jul 2015, at 17:47, Adi Roiban  wrote:
> 
> On 22 July 2015 at 05:33, Amber "Hawkie" Brown
>  wrote:
>> Hi everyone,
>> 
>> I'm going to be renovating http://speed.twistedmatrix.com/ soon. Because of 
>> the svn -> git migration, the historical data will be archived, so, if 
>> you're interested, I'd check it out now.
>> 
>> The new Twisted Speedcenter will have Python 2.7, Python 3.4, and PyPy 2.5, 
>> all of the standard versions of Python on Ubuntu 15.04. The benchmarks that 
>> it will be running can be found at 
>> https://github.com/twisted-infra/twisted-benchmarks .
> 
> Thanks for working on this!
> 
> Why are the benchmarks part of twisted-infra and not of twisted ?
> 

No particular reason. I just put them there as they're connected to our infra, 
but really, they are a form of validation test and should be moved into Twisted 
when everything is rolling and they can be used better for that.

> 
> --
> Adi Roiban
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Considerations for Twisted prereleases on PyPI

[Amber "Hawkie" Brown]

Hi everyone,

PyPI + pip has supported uploading prereleases for a long while, and this would 
be a much better way for you, the Twisted user, to get the prereleases, rather 
than messing about with tarballs.

Pip 1.4+ (which according to 
https://caremad.io/2015/04/a-year-of-pypi-downloads/ constitutes 80%+ of pips) 
supports prereleases on PyPI.

So, the question is, do people think we should start putting them on PyPI? Is 
it worth some users on ancient pips inadvertantly getting (admittedly quite 
stable) prereleases? Would you use it, and would you be more likely to test 
Twisted prereleases if they were distributed like this (in addition to the 
tarball)?

Thanks,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] An error occurred with twisted 15.2.1 & python 3.4.3 on windows

[Amber "Hawkie" Brown]

> On 29 Jul 2015, at 10:38, Glyph Lefkowitz  wrote:
> 
>> 
>> On Jul 28, 2015, at 3:29 AM, Gelin Yan  wrote:
>> 
>> 
>> 
>> On Tue, Jul 28, 2015 at 3:46 PM, Tristan Seligmann  
>> wrote:
>> On Mon, 27 Jul 2015 at 13:18 Gelin Yan  wrote:
>>   Is it a bug?
>> 
>> Yes; see https://twistedmatrix.com/trac/ticket/7626 for more details.
>> 
>> ___
>> Twisted-Python mailing list
>> Twisted-Python@twistedmatrix.com
>> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>> 
>> 
>>   It looks like this bug has existed for almost one year. Do we have windows 
>> building slave for python 3?
> 
> No.  For this reason, technically Twisted only supports Python 3 on Linux.  
> Does anyone feel like volunteering to set up a 3 builder?  I wonder if 
> HawkOwl has already done this...

I haven't -- I don't think I have access or know how to get onto the Windows 
builders. Happy to set up a Py3 tests+coverage builder (after PyCon AU, that 
is). (Also, I might set up a Py2.7 coverage builder now we have 
https://codecov.io/github/twisted/twisted to combine it...)

- Amber

> 
> -glyph
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.3.0pre2 Prerelease Announcement

[Amber "Hawkie" Brown]

Hi everyone,

I've just uploaded 15.3.0pre2 to 
http://twistedmatrix.com/Releases/pre/15.3.0pre2/ , which provides a small fix 
for Twisted-using libraries that subclass Protocol overwriting the `_log` 
attribute.

Please test your software with it, but as this is a very minor change, I will 
release it very soon.

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.3 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Labs, I am honoured to announce the release of 
Twisted 15.3.

We're marching confidently into the future, and this release demonstrates this:

* 10+ modules ported to Python 3 (see NEWS for specifics)
* Twisted Lore has been removed.
* Twisted no longer releases as 'subprojects' -- there is only one 
Twisted, long may it reign.
* twistd now uses cProfile (instead of Hotshot) as the default profiler.
* 40+ more tickets closed overall.

You can find the downloads at https://pypi.python.org/pypi/Twisted (or 
alternatively http://twistedmatrix.com/trac/wiki/Downloads). The NEWS file can 
be found at https://github.com/twisted/twisted/blob/trunk/NEWS .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] failing coverage builders

[Amber "Hawkie" Brown]

Hi Glyph,

I'll take a look.

I find the combined codecov rather valuable for figuring out what isn't covered 
on either, but I'll remove it for now.

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl

> On 7 Aug 2015, at 04:32, Glyph  wrote:
> 
> The python 3.4 coverage builders are failing, apparently because one of the 
> builders is down:
> 
> <https://buildbot.twistedmatrix.com/builders/debian7-py3.4-coverage/builds/399/steps/shell_5/logs/stdio>
> 
> I'll probably make those builders unsupported later today if there is no 
> obvious fix; at this point, depending on codecov is mostly just a net 
> negative.  We can't have it reasonably fail our builds or report status for 
> us, and "coverage html" produces perfectly usable coverage reports, and so 
> the main consequence is that our builds will fail if they're down (or if they 
> introduce a version of coverage on PyPI that doesn't support python 3, 
> apparently?)
> 
> -glyph
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Updates on the Twisted Buildbots

[Amber "Hawkie" Brown]

Hi everyone,

If you haven't looked at the buildbots for a while, there's been some changes! 
(for brevity's sake, unsupported builders will be prefixed with a U, eg "U2.7")

- Fedora 17 (2.7), 18 (2.7), 19 (2.7, 3.3), and RHEL6 (2.6) are removed, and 
replaced by RHEL7 (2.7), Fedora 21 (2.7, 3.4), Fedora 22 (U2.7, U3.4, to be 
fixed very soon, UPyPy2.4). RHEL6 will return with the 2.7 EPEL soon.
- FreeBSD 10.1 is supported on both Py2.7 and Py3.4.
- OS X 10.6 has been removed and OSX 10.10 has been added (2.7-select 
supported, kqueue and cfreactor both unsupported)
- Ubuntu 15.04 is now a supported platform (2.7, 3.4) and has unsupported PyPy 
(2.5) and Jython (2.7) builders.
- All of the builders (excepting Windows) are built and ran in a virtualenv. 
This means that they have up-to-date dependencies, and if Twisted gains 
dependencies, the infra team can add them to the build process easily.

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.4.0pre1 Prerelease Announcement

[Amber "Hawkie" Brown]

Hello everyone!

Another few months, another Twisted release. This one has a few more Py3 
goodies in it!

- twisted.positioning, the rest of twisted.internet.endpoints, KQueueReactor 
(for real this time), twisted.web.proxy/guard, and Trial (!!!) have all been 
ported to Python 3.
- Twisted officially supports several more platforms: Py3.4 on FreeBSD, 
Py2.7/Py3.4 on Fedora 21/22, and Py2.7 on RHEL7.
- Python 2.6 is no longer supported, and support for Debian 6, and RHEL6 has 
been removed because of this.
- Support for the EOL'd platforms of Fedora 17/18/19 has been removed.
- Twisted has moved to requiring setuptools for installation.
- twisted.python.failure.Failure's __repr__ now includes the  exception message.
- 19 tickets in total closed!

As usual, you can find the tarball and newsfile at 
http://twistedmatrix.com/Releases/pre/15.4.0pre1/ ! Please download them, test 
them, share them, appreciate them, make them a little nest so that they are 
comfortable. If there aren't any reported issues, this will be getting a full 
release soon.

Twisted Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.4.0 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 15.4, codenamed "Trial By Fire".

Twisted is continuing to forge ahead, with the highlights of this release being:

- twisted.positioning, the rest of twisted.internet.endpoints, KQueueReactor 
(for real this time), and twisted.web.proxy/guard have all been ported to 
Python 3.
- Trial has been ported to Python 3! This was made possible by a Python 
Software Foundation grant.
- Twisted officially supports several more platforms: Py3.4 on FreeBSD, 
Py2.7/Py3.4 on Fedora 21/22, and Py2.7 on RHEL7.
- Python 2.6 is no longer supported, and support for Debian 6, and RHEL6 has 
been removed because of this.
- Support for the EOL'd platforms of Fedora 17/18/19 has been removed.
- Twisted has moved to requiring setuptools for installation.
- twisted.python.failure.Failure's __repr__ now includes the exception message.
- 19 tickets in total closed!

You can find the downloads at https://pypi.python.org/pypi/Twisted (or 
alternatively http://twistedmatrix.com/trac/wiki/Downloads). The NEWS file can 
be found at https://github.com/twisted/twisted/blob/trunk/NEWS .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl
hawk...@atleastfornow.net


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Exception's Implicit Public API, and Python 3

[Amber "Hawkie" Brown]

We just ran into an issue in Autobahn|Python where a log message that tried to 
use the message attribute an Exception subclass 
(twisted.internet.error.ProcessTerminated). The message attribute was 
deprecated in Python 2.6, and removed in Python 3 -- but it still "works" in 
Python 2.7.

So, this needs the question: Is this breaking Twisted's backwards compat (that 
.message isn't there on Python 3)? Should we go through and look at our 
exception subclasses, and look at what makes sense to have a .message attribute 
(for example, I'd say it makes sense on ProcessTerminated) and then add it? Or 
is it just a 2/3 change that should be expected during porting? It seems like 
an interesting edge case (and another example of "Don't use subclassing, kids" 
;) ).

The Autobahn ticket (which we're fixing as I write this email) is here 
https://github.com/tavendo/AutobahnPython/issues/479 .

Regards,

Amber "Hawkie" Brown
GPG: https://keybase.io/hawkowl
hawk...@atleastfornow.net




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Changes to Twisted's binary distribution

[Amber "Hawkie" Brown]

Hi everyone,

Just letting everyone know, the next release (Twisted 15.5) will not include 
MSI or EXE installers for Windows, only binary wheels, and installation through 
pip or from source dist will be the only supported method of installation. The 
exe/msi installers didn't work well (or at all?) for virtualenvs, and when we 
(eventually) start shipping binary wheels for OS X, it'll make everything more 
consistent.

Regards,

Amber "Hawkie" Brown
Twisted Release manager
GPG: https://keybase.io/hawkowl
hawk...@atleastfornow.net




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Changing the Twisted Compatibility Policy

[Amber "Hawkie" Brown]

Hi everyone,

As many know, one of the things that makes the Twisted project so unique is our 
conformance to our Compatibility Policy. This policy means that users of 
Twisted can freely upgrade between versions with all incompatibilities being 
warned about before causing code to break. However, for a while, one part of 
the compatibility policy has caused issues - what we do with code that has been 
deprecated for a long time, and at least the release +  2 & 1 year after.

The existing policy states:

"Removal should happen once the deprecated API becomes an additional 
maintenance burden. For example, if it makes implementation of a new feature 
more difficult, if it makes documentation of non-deprecated APIs more 
confusing, or if its unit tests become an undue burden on the continuous 
integration system. Removal should not be undertaken just to follow a timeline."

This makes the only reasonable cause for any code being removed from Twisted is 
if it is a maintenance burden, but does not take into account the effect that 
keeping large amounts of deprecated code has on new, existing, and future 
Twisted users. It does specify that it should be removed if it makes 
documentation of non-deprecated APIs confusing, but by its very existence, it 
makes what should be "best practice" more confusing -- especially if the 
deprecated API is "simpler" at first glance, but was deprecated because of vast 
underlying issues,

Discussions have come to the conclusion that the exact reverse of this policy 
should be instated:

"Removal of code should occur as soon as the deprecation grace period has 
ended."

The reason for this is that a leaner Twisted is a better Twisted -- we should 
strive to not break existing applications, but we have the deprecation policy 
in place to ensure that breakage is, if all goes to plan, never out of the 
blue. Less code surface means that Twisted is easier to learn for new users and 
Twisted-using projects onboarding new people, easier to use for established 
users with a clear best practice, and easier to maintain because the codebase 
is not a web of things we deprecated and then never removed. We believe this 
change benefits everyone.

This is also similar to the deprecation policy of another time-based releasing 
project, Django 
(https://docs.djangoproject.com/en/1.8/internals/release-process/#internal-release-deprecation-policy),
 where releases are every 9 months and code is *always* removed in Release 
where deprecated + 2, giving them a deprecation grace period of up to 1 and a 
half years.

If you have any opinions on this change, please let me know, and we'll take it 
all into account before changing the policy.

Twisted Regards,
Amber "Hawkie" Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] revisiting onboarding

[Amber "Hawkie" Brown]

> On 27 Oct 2015, at 04:52, Chris Wolfe  wrote:
> 
> On 2 February 2015 at 19:18, Glyph Lefkowitz  wrote:
> [snip]
> > Not all committers are actively involved in the project at all times, so we 
> > should form a "committer committee"
> > of people who are interested in evaluating candidates.  If you would like 
> > to do that and you're already a committer,
> > please contact me and I'll add you to the list.
> 
> It looks like this new process has stalled on the formation of the committee 
> to review new contributor requests. As of right now, the committee has no 
> members. :-)
> 
> This email is a call for volunteers. If you would like to serve on the 
> committee, please reply to this thread and state that you are interested in 
> serving on the committee. Once enough volunteers have signed up, new 
> contributor requests will be sent to the committee's mailing list.

I'm happy to be on this.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Possible bug

[Amber "Hawkie" Brown]

Hi Chris,

Twisted does not yet support Python 3 on Windows.

There's a ticket at https://twistedmatrix.com/trac/ticket/8025#ticket which 
makes all the tests pass on the platform; I just need to work on it some more. 
I expect Twisted 16.0 to have base support for Python 3 on Windows.

- Amber

> On 31 Oct 2015, at 14:41, Chris Norman  wrote:
> 
> Hi all,
> Using windows 10 with Python 3.5, importing pretty much anything gives me the 
> following error. Not sure if there's something wrong with my configuration or 
> if it's a bug... I seem to remember something a while back, should I file a 
> ticket?
> 
> 
> Traceback (most recent call last):
>  File "", line 1, in 
>  File "C:\python35\lib\site-packages\twisted\internet\reactor.py", line 38, 
> in 
>from twisted.internet import default
>  File "C:\python35\lib\site-packages\twisted\internet\default.py", line 56, 
> in 
>install = _getInstallFunction(platform)
>  File "C:\python35\lib\site-packages\twisted\internet\default.py", line 50, 
> in _getInstallFunction
>from twisted.internet.selectreactor import install
>  File "C:\python35\lib\site-packages\twisted\internet\selectreactor.py", line 
> 18, in 
>from twisted.internet import posixbase
>  File "C:\python35\lib\site-packages\twisted\internet\posixbase.py", line 18, 
> in 
>from twisted.internet import error, udp, tcp
>  File "C:\python35\lib\site-packages\twisted\internet\udp.py", line 53, in 
> 
>from twisted.internet import base, defer, address
>  File "C:\python35\lib\site-packages\twisted\internet\base.py", line 23, in 
> 
>from twisted.internet import fdesc, main, error, abstract, defer, threads
>  File "C:\python35\lib\site-packages\twisted\internet\defer.py", line 29, in 
> 
>from twisted.python import lockfile, failure
>  File "C:\python35\lib\site-packages\twisted\python\lockfile.py", line 52, in 
> 
>_open = file
> NameError: name 'file' is not defined
> 
> Cheers,
> 
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] The End of Windows XP Support in Twisted 15.5

[Amber "Hawkie" Brown]

Hi everyone,

We've just removed the Windows XP builder from our buildbot. Many thanks for 
Tom Prince for keeping it online for so long, but right now, we think it's time 
to retire targeting XP.

Our only current supported Windows platform is Windows 7 x64, with Python 
2.7.10, with Python 3.4 and Python 3.5 support coming soon.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.5 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hello everyone!

Hot off the presses comes Twisted 15.5.0pre1, the prerelease of Twisted 15.5, 
which has been described by some as "totally radical" and "off the wall".

In this release:

- Python 3.5 support on POSIX was added, and Python 2.6 support was dropped.
- More than nine additional modules have been ported to Python 3, ranging from 
Twisted Web's Agent and downloadPage, twisted.python.logfile, and many others, 
as well as...
- twistd is ported to Python 3, and its first plugin, web, is ported.
- twisted.python.url, a new URL/IRI abstraction, has been introduced to answer 
the question "just what IS a URL" in Twisted, once and for all.
- NPN and ALPN support has been added to Twisted's TLS implementation, paving 
the way for HTTP/2.
- Conch now supports the DH group14-sha1 and group-exchange-sha256 key exchange 
algorithms, as well as hmac-sha2-256 and hmac-sha2-512 MAC algorithms. Conch 
also works nicer with newer OpenSSH implementations.
- Twisted's IRC support now has a sendCommand() method, which enables the use 
of sending messages with tags.
- 55+ closed tickets overall.

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/15.5.0pre1/) to get the prerelease 
tarballs and the full NEWS file.

Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Thanks! <3

Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.5.0 Prerelease 2 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

Twisted 15.5.0pre2 is now available for download. This includes a bugfix for a 
regression in 15.5 which prevents Twisted Web's client from doing requests to 
raw IPv6 addresses.

You can find the new release and the NEWS file at 
https://twistedmatrix.com/Releases/pre/15.5.0pre2/. Please test it! If no more 
issues are found, 15.5 will release sometime at the end of this week.

Regards,
Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] doc breakage

[Amber "Hawkie" Brown]

> On 27 Nov 2015, at 20:10, Phil Mayers  wrote:
> 
> Does this look right?
> 
> https://twistedmatrix.com/documents/current/api/twisted.internet.interfaces.IReadWriteDescriptor.html
> 
> Looks like docs for logPrefix has stomped on docs for all the other interface 
> methods?
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Yeah, this is a bug in PyDoctor we haven't got to the bottom of... sorry!

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] doc breakage

[Amber "Hawkie" Brown]

> On 28 Nov 2015, at 15:04, Glyph  wrote:
> 
>> 
>> On Nov 28, 2015, at 1:39 AM, Amber Hawkie Brown  
>> wrote:
>> 
>> 
>>> On 27 Nov 2015, at 20:10, Phil Mayers  wrote:
>>> 
>>> Does this look right?
>>> 
>>> https://twistedmatrix.com/documents/current/api/twisted.internet.interfaces.IReadWriteDescriptor.html
>>> 
>>> Looks like docs for logPrefix has stomped on docs for all the other 
>>> interface methods?
>>> 
>>> ___
>>> Twisted-Python mailing list
>>> Twisted-Python@twistedmatrix.com
>>> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>> 
>> Yeah, this is a bug in PyDoctor we haven't got to the bottom of... sorry!
> 
> Do you happen to have a link to the bug?

Yep!

https://github.com/twisted/pydoctor/issues/10

The multiple inheritance is messing things up...

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.5 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 15.5!

The sixth (!!) release in 2015 has quite a few goodies in it -- incrementalism 
is the name of the game here, and everything is just a little better than it 
was before. Some of the highlights of this release are:

- Python 3.5 support on POSIX was added, and Python 2.6 support was dropped. We 
also only support x64 Python on Windows 7 now.
- More than nine additional modules have been ported to Python 3, ranging from 
Twisted Web's Agent and downloadPage, twisted.python.logfile, and many others, 
as well as...
- twistd is ported to Python 3, and its first plugin, web, is ported.
- twisted.python.url, a new URL/IRI abstraction, has been introduced to answer 
the question "just what IS a URL" in Twisted, once and for all.
- NPN and ALPN support has been added to Twisted's TLS implementation, paving 
the way for HTTP/2.
- Conch now supports the DH group14-sha1 and group-exchange-sha256 key exchange 
algorithms, as well as hmac-sha2-256 and hmac-sha2-512 MAC algorithms. Conch 
also works nicer with newer OpenSSH implementations.
- Twisted's IRC support now has a sendCommand() method, which enables the use 
of sending messages with tags.
- 55+ closed tickets overall.

For more information, check the NEWS file (link provided below).

You can find the downloads at <https://pypi.python.org/pypi/Twisted> (or 
alternatively <http://twistedmatrix.com/trac/wiki/Downloads>) .
The NEWS file is also available at 
<https://github.com/twisted/twisted/blob/twisted-15.5.0/NEWS>.

Also worth noting is the two Twisted Software Foundation fellows -- Adi Roiban 
and myself -- who have been able to dedicate time to reviewing tickets and 
generally pushing things along in the process. We're funded by the Twisted 
Software Foundation, which is, in turn, funded by donators and sponsors -- 
potentially like you! If you would like to know how you can assist in the 
continued funding of the Fellowship program, see our website: 
https://twistedmatrix.com/trac/wiki/TwistedSoftwareFoundation#BenefitsofSponsorship

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,

Amber "Hawkie" Brown
Twisted Release Manager, Twisted Fellow


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Suggested plan for GitHub migration

[Amber "Hawkie" Brown]

Hi Craig,

Thanks for this, sharing your past experience is invaluable :)

I've gone through and thought about it a bit, and rewritten it into 
https://github.com/twisted-infra/braid/blob/git-migration-plan/gitmigration.rst 
-- it is basically your plan, with some added notes about Twisted Infra 
specific parts. I've skimmed over the specific details, since I feel that going 
too in-depth in such a plan will just be wasted effort as unknown issues arise, 
but with enough structure that we have a clear set of overarching goals for 
each step.

The migration will have a handful of policy changes that we will have to 
resolve -- such as ensuring that all merges have a topfile -- which aren't 
possible under a GitHub based system. I think these issues will just involve a 
lot of scrutiny and double checking during the transitional period until we are 
confident that we are enforcing our existing quality and process standards.

If anyone has any suggestions, or any more invaluable experience to share, 
please do :)

- Amber


> On 18 Nov 2015, at 07:48, Craig Rodrigues  wrote:
> 
> On Tue, Nov 17, 2015 at 8:57 AM, Adi Roiban  wrote:
> 
> For now, the funds were raised to migrate to GitHub, so we can not use
> them to do other things.
> 
> We will stay on Trac for issues... at least for now.
> 
> I have no idea how we can migrate to any issue tracker without losing
> data if we don't have full access to the database.
> 
> It is possible to migrate to another issue tracker and not lose
> data.  I've done Trac -> Redmine, and it works, but there was an existing 
> migration
> script I could use.
> For migrating to a cloud based bug tracker, you would need to take every user
> in the existing Trac database, and see if there would be a way to map
> the existing users to the cloud database, such as GitHub.  It's a lot of 
> work, but possible.
> However, for the scope of this project, if staying with Trac for issues is 
> what is required, that is fine.
> 
> 
> We don't plan to migrate to GitHub Issues / GitHub Wiki / GitHub Pages
> 
> 
> OK.
> 
> So based on what you have listed, I would say that most of the work will be
> working with Git post commit hooks.
> 
> I would say the plan should be something like this.
> 
> A.1  https://github.com/twisted/twisted will be the "repository of truth"
>for Twisted.
>-> Twisted releases will be done from GitHub
>-> the Twisted developers who are now "core committers" for SVN, 
> must be
>given access to be "core committers" to 
> https://github.com/twisted/twisted
> 
> A.2  On the Trac server, a local git mirror of the GitHub must be set up.
>Every bug tracker I've seen that integrates with git needs a local 
> mirror of the repo
> in order to parse the git history in order to update the bug database.
> This mirror should be read-only, and the only thing updating this 
> repo should be the Trac GitHub plugin.
> 
> A.3  On the Trac server, this plugin must be installed: 
> https://github.com/trac-hacks/trac-github
> 
> A.4  On the GitHub server, a post-commit web hook must be configured.  The 
> workflow will be this:
> 
>[core committer does push to https://github.com/twisted/twisted]
>  -> [post commit GitHub hook will be called to poke the Trac 
> GitHub plugin]
>  -> [Trac GitHub plugin will update the local git repo on the 
> Trac server]
>  -> [Trac GitHub will parse the git history for new commits and 
> update tickets]
> 
> I would recommend that steps (1) - (4) be made to work in a staging 
> environment, with a separate
> GitHub repo, and a separate copy of the Trac database.  That way, you can 
> test things out without derailing
> Twisted developers.  When you are confident that this workflow works, then 
> the transition plan will be something
> like the following.
> 
> B.1   Send an e-mail to the mailing list and pick one day for the maintenance 
> window.
> This will warn folks when they should take a holiday from Twisted 
> work. :)
> 
> B.2   When maintenance is about to begin, send a [HEADSUP] mail saying that 
> repo will be unavailable.
> 
> B.3  Create Subversion pre-commit hook to disable all commits to
>  Subversion:
>   
> http://stackoverflow.com/questions/2411122/how-to-freeze-entire-svn-repository-to-make-it-read-only
> 
> B.4  Set up steps A.1 - A.4
> 
> B.5  Verify that B.4 works.  Have someone (Glyph?) do a commit to 
> https://github.com/twisted/twisted, and
>  make sure that Trac works.
> 
> B.6  Once the Twisted core team are satisified that everything works, send an 
> e-mail to the mailing list
> that the maintenance window is over, and GitHub is now where the 
> action is!
> 
> B.7  Update all wiki documentation to change all references to getting code 
> from Subversion,
>  to getting code from GitHub.
> 
> B.8  Update all systems which used Subversion to use GitHub.  For 

[Twisted-Python] Supported Platform Changes: Fedora 23 (3.4) & Ubuntu 15.10 (2.7, 3.5) Added, Fedora 21 (2.7, 3.4) Removed

[Amber "Hawkie" Brown]

Hi everyone,

Three new platforms have been added as supported platforms for Twisted:

- Fedora 23, Python 3.4 (2.7 has test failures, will become supported soon)
- Ubuntu 15.10, Python 2.7
- Ubuntu 15.10, Python 3.5

Additionally, Fedora 21 has gone End Of Life and its builders have been removed.

Regards,

Amber Brown
Twisted Infrastructure Owl


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Suggested plan for GitHub migration

[Amber "Hawkie" Brown]

> On 4 Dec 2015, at 11:07, Glyph Lefkowitz  wrote:
> 
> 
>> On Dec 3, 2015, at 3:53 PM, Craig Rodrigues  wrote:
>> 
>> 
>> 
>> On Tue, Dec 1, 2015 at 5:01 PM, Glyph Lefkowitz  
>> wrote:
>> 
>> One thing that I'd love to see is a checklist that is kept up-to-date 
>> regarding which parts of this have already happened.
>> 
>> 
>> I worked with Amber and Adi and we have the checklist:
>> https://github.com/twisted-infra/braid/blob/git-migration-plan/gitmigration.md
> 
> Thank you very much for your participation in this.
> 
> The important thing about a "checklist" though, is checking things off - how 
> will that be kept up to date in sync with what has actually happened?
> 
> -glyph

When it's accepted, we can make it a GItHub issue, and then we can, well, click 
on the checkbox. :)

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [INCOMPATIBLE CHANGE] Removing Gadfly support from adbapi

[Amber "Hawkie" Brown]

So, apparently, a long time ago, there was a database called Gadfly, and 
Twisted used to test adbapi against it. However, since then, we've moved on 
from Python versions that gadfly supports, so it outright doesn't work now -- 
not buggy, not weird -- just doesn't even import.

This doesn't change any user facing code, but does change some tests, and even 
though it's covered under the compatibility policy, I thought I'd put it on the 
ML anyway. :)

You can find the code at https://twistedmatrix.com/trac/ticket/8119. We do not 
require any signoffs to remove it, this email is purely informational.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 15.4 was the last release to support Python 2.6; or: a HawkOwl Can't Words Situation

[Amber "Hawkie" Brown]

Hi everyone!

It's been brought to my attention that I misworded something in the release 
notes and it slipped through the cracks. In the NEWS I said:

> This is the last Twisted release where Python 2.6 is supported, on any 
> platform.

However, I meant that this is the first Twisted release to drop 2.6 support 
wholesale, preventing import on this platform. Twisted 15.4 will still operate, 
so if you have Python 2.6 deployment requirements, bracket the maximum to 15.4 
on that platform by using an if statement in your setup.py, and `Twisted 
>=*minreq*,<=15.4; python_version < '2.7'` under requires_dist in your 
setup.cfg, where minreq is the minimum required Twisted.

Sorry for the inconvenience!

- Amber "HawkOwl" Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] PotentialZombieWarning warning message?

[Amber "Hawkie" Brown]

> On 14 Dec 2015, at 22:52, pisymbol .  wrote:
> 
> Hi:
> 
> I'd like to adopt Twisted for a current project I'm coding up. I'm on
> CentOS 6.7 x86-64 using python v2.6 and the stock
> python-twisted-8.2.0-3.1 package built for this release.

...

> Is there anyway to get rid of this message? I realize I'm using an
> older release of twisted but I can't upgrade to the latest without
> incurring the cost of installing an python v2.7 or greater.

Hi,

Python 2.6 has been EOL for years and Twisted 8.2.0 is nearly seven years old. 
We can't really help with things that old (many, many issues have since been 
fixed, so remembering what's a bug that's been squashed and what's a platform 
bug is nearly impossible), but upgrading to Twisted 15.4 (the last release with 
Python 2.6 support, and only 4 or so months old) may help.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] When's the next release?

[Amber "Hawkie" Brown]

Hi!

Since a release went out just the other week, I'd say January at the earliest. 
Every 2-3 months is the schedule that seems to balance getting things out there 
with the burden of downstream & users having to handle updates.

- Amber

> On 14 Dec 2015, at 20:16, Jonathan Lange  wrote:
> 
> Hello!
> 
> I've just landed a fix to #4811, which ought to make it possible to use trial 
> with regular standard library unittests that have expected failures & 
> unexpected successes.
> 
> I'm very keen to start using that in my code base, and the easiest way for me 
> to do that is for there to be an official release of Twisted. When might one 
> expect the next release to take place?
> 
> Thanks,
> jml
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Python 2.7 on CentOS 6 (was: PotentialZombieWarning warning message?)

[Amber "Hawkie" Brown]

> On 15 Dec 2015, at 08:43, Glyph Lefkowitz  wrote:
> 
>>> But again: Python 2.6 is unsupported by the upstream Python developers.  You
>>> really should not be using it, since it won't receive security updates (of
>>> course, Red Hat and transitively CentOS claim to "support" these packages,
>>> but if upstream is refusing patches at this point, it's not clear where that
>>> support will come from).
>> 
>> As you can imagine, this boils down to politics.
> 
> I understand that things like this often do, which is exactly why I want to 
> make it clear that we (speaking in terms of the broader Python community now, 
> not just Twisted) are trying to push people towards more recent versions just 
> because they're more fun or more aesthetically pleasant, but because there 
> are very real risks associated with being on unsupported ancient versions of 
> things.  It pains me not to be supporting a configuration that some users 
> want, but there is a line where "conservative about change" becomes 
> "negligent about maintenance" and python 2.6 crossed it a little over two 
> years ago :-).

There is a solution to this, and Nick Coghlan has mentioned it to me many times 
-- Software Collections for RHEL and CentOS. Software Collections is RH's 
answer to "new software" on "stable distributions" --  SCLs operate 
side-by-side with system packages, so it won't break anything. Since you're a 
CentOS 6.7 user, the standard SCL should work (it's 6.5+).

You can find the Python 2.7 SCL at 
https://www.softwarecollections.org/en/scls/rhscl/python27/, and CentOS 
publishes instructions on using them on 
https://wiki.centos.org/AdditionalResources/Repositories/SCL . This might solve 
your problem of being restrained to CentOS 6, but Python 2.6 being EOL'd 
everywhere but it.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] asynchronous response

[Amber "Hawkie" Brown]

> On 17 Dec 2015, at 08:11, Kevin Mcintyre  wrote:
> 
> Hey - I'm confused, so nothing new :) ...but I'm running at this example and 
> I'm scratching my head.
> 
> http://twistedmatrix.com/documents/current/web/howto/web-in-60/asynchronous-deferred.html
> 
> I would've thought 2 requests could be served simultaneously, but when I fire 
> off 2 requests the first received gets it's response after 5 seconds, while 
> the second response takes 10 seconds.
> 
> I think I understand what's happening, but I don't know why...and I would 
> love an example where the subsequent request doesn't have to wait for the 
> first request to finish.
> 
> Thanks,
> Kevin


I've ran into this before --  browsers sometimes rate-limit requests, and won't 
actually send the second request until the first is done, over the same 
connection, rather than making a second TCP connection -- try using cURL or 
wget, which has no such limitation, and see if it works any better.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [BACKWARDS INCOMPATIBLE] Moving Twisted to PEP-3333

[Amber "Hawkie" Brown]

Hi everyone!

We've been attempting to port twisted.web.wsgi to Python 3, as of recent. The 
existence of PEP- makes this easier, but due to our backwards compatibility 
policy, implementing stricter checks to make sure t.w.wsgi-using applications 
are actually PEP- may be a change which cannot be easily done.

The patch we have currently, which is based on work by jMyles (of Hendrix), 
tirelessly worked on allennap (of Canonical MAAS), and sheparded along by the 
wonderful Adi (our other Twisted Fellow), is in very good shape, bringing 
Twisted's WSGI support to be compliant with PEP-. PEP- is much stricter 
on bytes/Unicode, and the patch introduces some further type checking that the 
original PEP-333 describes as a must, even though we did not check this before.

This branch cannot currently be merged because of backwards compatibility 
issues -- the spirit of our Compatibility Policy is that 'apps keep working', 
and sufficiently Unicode unclean WSGI applications may break due to it, even 
though PEP-333 is very explicit in saying that "HTTP does not directly support 
Unicode, and neither does this interface".

So, I am looking to get a compat exception for this -- WSGI is very explicit in 
its types, and any misbehaving applications are violating the specification 
grossly enough for there to possibly not need a compat exception -- but going 
through this way may catch the attention of anyone with a potentially 
misbehaving application and fix it before Twisted 16.0, when I expect this will 
be merged.

The ticket is https://twistedmatrix.com/trac/ticket/7993, and the branch you 
should test against is linked at the top. The compatibility policy will allow a 
week before we move to merge the ticket, although we may have some changes to 
the branch to make warnings turn into errors, if we are breaking backwards 
compat, so please ensure no exceptions *or warnings* are produced by your code.

Thanks,

- Amber
Twisted Fellow, RM, Python 3 Overlord


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [(maybe) BACKWARDS INCOMPATIBLE] Moving Twisted to PEP-3333

[Amber "Hawkie" Brown]

> On 22 Dec 2015, at 14:27, Amber Hawkie Brown  
> wrote:
> 
> Hi everyone!
> 
> We've been attempting to port twisted.web.wsgi to Python 3, as of recent. The 
> existence of PEP- makes this easier, but due to our backwards 
> compatibility policy, implementing stricter checks to make sure 
> t.w.wsgi-using applications are actually PEP- may be a change which 
> cannot be easily done.
> 
> The patch we have currently, which is based on work by jMyles (of Hendrix), 
> tirelessly worked on allennap (of Canonical MAAS), and sheparded along by the 
> wonderful Adi (our other Twisted Fellow), is in very good shape, bringing 
> Twisted's WSGI support to be compliant with PEP-. PEP- is much 
> stricter on bytes/Unicode, and the patch introduces some further type 
> checking that the original PEP-333 describes as a must, even though we did 
> not check this before.
> 
> This branch cannot currently be merged because of backwards compatibility 
> issues -- the spirit of our Compatibility Policy is that 'apps keep working', 
> and sufficiently Unicode unclean WSGI applications may break due to it, even 
> though PEP-333 is very explicit in saying that "HTTP does not directly 
> support Unicode, and neither does this interface".
> 
> So, I am looking to get a compat exception for this -- WSGI is very explicit 
> in its types, and any misbehaving applications are violating the 
> specification grossly enough for there to possibly not need a compat 
> exception -- but going through this way may catch the attention of anyone 
> with a potentially misbehaving application and fix it before Twisted 16.0, 
> when I expect this will be merged.
> 
> The ticket is https://twistedmatrix.com/trac/ticket/7993, and the branch you 
> should test against is linked at the top. The compatibility policy will allow 
> a week before we move to merge the ticket, although we may have some changes 
> to the branch to make warnings turn into errors, if we are breaking backwards 
> compat, so please ensure no exceptions *or warnings* are produced by your 
> code.
> 
> Thanks,
> 
> - Amber
> Twisted Fellow, RM, Python 3 Overlord
> ___
> Twisted-web mailing list
> twisted-...@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web

Hi everyone!

So, with further looking with Tom Prince, it appears that my backwards compat 
fears in regards to Unicode were from my older remembering of the branch, 
allenap and Adi have made it so that it raises a warning on Python 2 if you're 
not Unicode/bytes clean, as well as introducing hard-checks on Python 3, where 
it is reasonable to do so.

So, this should mean that all your Python 2 WSGI apps should keep working, even 
if they're not Unicode clean, but I am still wanting to go through the 
exception process to give users of Twisted's WSGI support a chance to raise any 
problems that they may have with the PEP--compatible code, as unlikely as 
they are to be.

I'd like to say thanks again to allenap and Adi's herculean efforts on this 
branch :)

- Amber



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] twisted-python on OS X 10.11 conch does not install

[Amber "Hawkie" Brown]

> On 30 Dec 2015, at 22:10, Adi Roiban  wrote:
> 
> On 30 December 2015 at 15:47, Guglielmo Pasa  
> wrote:
> Hi,
> I’m trying to get twisted installed on OS X 10.11 with virtualenv and 
> python3.5. All dependencies are satisfied.
> It seems to install correctly and it seems that OpenSSL is working pretty 
> well with it.
> 
> But when I try to load
> 
> import Crypto
> import twisted.conch.ssh.transport
> 
> I get
> 
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named ‘twisted.conch'
> 
> on inspection, in the folder site-packages/twisted there is no conch folder.
> 
> 
> I tried to build twisted from source and conch doesn’t seem to build either
> 
> What can I do to solve this?
> 
> Use Python 2.7 :)
> 
> Conch.ssh was not ported to Python 3

Yet ;)

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] operations: baby steps. buildbot move?

[Amber "Hawkie" Brown]

> On 1 Feb 2016, at 08:46, Glyph Lefkowitz  wrote:
> 
> So at some point in the coming week I'd like to just move exactly the version 
> of the Buildmaster we're running right now to a new cloud host on Rackspace; 
> probably the smallest one that comes with an SSD.

Sounds good. The 2GB General Purpose that I use for the buildbots is plenty 
fast, and has enough RAM that we don't have to care (although I think RAX is 
smart enough that we can start at 1GB and move up to 2GB if needed?).

> Hawkowl is in the process of upgrading us to Buildbot 9 which will be 
> wonderful when it happens, but I want to be clear that this effort is wholly 
> independent from that and neither depends on the other :-).

Yep, Nine is separate.

> 
> It looks to me like the thing I need to do is 'fab config.production 
> buildbot.stop; fab config.production buildbot.dump', then make the relevant 
> DNS change.  At this point I think I need to add a new environment to 
> ENVIRONMENTS and do 'fab config.buildbot buildbot.dump'.  It's not obvious to 
> me how to have two hosts present in 'config.production' but if somebody knows 
> this please let me know.

I think "config.production" is a bit of a eh name to have after, we should 
change it if we have more machines. Eg. config.prod-dornkirk, or whatever. Then 
we just need to write what goes where.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Compatibility issues with Twisted and OpenSSL 1.0.2f

[Amber "Hawkie" Brown]

Hi everyone,

There's a known issue with Twisted + PyOpenSSL>=0.13 using OpenSSL version 
1.0.2f. Please note, this only potentially affects you if:

- You use Windows or OS X -- Cryptography 1.2.2's wheels have a bundled 1.0.2f.
OR
- You use a Linux or FreeBSD distribution which has OpenSSL 1.0.2f. If you are 
using a released distribution of Ubuntu or Debian, you most likely have a 
*patched* (so, still secure) past version (like Ubuntu 15.10, which has a 
patched 1.0.2d). If you are using Fedora 23, you may have 1.0.2f. You can check 
by running "openssl version".

There is also an unrelated issue with CFFI that causes Cryptography 1.2 wheels 
for Windows/OS X to cause CPython to crash on interpreter shutdown.

The current highest working Cryptography version that causes a test suite pass 
is 1.2.2 on Linux with OpenSSL versions other than 1.0.2f, 1.1.2 on Windows & 
OS X without an unreleased CFFI patch, and 1.2.1 once the CFFI patch is 
released. Our Windows and OS X builders have their Cryptography dependencies 
pinned to 1.1.2 until these problems are solved.

Please note, this doesn't mean your applications may or may not work in 
practice with OpenSSL 1.0.2f! It just means the test suite does not pass, so we 
can't be absolutely sure that 1.0.2f will not cause problems for you. The 
latest patched versions of OpenSSL are strongly recommended from a security 
standpoint.

The relevant issues are:

- Make tests pass on 1.0.2f (Twisted, 
https://twistedmatrix.com/trac/ticket/8189)
- Crash during interpreter shutdown when using static callbacks (CFFI, 
https://bitbucket.org/cffi/cffi/issues/246/crash-during-interpreter-shutdown-when)

Regards,

Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.0pre1 Announcement

[Amber "Hawkie" Brown]

Hi everyone, it's time for another Twisted release!

Twisted 16.0 brings some important changes, and some nice-to-haves as well. The 
major things are:

- TLS endpoints have arrived! They're like the old `ssl:` endpoints, but 
support faster IPv4/IPv6 connections (using HostnameEndpoint) and always do 
hostname verification.
- Conch now uses Cryptography instead of PyCrypto for underlying cryptographic 
operations. This means it'll work much better on PyPy!
- Headers objects (notably used by t.web.server.Request) now support Unicode 
for the vast majority of cases, encoding keys to ISO-8859-1 and values to UTF-8.
- WSGI support and AMP have been ported to Python 3, along with a handful of 
other modules.
- More shedding of the past, with the GTK+ 1 reactor being removed.
- Over 45 tickets have been closed.

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.0.0pre1/) to get the prerelease 
tarballs and the full NEWS file.

Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Thanks! <3

- Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted + OpenSSL 1.0.2f issues resolved

[Amber "Hawkie" Brown]

Hi everyone,

Since Tristan Seligmann has fixed https://twistedmatrix.com/trac/ticket/8189 , 
and the CFFI crash-on-shutdown bugs have been resolved upstream, Twisted is now 
fully compatible with OpenSSL 1.0.2f as included in Cryptography 1.2.2, and as 
included in distributions that have been updated.

This fix is in Twisted trunk, but did not make it into Twisted 16.0. Twisted 
16.1 will include the fix.

Thanks to Tristan and Glyph (the reviewer) for getting this issue fixed.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.0.0 Prerelease 2 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

A few issues were identified in Twisted 16.0.0pre1 by the Canonical MAAS team, 
related to the twisted.conch.ssh.keys module missing some dependencies when 
installed on Python 3.

These issues have been fixed and are in Twisted 16.0.0pre2. You can find it and 
the NEWS file at https://twistedmatrix.com/Releases/pre/16.0.0pre2/ .

If no further issues are identified, Twisted 16.0 will be released this week.

- Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.0.0 Prerelease 3 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

exarkun spotted a regression in the 16.0.0 prereleases, where calling 
endpoints' serverWithString with a SSL strports description and an empty chain 
file would give an unhelpful error message.

These issues have been fixed and are in Twisted 16.0.0pre3. You can find it and 
the NEWS file at https://twistedmatrix.com/Releases/pre/16.0.0pre3/ .

If no further issues are identified, Twisted 16.0 will be released this week 
(for real!).

- Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.0 Released

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.0!

Twisted 16.0 brings some important changes, and some nice-to-haves as well. The 
major things are:

- TLS endpoints have arrived! They're like the old `ssl:` endpoints, but 
support faster IPv4/IPv6 connections (using HostnameEndpoint) and always do 
hostname verification.
- Conch now uses Cryptography instead of PyCrypto for underlying cryptographic 
operations. This means it'll work much better on PyPy!
- Headers objects (notably used by t.web.server.Request) now support Unicode 
for the vast majority of cases, encoding keys to ISO-8859-1 and values to UTF-8.
- WSGI support and AMP have been ported to Python 3, along with a handful of 
other modules.
- More shedding of the past, with the GTK+ 1 reactor being removed.
- Over 45 tickets have been closed since 15.5.

For more information, check the NEWS file (link provided below).

You can find the downloads at  (or 
alternatively ). The NEWS file is 
also available at .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,

Amber Brown (HawkOwl)
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.1.0 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

Another Twisted release is upon us -- this one is small, but has some nice to 
haves. In this release is:

- twisted.application.internet.ClientService, a service that maintains a 
persistent outgoing endpoint-based connection -- a replacement for 
ReconnectingClientFactory that uses modern APIs;
- A large (77% on one benchmark) performance improvement when using 
twisted.web's client on PyPy;
- A few conch modules have been ported, in preparation for further porting of 
the SSH functionality;
- Full support for OpenSSL 1.0.2f and above;
- t.web.http.Request.addCookie now accepts Unicode and bytes keys/values;
- `twistd manhole` no longer uses a hard-coded SSH host key, and will generate 
one for you on the fly (this adds a 'appdirs' PyPI dependency, installing with 
[conch] will add it automatically);
- Over eighteen tickets overall closed since 16.0.

As usual, you can get the NEWS file at 
https://twistedmatrix.com/Releases/pre/16.1.0pre1/NEWS.txt and download the 
tarball from https://twistedmatrix.com/Releases/pre/16.1.0pre1/.

Please test this release with your applications, and let me know if all goes 
smoothly. If there's no reported issues, the release will occur in roughly a 
week.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.1 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.1!

This release is hot off the heels of 16.0 released last month, including some 
nice little tidbits. The highlights include:

- twisted.application.internet.ClientService, a service that maintains a 
persistent outgoing endpoint-based connection -- a replacement for 
ReconnectingClientFactory that uses modern APIs;
- A large (77% on one benchmark) performance improvement when using 
twisted.web's client on PyPy;
- A few conch modules have been ported to Python 3, in preparation for further 
porting of the SSH functionality;
- Full support for OpenSSL 1.0.2f and above;
- t.web.http.Request.addCookie now accepts Unicode and bytes keys/values;
- `twistd manhole` no longer uses a hard-coded SSH host key, and will generate 
one for you on the fly (this adds a 'appdirs' PyPI dependency, installing with 
[conch] will add it automatically);
- Over eighteen tickets overall closed since 16.0.

For more information, check the NEWS file (link provided below).

You can find the downloads at  (or 
alternatively ). The NEWS file is 
also available at .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.1.1 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

I'd like to announce a prerelease of the upcoming Twisted 16.1.1, a patch 
release for Twisted 16.1. This fixes a regression in twisted.web where requests 
would not be logged.

The tarball and NEWS file can be found at 
https://twistedmatrix.com/Releases/pre/16.1.1pre1/ . Please test this release 
with your software.

If no issues are found, it will be released in a day or two.

Amber Brown
Twisted Release Manager


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.1.1 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.1.1!

This is a small bugfix release in the 16.1 series, fixing a bug where `twistd 
web` would not output access logs.

For more information, check the NEWS file (link provided below).

You can find the downloads at  (or 
alternatively ). The NEWS file is 
also available at .

Twisted Regards,
Amber Brown


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Twisted 16.1 Release Announcement

[Amber "Hawkie" Brown]

> On 12 Apr 2016, at 21:17, anatoly techtonik  wrote:
> 
> Hi,
> 
> Are there any plans to get back 32-bit wheels for Twisted?
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Hi,

Yes, sometime, when either Glyph or I have the moment to do builder work and 
get the needed stuff installed on the builder. They will be Windows 7-compiled 
32bit wheels.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Changes to Twisted's Trac (GitHub Authentication)

[Amber "Hawkie" Brown]

Hi everyone,

If you've ever had your password eaten by our Trac instance, had your comment 
rejected by spambayes, or seen the amount of effort it takes removing random 
nulls from our htpasswd files, rejoice! With 
https://github.com/twisted-infra/braid/pull/192 , we are moving our Trac 
instance to log in using GitHub OAuth. This should mean we solve the issue of 
keeping passwords (making you and us more secure), being able to turn off the 
spam filter (as we don't have anonymous ticket submittal, and github is better 
at catching spammers than we are), and hopefully cause less ongoing issues with 
passwords suddenly not working.

What this means for you is that your username and password will no longer work 
for logging into our Trac, you will need to authorise your GitHub login to 
access it. This means that you may have another username, please contact me 
privately and I will see what I can do about migrating any ticket histories 
over, if you feel like it is needed.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [MIGRATION COMPLETE] Changes to Twisted's Trac (GitHub Authentication)

[Amber "Hawkie" Brown]

I would like to note that this migration has now finished, and you can now log 
in via GitHub. Legacy logins have been disabled, and previous admin accounts 
(except for a current handful) have been revoked in the name of minimising our 
security surface; if you once had access to our Trac and would like to still 
use it, please let me know what your GitHub user account is, and I can set 
those permissions back up.

- Amber

> On 27 Apr 2016, at 19:13, Amber Hawkie Brown  
> wrote:
> 
> Hi everyone,
> 
> If you've ever had your password eaten by our Trac instance, had your comment 
> rejected by spambayes, or seen the amount of effort it takes removing random 
> nulls from our htpasswd files, rejoice! With 
> https://github.com/twisted-infra/braid/pull/192 , we are moving our Trac 
> instance to log in using GitHub OAuth. This should mean we solve the issue of 
> keeping passwords (making you and us more secure), being able to turn off the 
> spam filter (as we don't have anonymous ticket submittal, and github is 
> better at catching spammers than we are), and hopefully cause less ongoing 
> issues with passwords suddenly not working.
> 
> What this means for you is that your username and password will no longer 
> work for logging into our Trac, you will need to authorise your GitHub login 
> to access it. This means that you may have another username, please contact 
> me privately and I will see what I can do about migrating any ticket 
> histories over, if you feel like it is needed.
> 
> - Amber
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.2.0pre1 Release Announcement

[Amber "Hawkie" Brown]

Hi everyone! Time for another Twisted prerelease!

Our release cadence stays steady, and this prerelease should bring some new 
nice features! The highlights include:

- twisted.protocols.haproxy.proxyEndpoint, a wrapper endpoint that gives some 
extra information to the wrapped protocols passed by haproxy;
- Migration of twistd and other twisted.application.app users to the new 
logging system (twisted.logger);
- Porting of parts of Twisted Names' server to Python 3;
- The removal of the very old MSN client code and the deprecation of the 
unmaintained ICQ/OSCAR client code;
- More cleanups in Conch in preparation for a Python 3 port and cleanups in 
HTTP code in preparation for HTTP/2 support;
- Over thirty tickets overall closed since 16.1.

For more information, check the NEWS file (link provided below).

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.2.0pre1/) to get the prerelease 
tarballs and the full NEWS file.

Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Twisted Regards,
Amber Brown (HawkOwl)



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [INFRASTRUCTURE OUTAGE] Moving from SVN to Git

[Amber "Hawkie" Brown]

Hi everyone!

It's finally time to pull the trigger on this.

Twisted's Trac may be down intermittently in the next few hours as I do the 
migration.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [ALL OK] [INFRASTRUCTURE OUTAGE] Moving from SVN to Git

[Amber "Hawkie" Brown]

Hi everyone!

Twisted infra is now back up and kicking, and we've moved to 
https://github.com/twisted/twisted as our "authoritative" mirror.

- Amber

> On 10 May 2016, at 18:16, Amber Hawkie Brown  
> wrote:
> 
> Hi everyone!
> 
> It's finally time to pull the trigger on this.
> 
> Twisted's Trac may be down intermittently in the next few hours as I do the 
> migration.
> 
> - Amber
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [INFRASTRUCTURE OUTAGE] Migration of Buildbot to new hardware

[Amber "Hawkie" Brown]

Hi everyone,

Keeping the infrastructure updates coming! I'm going to be moving the Buildbot 
to new hardware, so it may be down for today, plus however long DNS takes to 
propagate. This should only affect Twisted committers running tests on the 
builder infrastructure; Trac, docs, and everything else will remain online.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [INCOMPATIBLE CHANGE] Removal of twisted.manhole and twisted.spread.ui

[Amber "Hawkie" Brown]

As part of some spring cleaning, I'm removing two of the largest sections of 
unmaintained, undocumented, and mostly untested code in Twisted. These are 
twisted.manhole (not twisted.conch.manhole, which is over SSH/telnet; 
twisted.manhole is over PB) and twisted.spread.ui (a GTK interface + some other 
things that are similar in purpose, which also depends on twisted.manhole). 
They are both broken and not very useful in their current form; and any 
improvements would require an almost complete rewrite, meaning that there's 
little to no chance that they are worth keeping.

As per the compatibility policy, these two branches are available for you to 
test your applications with:

- https://twistedmatrix.com/trac/ticket/8329 -- removing twisted.spread.ui
- https://twistedmatrix.com/trac/ticket/8330 -- removing twisted.manhole

The git branches are available on the Trac links. They will be available for a 
week from now before the minimum merge time, as per the policy, for you to test 
your applications.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [ALL IS WELL] [INFRASTRUCTURE OUTAGE] Migration of Buildbot to new hardware

[Amber "Hawkie" Brown]

Hi everyone,

The BuildBot migration is now complete.

- Amber

> On 11 May 2016, at 16:28, Amber Hawkie Brown  
> wrote:
> 
> Hi everyone,
> 
> Keeping the infrastructure updates coming! I'm going to be moving the 
> Buildbot to new hardware, so it may be down for today, plus however long DNS 
> takes to propagate. This should only affect Twisted committers running tests 
> on the builder infrastructure; Trac, docs, and everything else will remain 
> online.
> 
> - Amber
> ___
> Twisted-web mailing list
> twisted-...@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.2 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.2!

Just in time for PyCon US, this release brings a few headlining features (like 
the haproxy endpoint) and the continuation of the modernisation of the 
codebase. More Python 3, less deprecated code, what's not to like?

- twisted.protocols.haproxy.proxyEndpoint, a wrapper endpoint that gives some 
extra information to the wrapped protocols passed by haproxy;
- Migration of twistd and other twisted.application.app users to the new 
logging system (twisted.logger);
- Porting of parts of Twisted Names' server to Python 3;
- The removal of the very old MSN client code and the deprecation of the 
unmaintained ICQ/OSCAR client code;
- More cleanups in Conch in preparation for a Python 3 port and cleanups in 
HTTP code in preparation for HTTP/2 support;
- Over thirty tickets overall closed since 16.1.

For more information, check the NEWS file (link provided below).

You can find the downloads at  (or 
alternatively ). The NEWS file is 
also available at .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 06:12, Glyph  wrote:
> 
> It is therefore tempting to map it into GitHub via labels and webhooks and 
> bot workflows.  However, I think a better mapping would be this:
> 
>   • Proposing: Just open a pull request.  Any open pull request should be 
> treated as part of the queue.
>   • Accepting: A committer pushes the big green button; this
>   • Reviewing: This is the potentially slightly odd part.  I believe a 
> review that doesn't result in acceptance should close the PR.  We need to be 
> careful to always include some text that explains that closing a PR does not 
> mean that the change is rejected, just that the submitter must re-submit.  
> Initially this would just mean opening a new PR, but Mark Williams is working 
> on a bot to re-open pull requests when a submitter posts a "please review" 
> comment: https://github.com/markrwilliams/txghbot
>   • Responding: A submitter can open a new PR, or, once we start running 
> txghbot, reopen their closed PR.
>   • Viewing: 
> https://github.com/twisted/twisted/pulls?utf8=✓&q=is%3Apr+is%3Aopen+-status%3Afailed

I think this is reasonable. I believe txghbot is in a place where we can start 
using it for just that.

> The one thing that this workflow is missing from trac is a convenient way for 
> committers, having eyeballed a patch for any obvious malware, to send it to 
> the buildbots.
> 
> We could also potentially just replace our buildbot build farm with a 
> combination of appveyor and travis-ci; this would remove FreeBSD from our 
> list of supported platforms, as well as eliminating a diversity of kernel 
> integrations.  However, for the stuff that doesn't work in containers (mostly 
> inotify) we could run one builder on non-container-based infrastructure, and 
> for everything else (integrating with different system toolchains) we can 
> test using Docker: https://docs.travis-ci.com/user/docker/.  I am very much 
> on the fence about this, since I don't want to move backwards in terms of our 
> test coverage, but this would accelerate the contribution process so much 
> that it's probably worth discussing.

I don't think that this will do us any good. Having travis/appveyor to be a 
first line of review (giving a quick "builds fail/builds probably pass) so that 
contributors get an immediate "does this have a chance of being merged" is a 
good thing; but there is certainly value in having the various different 
platforms. All we need is a bit more tooling around it (and I think txghbot is 
a good starting place for that).

We also need to look into some extra tooling around tox; mainly around the 
ratcheting quality checkers -- some form of fetching the latest build from 
buildbot and downloading it locally to compare, or something.

> 10 years ago or so, we would routinely discover kernel bugs in our 
> integration test harness and they would be different on different platforms.  
> But today's platform realities are considerably less harsh, since there are a 
> lot more entities in the ecosystem that have taken responsibility for testing 
> that layer of the stack; I couldn't find anything since 2008 or so where we 
> really saw a difference between Fedora and Ubuntu at the kernel level, for 
> example.

The issue in 2016 is not actually the kernel; but OpenSSL and OpenSSH, among 
other system libraries. Every new version of Fedora has been red on the 
buildbots for this reason; OpenSSL changed, and we needed to fix our use of it. 
Worth also noting is that Travis is so horrendously behind in all things 
Python+Ubuntu (do they even have a current PyPy yet?) that we're not actually 
testing the platforms people are *using*, which is something I think is 
valuable that the current system gives us.

> 
> Thoughts?
> 
> -glyph

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 14:15, Glyph  wrote:
> 
> Sorry, I guess I wasn't clear.  I know that PRs are presently a potential 
> alternative to a diff, and that we are still using Trac for ticketing.  I 
> want to make it possible to avoid using Trac for ticketing; perhaps switching 
> to github issues entirely.

This is an optimistic idea but one that, unfortunately, won't happen yet ;)

The things GitHub Issues need to be competitive with Trac as it stands:

- Allowing triage by people without write.
- Useful search (GitHub search is kind of abysmal)
- Assigning to non-committers.

Without these things (and quite a few more), it's unlikely that GitHub Issues 
will be as useful to us.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 14:24, Daniel Sank  wrote:
> 
> All,
> 
> > Please do not use squash commits.  See 
> > http://mjg59.dreamwidth.org/42759.html.
> 
> Squashing commits is essential to making useful commit histories. Are you 
> just saying not to use Github's built-in feature which squashes everything 
> into a _single_ commit? If so, note that you can turn that GUI feature off so 
> nobody is tempted to use it. That does leave the question of whether you want 
> people to use merge commits or to rebase their branch on the latest master 
> before merging so that you always get a fast-forward.
> 

The thing is that we don't want fast-forward; fast-forward merging creates 
awful commit histories with no regard to branches, especially for ones like 
Twisted where (near) every commit on trunk needs to be a deployable one, and 
where we may need to revert an entire branch.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 14:23, Glyph  wrote:
> 
> A lot of projects do follow this workflow, and maybe it will be fine for us.  
> The real question is; is FreeBSD support really worth it for the cost to 
> contributors, since that's the only platform we currently support but can't 
> test?

I'm guessing that we have more FreeBSD users than Windows users ;)

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 14:32, Glyph  wrote:
> 
> 
>> On May 21, 2016, at 11:21 PM, Amber Hawkie Brown  
>> wrote:
>> 
>> 
>>> On 22 May 2016, at 14:15, Glyph  wrote:
>>> 
>>> Sorry, I guess I wasn't clear.  I know that PRs are presently a potential 
>>> alternative to a diff, and that we are still using Trac for ticketing.  I 
>>> want to make it possible to avoid using Trac for ticketing; perhaps 
>>> switching to github issues entirely.
>> 
>> This is an optimistic idea but one that, unfortunately, won't happen yet ;)
>> 
>> The things GitHub Issues need to be competitive with Trac as it stands:
>> 
>> - Allowing triage by people without write.
> 
> How are things currently "triaged"?  Do you mean "review"?  If so, I think it 
> would be acceptable to come up with a magic comment for a non-commiter to use 
> to signify that they've fully reviewed a PR.  As it stands, we need 
> committers to "accept" a review by deciding to merge, the only difference 
> here is that it would remain in the review queue until they did so, which I 
> think is acceptable (since if the review isn't accepted, it should have 
> remained in the queue anyway).  We could also have a bot address this 
> edge-case somehow.

Creating a ticket, adding it to the relevant milestone (commit required on 
GitHub), setting the component (which would be a tag on github, requires 
commit)...

> 
>> - Useful search (GitHub search is kind of abysmal)
> 
> I don't see how Trac's is better.

It has a GUI rather than being stringly typed ;)

> 
>> - Assigning to non-committers.
> 
> Honestly I'm not sure that the non-committer assignment part of the workflow 
> is all that useful.  I know I hardly ever look at report 7, and I very much 
> doubt any non-committer does :).  It's not like we're losing information, 
> either; we still have a record of whose fork the PR points to.

I look at report 7 :(

> 
>> Without these things (and quite a few more), it's unlikely that GitHub 
>> Issues will be as useful to us.
> 
> I am curious about the "quite a few more".  There are things which we really 
> need as a critical part of our workflow (primarily: the review queue) and 
> then there are accidents of the way trac works.  Nothing is graven in stone 
> here :).
> 

I guess there's a lot of things that are an accident of trac, but the things 
above are useful.

> -glyph



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

> On 22 May 2016, at 15:23, Glyph  wrote:
> 
> 
>> On May 22, 2016, at 12:15 AM, Hynek Schlawack  wrote:
>> 
>> Ah finally a fine bike shedding thread that gets everyone involved. ;)
> 
> OKAY NOW THAT I'VE GOT YOU ALL HERE LET'S TALK ABOUT 
> https://twistedmatrix.com/trac/ticket/288
> 
> *slams a metal grating shut over the only exit from the mailing list*
> 
JEAN-CHA^W^W GLYPH YOU FOOL, YOU'VE LOCKED US ALL IN!

> -glyph


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] overview: new review queue venue

[Amber "Hawkie" Brown]

Mark has been working on a bot which would reopen it with a comment: 
https://github.com/markrwilliams/txghbot

- Amber

> On 23 May 2016, at 12:56, Craig Rodrigues  wrote:
> 
> I submitted this PR, which is now closed: 
> https://github.com/twisted/twisted/pull/62
> 
> I don't want to re-open that PR, but I am using that as an example
> As an example, if I wanted to re-open that, how would I go about doing it?
> 
> I am not an administrator of the Twisted GitHub project, so on that web link,
> there is no option for me to re-open the PR.
> 
> Are you suggesting that I would need to
>-> create a new branch in my repo with new commits
>-> create a new pull request
> 
> ?
> 
> --
> Craig
> 
> On Sun, May 22, 2016 at 9:39 PM, meejah  wrote:
> 
> closing a PR with a nice note explaining, "please re-open when X is
> fixed/changed" scares away a potential contributer I have my doubts as
> to whether they would fix X if you *didn't* close it...)
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Porting PB to python3

[Amber "Hawkie" Brown]

> On 11 Jun 2016, at 03:39, Craig Rodrigues  wrote:
> 
> Hi,
> 
> I reviewed your branch:  
> https://github.com/wrohdewald/twisted/commits/spread-py3-7598/twisted
> 
> In my opinion, that branch has two categories of Python 3 porting:
> 
> Category 1: Minor
>   -> these are "minor" fixos, such as dealing with xrange -> range
> 
> Category 2: Major
>-> you have done a lot of work to deal with bytes versus unicode strings
> 
> I hope you haven't lost interest in this, and are still willing to push 
> forward.
> I would recommend that if you can separate out the minor fixes
> into separate GitHub pull requests and separate Trac tickets, then do that.
> 
> If you see: https://github.com/twisted/twisted/commits/trunk
> 
> you will see I have submitted a lot of pull requests + trac tickets of "minor"
> Python 3 fixes, and those have successfully been reviewed and merged
> by Twisted committers.
> 
> Dealing with bytes versus unicode strings will take longer to review,
> because it is more advanced.  That is why I recommend separating
> out the "minor" fixos if you can.
> 
> The other think I would recommend is if you do periodic merges
> from trunk to your branch, since a lot of new Python 3 fixes have gone into 
> trunk in the past few weeks.
> 
> --
> Craig
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

I've also taken a hack at this whilst I was on the plane; please see 
https://github.com/twisted/twisted/compare/trunk...port-pb-7598 which has some 
minorly different approaches to porting than your branch. There is a few fixes 
to things I hadn't got to, which I'll investigate :)

- Amber



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Upcoming Buildbot Changes (Ubuntu version support)

[Amber "Hawkie" Brown]

Hi everyone,

I'm doing some builder work today; including changing the versions of Ubuntu we 
test on. From next week, our supported Ubuntu platforms will be:

- Ubuntu 12.04 (Python 2.7)
- Ubuntu 14.04 (Python 2.7)
- Ubuntu 16.04 (Python 2.7, Python 3.4, Python 3.5, PyPy (unsupported))

These are all LTS versions right now, and should provide us pretty wide 
coverage of Ubuntus that are widely used.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Upcoming Buildbot Changes (Ubuntu version support)

[Amber "Hawkie" Brown]

> On 12 Jun 2016, at 03:36, Glyph  wrote:
> 
>> On Jun 10, 2016, at 21:35, Amber Hawkie Brown  
>> wrote:
>> 
>> Hi everyone,
>> 
>> I'm doing some builder work today; including changing the versions of Ubuntu 
>> we test on. From next week, our supported Ubuntu platforms will be:
>> 
>> - Ubuntu 12.04 (Python 2.7)
>> - Ubuntu 14.04 (Python 2.7)
>> - Ubuntu 16.04 (Python 2.7, Python 3.4, Python 3.5, PyPy (unsupported))

(correction, 16.04 dropped Python 3.4 from the repos, so it will be 2.7, 3.5, 
PyPy on that platform, with 3.4 being covered by Fedora)

> 
> Cool!  Is this going to let us delete any builders? :)

Yes, all of our 15.04 and 15.10 builders can be removed now, which I'll do 
shortly.

> 
>> These are all LTS versions right now, and should provide us pretty wide 
>> coverage of Ubuntus that are widely used.
> 
> Thanks for taking on this maintenance.

:)

> 
> -g
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Porting PB to python3

[Amber "Hawkie" Brown]

> On 13 Jun 2016, at 01:04, Wolfgang Rohdewald  
> wrote:
> 
> Am Freitag, 10. Juni 2016, 12:39:20 CEST schrieb Craig Rodrigues:
>> I hope you haven't lost interest in this, and are still willing to push
>> forward.
> 
> Maybe in autumn. But I rather hope somebody else would continue with this.
> 

I will -- as mentioned, I have a patch that's missing a few things, so I'll 
combine them and keep pushing this forward :)

- Amber

> --
> Wolfgang
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.0 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hello everyone! It's time for yet another Twisted release -- although not long 
after the last, we have had a bunch of good changes from the PyCon sprints, and 
some long-awaited work has landed!

- The Git migration has happened, so we've updated our development 
documentation to match. We're now trialling accepting pull requests at 
github.com/twisted/twisted, so if you've ever wanted an excuse to contribute, 
now's the chance!
- In our steady shedding of baggage, twisted.spread.ui, twisted.manhole (not to 
be confused with twisted.conch.manhole!), and a bunch of old and deprecated 
stuff from twisted.python.reflect and twisted.protocols.sip have been removed.
- twisted.web's HTTP server now handles pipelined requests better -- it used to 
try and process them in parallel, but this was fraught with problems and now it 
processes them in series, which is less surprising to code that expects the 
Request's transport to not be buffered (e.g. WebSockets).
- Twisted now has HTTP/2 support in its web server! This is currently not 
available by default -- you will need to install hyper-h2, which is available 
in the [h2] setuptools extras. If you want to play around with it, see the 
install link below. Upon release, you will be able to simply "pip install 
twisted[http2]".
- 53 tickets closed overall, including cleanups that move us closer to a total 
Python 3 port.

For more information, check the NEWS file (link provided below).

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.3.0pre1/) to get the prerelease 
tarballs and the full NEWS file. If you want to install it right away, run:

pip install 
https://twistedmatrix.com/Releases/pre/16.3.0pre1/Twisted-16.3.0rc1.tar.bz2

If you would like to try out the newly-landed HTTP/2 support, run:

pip install -U 
https://twistedmatrix.com/Releases/pre/16.3.0pre1/Twisted-16.3.0rc1.tar.bz2#egg=Twisted[http2,tls]

This will download the new HTTP/2 dependencies and the TLS requirements as well.

Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Twisted Regards,
Amber Brown (HawkOwl)



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] two minor things

[Amber "Hawkie" Brown]

> On 22 Jun 2016, at 18:51, Tristan Seligmann  wrote:
> 
> On Wed, 22 Jun 2016 at 10:05 Glyph  wrote:
> 
> If we are going to change this, I would really appreciate it if someone in 
> favor of the change would write a script to re-name the literally thousands 
> of outstanding branches to the new convention, so we don't have a random mix. 
>  Luckily git makes this considerably more light weight, since it just changes 
> the name of the pointer and doesn't create new revisions :-).
> 
> I think most of the "outstanding branches" are actually merged, and need to 
> be deleted. So maybe a script to do that first...? (Sorry, I'm not likely to 
> get around to this any time soon)

I might take a stab at this... firstly we want to delete the merged ones, and 
then migrate the rest.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.0 Prerelease 2 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

Here's another prerelease in the 16.3 series -- fixing a 16.2 regression in 
HTTP timeouts not working.

For more information, check the NEWS file (link provided below).

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.3.0pre2/) to get the prerelease 
tarballs and the full NEWS file. If you want to install it right away, run:

   pip install 
https://twistedmatrix.com/Releases/pre/16.3.0pre2/Twisted-16.3.0rc2.tar.bz2

A reminder that if you would like to try out the newly-landed HTTP/2 support, 
run:

   pip install -U 
https://twistedmatrix.com/Releases/pre/16.3.0pre2/Twisted-16.3.0rc2.tar.bz2#egg=Twisted[http2,tls]

This will download the new HTTP/2 dependencies and the TLS requirements as well.

Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.0 Release Announcement

[Amber Hawkie Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.3.0.

The highlights of this release are:

- The Git migration has happened, so we've updated our development 
documentation to match. We're now trialling accepting pull requests at 
github.com/twisted/twisted, so if you've ever wanted an excuse to contribute, 
now's the chance!
- In our steady shedding of baggage, twisted.spread.ui, twisted.manhole (not to 
be confused with twisted.conch.manhole!), and a bunch of old and deprecated 
stuff from twisted.python.reflect and twisted.protocols.sip have been removed.
- twisted.web's HTTP server now handles pipelined requests better -- it used to 
try and process them in parallel, but this was fraught with problems and now it 
processes them in series, which is less surprising to code that expects the 
Request's transport to not be buffered (e.g. WebSockets). There is also a 
bugfix for HTTP timeouts not working in 16.2.
- Twisted now has HTTP/2 support in its web server! This is currently not 
available by default -- you will need to install hyper-h2, which is available 
in the [h2] setuptools extras. If you want to play around with it "pip install 
twisted[h2]" (on Python 2, a bugfix release will make it available on Python 3) 
and add "h2" to your Site's acceptableProtocols.
- 53 tickets closed overall, including cleanups that move us closer to a total 
Python 3 port.

For more information, check the NEWS file (link provided below).

You can find the downloads at  (or 
alternatively ). The NEWS file is 
also available at .

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Twisted 16.3.0 Prerelease 2 Announcement

[Amber "Hawkie" Brown]

Hmm, I have it working fine (Python 2.7/3.5, w/ Cryptography wheels on OS X)...

The default ciphers in Twisted are:

ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS

So I am not sure why it's not picking up 
"TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256" first...

- Amber

> On 10 Jul 2016, at 01:30, Paweł Miech  wrote:
> 
> Thanks for fixing this.
> 
> Did anyone actually manage to make HTTP2 in Twisted work with Google-Chrome? 
> I tried to do this today, and it seems this is surprisingly difficult. It 
> turns out that Chrome requires ALPN and it dropped support for NPN. ALPN is 
> only supported with OpenSSL 1.0.2 or above, which by default is not available 
> in most systems. This is discussed here. I tried setting up docker image with 
> Ubuntu 16.04 that has required version of OpenSSL, but it seems that Chrome 
> still doesn't like it. It returns ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY 
> error and fails to load page. Looking up this error I found out this might be 
> happening because some TSL ciphers are blacklisted in HTTP2, there is nice 
> answer about this here it links to this part of HTTP2 spec 
> https://http2.github.io/http2-spec/#rfc.section.9.2.2
> 
> My question is: should user deal with this kind of stuff themselves? If some 
> ciphers are blacklisted in HTTP2 shouldn't this be handled somewhere in 
> Twisted? E.g. perhaps there should be some Http2SSLContextFactory? If you'd 
> like to reproduce this I did some sample repo here: 
> https://github.com/pawelmhm/sf-books-http2 it contains dockerfile that builds 
> from Ubuntu 16.04 and runs simple Twisted HTTP 2 resource.
> 
> 2016-07-04 13:48 GMT+02:00 Craig Rodrigues :
> On Sun, Jul 3, 2016 at 3:15 AM, Paweł Miech  wrote:
> HTTP2 support sounds really exciting.
> 
> > Please let me know if you have any issues, as well as if you don't! If 
> > everything works well, that's a good thing for me to know :)
> 
> I played around with this today and found out that the command you recommend:
> 
> >  pip install -U 
> > https://twistedmatrix.com/Releases/pre/16.3.0pre2/Twisted-16.3.0rc2.tar.bz2#egg=Twisted[http2,tls]
> 
> does NOT install dependencies when ran on Python 3, I had to manually install 
> h2 to HTTP2 support to work. It works ok on Python 2. My installation logs on 
> Python 3.4 look like this:
> 
> 
> I think I've fixed that in trunk with this:
> 
> https://github.com/twisted/twisted/pull/287
> 
> --
> Craig
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
> 
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] IProtocolWithReactor, or passing the reactor though to protocols

[Amber "Hawkie" Brown]

(disclaimer: this is after several hours on an aeroplane, this may all be 
nonsense)

So, I'm currently looking into adding some features to twisted.web -- something 
that historically hasn't had the best support for pluggable reactors, and which 
requires levels and levels of monkeypatching (see the top level of 
https://github.com/twisted/twisted/compare/trunk...deferreds-in-resrender-3711 
). So, I was thinking, what if we made a new way for things to get their 
reactor, rather than extending all these concrete implementations everywhere?

Currently, you'd pass a reactor instance through to protocols by making the 
factory understand it, and the protocol calling self.factory._reactor or 
whatever. I never thought this was a supremely helpful or useful interface -- 
especially for one-shot classes -- so what if instead we made a new 
IProtocol-extending interface, which signals to tcp.Port/etc that the protocol, 
once created, should have a reactor set on it (maybe through some 
"setConnectingReactor" or something). This would mean that the factory doesn't 
know about the reactor in most cases (with things like HTTPFactory doing 
logging as an exception) -- but we could also have an 
IClient/ServerFactoryWithReactor, that Endpoints (which needs to know about the 
reactor, and which reactor it is listening on) can then check for and call a 
similar function, telling the Factory what reactor it is actually running under.

This, I think, would reduce a bunch of duplicate code in __init__s of 
factories, and could be implemented in the base class of Protocol or 
ServerFactory, possibly. What do people think?

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] IProtocolWithReactor, or passing the reactor though to protocols

[Amber "Hawkie" Brown]

> On 15 Jul 2016, at 23:06, Glyph Lefkowitz  wrote:
> 
>> 
>> On Jul 15, 2016, at 6:02 AM, Amber Hawkie Brown  
>> wrote:
>> 
>> (disclaimer: this is after several hours on an aeroplane, this may all be 
>> nonsense)
>> 
>> So, I'm currently looking into adding some features to twisted.web -- 
>> something that historically hasn't had the best support for pluggable 
>> reactors, and which requires levels and levels of monkeypatching (see the 
>> top level of 
>> https://github.com/twisted/twisted/compare/trunk...deferreds-in-resrender-3711
>>  ). So, I was thinking, what if we made a new way for things to get their 
>> reactor, rather than extending all these concrete implementations everywhere?
>> 
>> Currently, you'd pass a reactor instance through to protocols by making the 
>> factory understand it, and the protocol calling self.factory._reactor or 
>> whatever. I never thought this was a supremely helpful or useful interface 
>> -- especially for one-shot classes -- so what if instead we made a new 
>> IProtocol-extending interface, which signals to tcp.Port/etc that the 
>> protocol, once created, should have a reactor set on it (maybe through some 
>> "setConnectingReactor" or something). This would mean that the factory 
>> doesn't know about the reactor in most cases (with things like HTTPFactory 
>> doing logging as an exception) -- but we could also have an 
>> IClient/ServerFactoryWithReactor, that Endpoints (which needs to know about 
>> the reactor, and which reactor it is listening on) can then check for and 
>> call a similar function, telling the Factory what reactor it is actually 
>> running under.
>> 
>> This, I think, would reduce a bunch of duplicate code in __init__s of 
>> factories, and could be implemented in the base class of Protocol or 
>> ServerFactory, possibly. What do people think?
> 
> 
> First off, I think a clearer articulation of the problem would be helpful :). 
>  Is it "I don't want to take parameters in __init__"?  Or "I don't want to 
> have duplicated code to grab the global reactor everywhere, but I still want 
> to grab the global reactor everywhere"?  Is it "most factories don't need the 
> reactor except to hand it to their protocols, therefore they shouldn't have 
> to have code to deal with it at all"?
> 
> I definitely don't think we should address any of these issues with 
> 'setConnectedReactor'.  This is using a side-effect rather than just 
> constructing the object with the things that it needs.  We also shouldn't do 
> it with a base class.  Depending even more on inheritance would be movement 
> in the wrong direction.
> 
> If we want to address the issue of duplicated code in constructors, how about 
> something like a @reactorParameter(name='reactor') decorator, which does the 
> grab-the-current-global-reactor-if-it's-not-passed thing?  A better pattern 
> is 'just pass in the reactor', of course.
> 
> Or, perhaps what you want is this 7-year-old ticket? :) 
> https://twistedmatrix.com/trac/ticket/3205
> 
> -glyph

Yes, that ticket is almost what I want! That is a much better solution for 
Protocols.

However, Factories still need the reactor given, and it seems really silly and 
very hard to explain why you both would need to create a Factory with a 
reference to a reactor, and then call 
reactor.listenTCP/endpoint.connect/listen, also with a reactor. I feel like one 
of these should really be able to tell the other.

This also doesn't fit the problem idnar raised on IRC -- that the reactor 
serving the connections may not be the one that the protocol wants to use, for 
whatever reason (gui reactor and a not gui reactor?) -- I can't say if #3205 
has the same problems, but I believe it does. I guess then that's up to the 
protocol, but I kind of would like if all protocols had one consistent place 
for "this is the reactor I should schedule things on" -- and transport.reactor 
does not seem to be it, because that's still got the problem that idnar has 
raised.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] IProtocolWithReactor, or passing the reactor though to protocols

[Amber "Hawkie" Brown]

> On 18 Jul 2016, at 09:15, Glyph Lefkowitz  wrote:
> 
>> On Jul 16, 2016, at 06:01, Amber Hawkie Brown  
>> wrote:
>> 
>> Yes, that ticket is almost what I want! That is a much better solution for 
>> Protocols.
>> 
>> However, Factories still need the reactor given, and it seems really silly 
>> and very hard to explain why you both would need to create a Factory with a 
>> reference to a reactor, and then call 
>> reactor.listenTCP/endpoint.connect/listen, also with a reactor. I feel like 
>> one of these should really be able to tell the other.
> 
> Which factories need this reference given?  Some need a clock, for e.g. 
> timeouts, but then... that's OK, give them a clock.  The fact that a 
> parameter must sometimes be passed to two different places doesn't mean we 
> shouldn't make it a parameter...

Yes, but it's a very big footgun. If we are using a custom reactor, we must 
pass it at every level of the stack, when the information can easily be got 
from other sources.

> Possibly the problem here is that 'doStart' and 'doStop' ought to receive the 
> reactor passed to them as well.  And maybe something else, too, for that 
> matter, like an address, or an endpoint - that interface has always been a 
> bit annoyingly narrow.  But a concrete use-case would help here.

My use case is making it easier to write things that require the reactor not 
having to be given absolutely everywhere -- it's very very inpenetrable to look 
at every interface and see if it has a reactor parameter.

> 
>> This also doesn't fit the problem idnar raised on IRC -- that the reactor 
>> serving the connections may not be the one that the protocol wants to use, 
>> for whatever reason (gui reactor and a not gui reactor?)
> 
> This use-case doesn't make any sense, because if you want to have a GUI you 
> need to use a GUI reactor for everything; the reference passed is the running 
> reactor.
> 

Different reactors in threads (e.g. gilectomy, STM).

>> -- I can't say if #3205 has the same problems, but I believe it does. I 
>> guess then that's up to the protocol, but I kind of would like if all 
>> protocols had one consistent place for "this is the reactor I should 
>> schedule things on" -- and transport.reactor does not seem to be it, because 
>> that's still got the problem that idnar has raised.
> 
> Where did idnar raise this problem?  I am still not clear on exactly what 
> we're talking about.

IRC, like I mentioned :)

> 
> -glyph
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Twisted tests on public CI

[Amber "Hawkie" Brown]

> On 20 Jul 2016, at 23:36, Glyph Lefkowitz  wrote:
> 
> It seems like the only thing that Buildbot is now covering which this setup 
> is not is alternate kernels, which have not diverged in behavior from 
> Twisted's perspective for 7 or 8 years.  I am starting to wonder if we could 
> get rid of the entire current buildbot environment with all its complicated 
> trust issues and just start over with the parts that we actually want: 
> on-demand, latent FreeBSD and Windows builders, for example.  This is a 
> tricky problem, but if it's the *only* thing we're trying to get buildbot to 
> do it's a lot simpler to start there.
> 
> Someone please correct me if I'm wrong though ;).

That and non-old Ubuntus -- new Fedora/RHEL versions for the past year or two 
have uncovered OpenSSL changes (partially because Fedora uses FIPS mode, and 
things like SSLv3 and MD5 just don't work on them), as well as testing more 
diverse versions (like Ubuntu 12.04, which has an OpenSSL which doesn't support 
NPN/ALPN).

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] close to the finish line on hosted windows testing

[Amber "Hawkie" Brown]

Just a note; I've got both issues fixed on a branch and am just cleaning it up 
for review. Them, I would like to remove the (quite broken) Windows 7 builder 
and just use appveyor.

- Amber

> On 24 Jul 2016, at 21:01, Glyph Lefkowitz  wrote:
> 
> Thanks to Craig and Adi's work, we now have tests sort of working on 
> appveyor.  However, they aren't actually reporting their pass/fail status 
> right now as github statuses, I am assuming because of the persistent 
> failures that were causing noise on unrelated tickets.
> 
> However, it's very close to being a useful builder; there are really only 2 
> remaining issues, not counting turning on the reporting itself.  I've made an 
> umbrella ticket here: https://twistedmatrix.com/trac/ticket/8664 
>  and documented what's wrong with 
> each one.
> 
> So, if you care about Twisted on Windows, fixing the issues documented there 
> should make it much easier for more folks to contribute easily :).
> 
> -glyph
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] INCOMPATIBLE CHANGE: twisted.python.dist renamed to twisted.python._setup

[Amber "Hawkie" Brown]

> On 8 Aug 2016, at 08:15, Craig Rodrigues  wrote:
> 
> 
> 
> On Sun, Aug 7, 2016 at 4:15 PM, Glyph Lefkowitz  > wrote:
> 
>> On Aug 7, 2016, at 4:19 AM, Adi Roiban > > wrote:
>> 
>> Hi,
>> 
>> I would like to remove twisted.python.dist as a public API without following 
>> the 1 year deprecation processes.
>> 
>> The module has a comment which informs people not to use it outside of 
>> Twisted, but I think it should be private module instead.
>> 
>> The ticket is here https://twistedmatrix.com/trac/ticket/8622 
>> 
>> The PR is here https://github.com/twisted/twisted/pull/467 
>> 
>> The branch is here 
>> https://github.com/twisted/twisted/tree/8622-setup-coverage 
>> 
>> 
>> This is part of the setup.py cleanup effort for having most of the setup.py 
>> code outside of setup.py itself so that we can test it as part of the 
>> automated test suite.
>> 
>> twisted.python.dist3 was kept as a private API as it is already used  by 
>> https://github.com/habnabit/twisted-depgraph 
>> 
>> 
>> Please let me know if you are using twisted.python.dist outside of Twisted 
>> and are against this change or if you approve it.
>> 
>> Thanks!
> 
> +1 from me!
> 
> 
> 
> 
> -1 from me.  dist.py probably should have been a private API from the 
> beginning, but it slipped through the cracks.
> However, what has been done is done.  This change seems gratuitous and 
> pointless with
> no benefits to anybody.
> 
> --
> Craig

I believe there's a point to it -- that is, we make it clear what is and what 
isn't user API. It's always said it in the header, but we should codify that 
it's really not user API. Plus it being private means we can make what changes 
we need for future setup.py changes, without deprecating things that nobody but 
us should ever use.

+1 from me.

- Amber



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.1 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

Hi everyone,

I've just uploaded the first prerelease of Twisted 16.3.1, a security & 
critical bug fix release of the 16.3 series. It contains:

- A bugfix for a HTTP/2 edge case,
- Fix for CVE-2008-7317 (generating potentially guessable HTTP session 
identifiers)
- Fix for CVE-2008-7318 (sending secure session cookies over insecured 
connections)
- Fix for CVE-2016-1000111 (http://httpoxy.org/)

You can find the tarball and the full news file for testing at 
https://twistedmatrix.com/Releases/pre/16.3.1pre1/ .

If no issues are found, I will issue a full release by Friday.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.4.0 Prerelease 1 Announcement

[Amber "Hawkie" Brown]

In a rare Twisted release double feature right after 16.3.1, I bring you the 
first prerelease of Twisted 16.4.0.

This is a big release, the first after the Git migration has really kicked in! 
And so, here's what it brings us:

- twist, a new command line tool for running Twisted plugins, similar to twistd 
but with a simpler, cleaner interface.
- A new interface for Protocols, IHandshakeListener, which tells Twisted to 
tell the Protocol when the TLS handshake has been completed.
- async/await support for Deferreds, allowing you to write Python 3.5+ 
coroutines using Twisted
- Trial can be invoked with "python -m twisted.trial".
- 35+ more modules ported to Python 3, and many many cleanups on the way to 
Python 3 on Windows support.
- 240+ closed tickets overall.

For more information, check the NEWS file (link provided below).

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.4.0pre1/ 
) to get the prerelease 
tarballs and the full NEWS file. If you want to install it right away, run:

   pip install 
https://twistedmatrix.com/Releases/pre/16.4.0pre1/Twisted-16.4.0rc1.tar.bz2 


Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.1 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.3.1.

This is a bug fix & security fix release, and is recommended for all users of 
Twisted. The fixes are:

- A bugfix for a HTTP/2 edge case,
- Fix for CVE-2008-7317 (generating potentially guessable HTTP session 
identifiers)
- Fix for CVE-2008-7318 (sending secure session cookies over insecured 
connections)
- Fix for CVE-2016-1000111 (http://httpoxy.org/ )

For more information, check the NEWS file (link provided below).

You can find the downloads at > (or alternatively 
>). The NEWS file is also 
available at >.

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] [BACKWARDS INCOMPATIBILITY] Making twisted.python.dist3 private

[Amber "Hawkie" Brown]

Hi everyone,

I am moving the dist3 from a whitelist to a blacklist, and that requires 
changing the whole module's interface, which shouldn't be public anyway.

You can get the branch here: https://github.com/twisted/twisted/pull/501 , 
it'll be available for a further week.

The only concern for this code was depgraph, which we are now at the point of 
not needing, as we're getting to leaf modules and not core modules.

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Moving under a src directory, or: Sorry But I Broke All Your Pull Requests

[Amber "Hawkie" Brown]

Hi everyone,

I have just merged the branch which puts twisted under a src/ directory. The 
reasons are many (see https://hynek.me/articles/testing-packaging/ for details 
as to why this is a Fantastic Idea), and it will require a bit of care with 
existing branches and pull requests.

Thankfully, glyph has scripted all that your PR should need to do:

python admin/fix-for-src-mv.py

This will move everything under the src/ dir. If you have moved/renamed files 
in your PR, you may need to manually fix the conflicts.

Happy hacking, everyone :)

- Amber


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.3.2 Release Announcement

[Amber "Hawkie" Brown]

On behalf of Twisted Matrix Laboratories, I am honoured to announce the release 
of Twisted 16.3.1.

This is a security fix release, and is recommended for all users of Twisted. 
The fixes contained are:

- Twisted's HTTP server, when operating over TLS, would not cleanly close 
sockets, causing it to build up CLOSE_WAIT sockets until it would eventually 
run out of file descriptors.

For more information, check the NEWS file (link provided below).

You can find the downloads at > (or alternatively 
>). The NEWS file is also 
available at >.

Many thanks to everyone who had a part in this release - the supporters of the 
Twisted Software Foundation, the developers who contributed code as well as 
documentation, and all the people building great things with Twisted!

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Twisted 16.4.0 Prerelease 2 Announcement

[Amber "Hawkie" Brown]

Hi everyone!

I bring you a new Twisted 16.4.0 prerelease, with the following fixes:

- Twisted's HTTP server, when operating over TLS, would not cleanly close 
sockets, causing it to build up CLOSE_WAIT sockets until it would eventually 
run out of file descriptors. (from 16.3.2)
- AMP no longer fails on floats on Python 3.

For more information, check the NEWS file (link provided below).

As usual, it's available for download -- go here 
(https://twistedmatrix.com/Releases/pre/16.4.0pre2/ 
) to get the prerelease 
tarballs and the full NEWS file. If you want to install it right away, run:

   pip install 
https://twistedmatrix.com/Releases/pre/16.4.0pre2/Twisted-16.4.0rc2.tar.bz2 


Please let me know if you have any issues, as well as if you don't! If 
everything works well, that's a good thing for me to know :)

Twisted Regards,
Amber Brown (HawkOwl)


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Please fix the broken buildbots

[Amber "Hawkie" Brown]

So I also investigated and it appeared like the hack I had in 
https://github.com/twisted-infra/braid/blob/master/services/buildbot/master/twisted_factories.py#L368
 to prevent this from occurring disappeared in prod; I think maybe Adi pushed 
up something trying to replicate what it was doing without committing it :)

I've redeployed from master of braid, and it appears to be working now.

- Amber

> On 23 Aug 2016, at 15:43, Mark Williams  wrote:
> 
> Glyph got me all set up so I can work on the Buildbots.  Thanks,
> Glyph!
> 
> I hope to resolve the issue Craig identified soon and will announce
> any progress.  Stay tuned!
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

[Amber "Hawkie" Brown]

The only reason to support Python 3.3 is PyPy3. However, since they now have 
funding to push it to 3.5, and PyPy3 is by no means production ready, I think 
it is reasonable to do this.

I will announce the release after Twisted 16.4 as the final one to support 
Python 3.3, in accordance with our compatibility policy.

- Amber

> On 24 Aug 2016, at 01:27, Mark Williams  wrote:
> 
> On Tue, Aug 23, 2016 at 09:44:16AM -0700, Glyph Lefkowitz wrote:
>> 
>> We can drop support for 3.3 of course, but that's a separate discussion.
> 
> I'm marginally in favor of it.  I appreciate Adi's concern about the
> build infrastructure.  And thanks to the inimitable Donald Stufft,
> it's easy to get a sense of how popular Python 3.3 is among Twisted
> users and whether or not dropping support for it will affect a large
> percentage of them.
> 
> He provided the following BigTable Query to run against the PyPI
> downloads dataset (available at
> https://bigquery.cloud.google.com/dataset/the-psf:pypi?pli=1 ):
> 
> SELECT
>  REGEXP_EXTRACT(details.python, r"^([^\.]+\.[^\.]+)") as python_version,
>  COUNT(*) as downloads,
> FROM
>  TABLE_DATE_RANGE(
>[the-psf:pypi.downloads],
>DATE_ADD(CURRENT_TIMESTAMP(), -31, "day"),
>DATE_ADD(CURRENT_TIMESTAMP(), -1, "day")
>  )
> WHERE file.project = 'twisted'
> GROUP BY python_version
> ORDER BY
>  downloads DESC
> 
> 
> Here're the results:
> 
> python_versiondownloads
> 2.7 446869
> null21959
> 3.5 15204
> 3.4 11245
> 2.6 5060
> 3.3 1060
> 3.2 271
> 3.6 241
> 2.4 5
> 1.17  3
> 2.5   2
> 
> (Donald explained that `null` represents mirrors and caches like
> bandersnatch.)
> 
> It appears that dropping Python 3.3 wouldn't exclude very many of our
> users.
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python