Mailman 3 June 2015 - Twisted

[Twisted-Python] vvangelovski@gmail.com has indicated you're a friend. Accept?
by vvangelovski＠gmail.com June 21, 2015

June 21, 2015

Hi, vvangelovski(a)gmail.com wants to follow you. ****** Is vvangelovski(a)gmail.com you friend? ****** If Yes please follow the link below: http://invites.discovernewwebsites.net/signup_e.html?fullname=Twisted+Gener… If No please follow the link below: http://invites.discovernewwebsites.net/signup_e.html?fullname=Twisted+Gener… Follow the link below to remove yourself from all such emails http://invites.discovernewwebsites.net/uns_inviter.jsp?email=twisted-python…

1 0

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com June 21, 2015

June 21, 2015

1 0

[Twisted-Python] Unsupported buildbots and future supported platforms
by Amber "Hawkie" Brown June 16, 2015

June 16, 2015

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/ste… . 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

3 2

[Twisted-Python] Should the CFFI wrapper and functions for win32 be a separate project?
by Oliver Palmer June 15, 2015

June 15, 2015

As the subject says, could the CFFI wrappers around the win32 functions that Twisted needs be a separate project? This came up briefly in https://twistedmatrix.com/trac/ticket/7889 so I thought I might pose the question to a larger audience. Generally speaking, the idea of making it a separate project to me seems like a logical step in many ways. Since the code is not specific to Twisted keeping it outside of the Twisted project, much like pywin32 is, makes it easier for contributors and consumers alike to reuse or expand on the cffi wrapper in the future. I don't think the objective would be to replace all of pywin32 initially but to provide enough to be usable by the Twisted project. Besides Twisted I know there are some other projects out there that could benefit from making this a separate project. But before taking this approach however I'm wondering if this would be reasonable from Twisted's perspective? ---Oliver

3 2

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com June 14, 2015

June 14, 2015

1 0

[Twisted-Python] Twisted formatting checking in Emacs?
by Jonathan Lange June 13, 2015

June 13, 2015

How can I set up Emacs so it gives me inline warnings of Twisted coding standard violations? I use flycheck <http://www.flycheck.org/> in Emacs for most projects, and rely a lot on it. How can I configure it to use twistedchecker <https://github.com/twisted/twistedchecker> for syntax checks for Twisted instead of its default flake8 & pylint checkers? Thanks, jml

2 3

[Twisted-Python] Twisted logger changes
by Maciej Wasilak June 9, 2015

June 9, 2015

Dear list, I've tried running Twisted 15.2.1 with my old library, and I am getting an exception, that I haven't seen before (with Twisted 14.0.0): File "/usr/local/lib/python2.7/dist-packages/txthings/coap.py", line 1338, in sendResponse print "Token: %s" % (response.token) File "/usr/local/lib/python2.7/dist-packages/twisted/logger/_io.py", line 163, in write string = string.decode(self._encoding) File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode return codecs.utf_8_decode(input, errors, True) exceptions.UnicodeDecodeError: 'utf8' codec can't decode byte 0xae in position 7: invalid start byte Although it is triggered by simple print, it seems to be caused by logging. Does new logging framework need any configuration to stay compatible with the old one? Best regards Maciej Wasilak

3 3

Re: [Twisted-Python] [Twisted-web] Twisted is removing Python 2.6 support
by John Santos June 8, 2015

June 8, 2015

At Monday 6/8/2015 11:32 AM, you wrote: >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 <JOHN(a)egh.com> wrote: > > Hi Glyph, > > > > Is this the Mac Mini we are hosting for you? Could I help with anything? > > Thanks -- John Santos Evans Griffiths & Hart, Inc. 781-861-0670 ext 539

2 1

[Twisted-Python] New Supported Platforms (FreeBSD 10.1/Python 2.7, OS X 10.10/Python 2.7)
by Amber "Hawkie" Brown June 8, 2015

June 8, 2015

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

1 0

Re: [Twisted-Python] [Twisted-web] Twisted is removing Python 2.6 support
by Glyph June 8, 2015

June 8, 2015

> On Jun 8, 2015, at 2:57 AM, exarkun(a)twistedmatrix.com wrote: > > On 09:42 am, hawkowl(a)atleastfornow.net wrote: >> >>> On 8 Jun 2015, at 17:27, exarkun(a)twistedmatrix.com wrote: >>> >>> On 05:57 am, hawkowl(a)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-web(a)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. >> 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? This prompted me to see if the existing builder could be upgraded. I thought the hardware was unsupported, but I hadn't checked. I think I was wrong, and it is now downloading Yosemite. (For the third time. Trying to do this download on the first day of WWDC may not have been the greatest idea.) I think that new hardware would still be preferable because this machine is old, slow, overtaxed, and unreliable. For example, it runs Speed Center as well as the OS X builder. We have redundancy in most of our other builders now, which is very useful especially during times of heavy activity, like sprints, where lots of concurrent builds are going on, but this is the sole OS X builder. Another area where redundancy would be nice is when doing upgrades. For example, if the download ever finishes, I'm going to pull the trigger on this Yosemite upgrade, and ... hopefully it works? If it doesn't, we will have zero Mac builders until someone in the data center that is donating hosting can plug a console into that machine and see why it didn't finish booting. There's not really a good way to manage this right now. Finally, it would be nice to actually support multiple pythons on multiple OS versions - all the still supported / updated ones, anyway - and we'd need multiple builders for that. -glyph

4 4