Re: [Python-Dev] Tracker cleanup roadmap
Let's improve the tracker UI to better fit our needs. Then, classify them bugs and separate garbage from real development. Lastly, bug reporters should get a better UI. That's it, any help is welcome. The plan sounds great. I can help with the deployment aspects (reviewing tracker patches, and deploying them on the tracker site), but not much beyond that (except for discussions, of course). Don't expect too much help from other people - I have been waiting for volunteers to show up helping with the tracker for more than a year now. I suggest you prioritize things by bang for the buck (is that the right saying?), starting with changes that take least effort to implement. Discussions should be carried out on the tracker-discuss list, and, of course, in the meta-tracker. Good luck, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Patch logging module for IronPython compatibility
Hello all, Issue 5287 is a patch for the logging module for compatibility with IronPython. IronPython provides sys._getframe but it throws an exception if you call it with a non-zero depth. This may be fixed in a future version of IronPython. http://bugs.python.org/issue5287 It doesn't at all change the behaviour on other platforms (does an explicit platform check I'm afraid) but fixes a nasty problem with the logging module not working at all on IronPython. As this is a bugfix for IronPython at least and IronPython 2.6 is currently being worked on (tracking Python 2.6) it would be great to get this into 2.6-maint. All the best, Michael -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] To 3.0.2 or not to 3.0.2?
Le Tuesday 17 February 2009 08:52:20 Lennart Regebro, vous avez écrit : On Tue, Feb 17, 2009 at 00:50, Guido van Rossum gu...@python.org wrote: Can you explain the difficulty with porting setuptools in more detail? Oh, it just exposes a bug in distutils. It probably means I'll have to make a test for python version, and if it is 3.0.1, monkey-patch distutils. I haven't really looked into if there is any other possibilities yet, I'm concentrating to make it run for 3.1 trunk first. That's funny, because the failing code does compare versions :-) ... File c:\Python30\lib\distutils\cygwinccompiler.py, line 314, in __init__ if self.gcc_version = 2.91.57: File c:\Python30\lib\distutils\version.py, line 64, in __le__ c = self._cmp(other) File c:\Python30\lib\distutils\version.py, line 341, in _cmp return cmp(self.version, other.version) NameError: global name 'cmp' is not defined -- Victor Stinner aka haypo http://www.haypocalc.com/blog/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patch logging module for IronPython compatibility
Michael Foord wrote: Hello all, Issue 5287 is a patch for the logging module for compatibility with IronPython. IronPython provides sys._getframe but it throws an exception if you call it with a non-zero depth. This may be fixed in a future version of IronPython. http://bugs.python.org/issue5287 It doesn't at all change the behaviour on other platforms (does an explicit platform check I'm afraid) but fixes a nasty problem with the logging module not working at all on IronPython. As this is a bugfix for IronPython at least and IronPython 2.6 is currently being worked on (tracking Python 2.6) it would be great to get this into 2.6-maint. I've submitted an alternative patch that catches the error _getframe raises on IronPython. As it is possible that _getframe will work on IronPython in the future (although it is likely to be enabled by a switch as tracking Python frames has a performance cost) this is a slightly more future proof solution. Michael All the best, Michael -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] To 3.0.2 or not to 3.0.2?
Victor Stinner wrote: Le Tuesday 17 February 2009 08:52:20 Lennart Regebro, vous avez écrit : On Tue, Feb 17, 2009 at 00:50, Guido van Rossum gu...@python.org wrote: Can you explain the difficulty with porting setuptools in more detail? Oh, it just exposes a bug in distutils. It probably means I'll have to make a test for python version, and if it is 3.0.1, monkey-patch distutils. I haven't really looked into if there is any other possibilities yet, I'm concentrating to make it run for 3.1 trunk first. Didn't a test fail because of this? seems the underlying issue is that this part of the stdlib didn't have enough test coverage. It seems that having very good/improving test coverage like is recommended for 3rd-party project wanting to switch would be a good goal for 3.0 evolution too. We know from PyPy experience that while always improving the test suite coverage is quite spotty at times. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wow!
On Tue, 17 Feb 2009 11:04:35 +1300, Greg Ewing wrote: Leif Walsh wrote: If only we had a second Earth to mess with, we could just copy and swap. Or we could use a generational approach, doing all our messy stuff around the moon and copying to earth when we've got our traffic control issues sorted out. Oh great, people not only trashed on the ground, but also the space. Have you never seen the garbage bin sign? Wait a minute... the standard lib must have something about this... import walle ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Closing outdated Mac issues
On 15 Feb, 2009, at 21:13, Daniel (ajax) Diniz wrote: Hi, In the discussion of a feature request for MacPython[1], the OP (hhas) said: As of Python 2.6/3.0, all Mac-specific modules are deprecated/ eliminated from the standard library and there are no longer any plans to submit appscript for possible inclusion. This issue should be rejected and closed. If that is the current state of Mac modules, there are no less than 17 issues* that should be closed, 4 bug reports** that might be kept open and 4 mixed-cases*** that might be obsolete/irrelevant. Besides amounting to 1% of open issues, these can divert efforts to bogus issues: I've submitted a patch for one of the mixed-cases (bug + feature request), but now don't think it was worth it. So, if someone could reassure / clarify the rules for closing these in general and/or take a quick look at specific issues, that would be a great help. The Carbon bindings in 2.6 are deprecated and I don't intend to work on fixing them, and would advise against trying to fix issues with these modules unless you're personally affected by them. Issue lists below. Regards, Daniel [1] http://bugs.python.org/issue916013 Should have been closed ages ago. * Feature requests and implementation polishing issues: http://bugs.python.org/issue706585 Expose FinderInfo in FSCatalogInfo Closed as won't fix. http://bugs.python.org/issue706592 Carbon.File.FSSpec should accept non-existing pathnames Closed as won't fix. http://bugs.python.org/issue776533 Carbon.Snd module SPB constructor shadowed Closed as fixed (after reapplying the patch on the trunk) http://bugs.python.org/issue779285 Carbon Event ReceiveNextEvent Left this open for now, I have to have a better look at the actual code to check if it is worthwhile to keep this issue open. http://bugs.python.org/issue806149 aetools.TalkTo methods can be obscured Closed as won't fix http://bugs.python.org/issue822005 Carbon.CarbonEvt.ReceiveNextEvent args wrong Left this open for now, seems to be related to issue779285. http://bugs.python.org/issue852150 Can't send Apple Events without WindowServer connection Closed as won't fix. http://bugs.python.org/issue853656 Carbon.CF.CFURLRef should be easier to create Closed as won't fix. http://bugs.python.org/issue869649 Quicktime missing funcitonality Closed as won't fix, even the C-level API is deprecated. http://bugs.python.org/issue878560 Add a console window for Carbon MacPython applets Closed as won't fix. [... Skip other issues ... : I'll have a look at these later on ] ** Probably out of date, irrelevant or both: http://bugs.python.org/issue779153 bgen requires Universal Headers, not OS X dev headers Should be closed, I'm not planning on recreating the Carbon bindings. http://bugs.python.org/issue602291 Bgen should learn about booleans This one is not related to OSX, appearently at least some people actually use Bgen for creating wrapper code. http://bugs.python.org/issue775321 plistlib error handling http://bugs.python.org/issue985064 plistlib crashes too easily on bad files Plistlib is in the generic standard library in 2.6 and 3.0. I haven't checked yet if these issues are relevant at this point in time. Ronald ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ronaldoussoren%40mac.com smime.p7s Description: S/MIME cryptographic signature ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] draft 3.1 release schedule
Benjamin Peterson schrieb: On Sun, Feb 15, 2009 at 10:59 AM, Guido van Rossum gu...@python.org wrote... Something like this? 3.1a1 March 7 3.1a2 April 4 3.1b1 May 2 3.1rc1 May 30 3.1rc2 June 13 3.1 Final June 27 That sounds reasonable. I will try to enforce a fairly strict stability policy during the beta and RCs. I've started a list on the release PEP [1]. [1] http://www.python.org/dev/peps/pep-0375/ Is the intention to release 2.7 and 3.1 in parallel? I suspect, comparing this to http://www.python.org/dev/peps/pep-0373/ that there is some name mangling in pep-0375? Regards, Gregor ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] To 3.0.2 or not to 3.0.2?
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote: Didn't a test fail because of this? seems the underlying issue is that this part of the stdlib didn't have enough test coverage. It seems that having very good/improving test coverage like is recommended for 3rd-party project wanting to switch would be a good goal for 3.0 evolution too. We know from PyPy experience that while always improving the test suite coverage is quite spotty at times. No, a test didn't fail. Our new distutils maintainer, Tarek Ziade, though, has been increasing the distutils test coverage greatly. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 2 very interesting projects - Python / Finance
Dear Python Group, First of all sorry for the unsolicited email, I have attached two very interesting long term Python projects in the Frankfurt area, Financial industry. I am working exclusively with the client on both requirements, interviews and contracts can be arranged very quickly. You will be involved in a project to develop the next generation of financial trading systems, this will be the biggest, fastest trading system of its kind in the world and will be used on a global scale. Financial experience is not a must, they are looking more for technical skills here. If the projects look interesting to you please feel free to contact me on the contact details below. Thank you for your help, Best Regards David Large Financial Institution - Frankfurt Senior Python C/C++ Developer (f/m) Tasks/Responsibilities Software developer for a complex electronic trading system. The software developer will work in the implementation team of the trading system; tasks include: - Requirements Analysis - Development of a Scripting framework based on Python - Specification - Implementation Target platform will be Linux. Qualifications/Required Skills (Mandatory) Rock Solid Python and C/C++ knowledge Integration of Python with C/C++ libraries Automated Testing Good overview and knowledge of open source software Experience of software development in large projects Good communications skills Ability to work in project teams A good command of English is a must. Additional Domain Business Skills Knowledge of derivatives trading an advantage, in particular U.S. options. Additional Information: Frankfurt am Main, Germany Start ASAP for a minimum of 6 months Rate - Negotiable This is an urgent requirement please contact me or send me your cv as soon as possible. Contact: David Russell - Account manager email: david.russ...@fdmgroup.com Tel: +49 (0) 69 756 0050 Web: www.fdmgroup.com /// Large Financial Institution - Frankfurt am Main Performance / High Availability Test Automation Engineer (f/m) Tasks/Responsibilities Developer of automated test procedures for a high-performance electronic trading system. The engineer will work in the Performance and Technical Test team of the project; tasks include: - Requirements Analysis - Development of distributed transaction feed procedures, mostly in Python - Implementation of automated result analysis - Design and implementation of test procedures for failover/recovery scenarios in a multi-tier environment - Supervision of regular runs of the automated performance test suite. Target platform will be Linux. Qualifications/Required Skills Python scripting Deep (3 years) knowledge of Linux, with a focus in the areas - Performance monitoring and tuning - Messaging architectures Performance testing experience, for latency and throughput, incl. data aggregation and reporting Good communications skills Experience of software development in large projects Good overview and knowledge of open source software Ability to work in an international project team. A good command of English is a must. Additional Domain Business Skills Knowledge of statistical data analysis methods would be an advantage. Experience in mechanisms of interfacing C/C++ and Python would also be advantageous. Frankfurt am Main, Germany Start ASAP to 31.12.09 with good extension prospects for 2010 Rate - Negotiable This is an urgent requirement please contact me or send me your cv as soon as possible. Contact: David Russell - Account manager email: david.russ...@fdmgroup.com Tel: +49 (0) 69 756 0050 Web: www.fdmgroup.com David Russell Account Manager FDM Group Beethoven Strasse 4, 60325 Frankfurt am Main Germany david.russ...@fdmgroup.com mailto:ka...@fdmgroup.com Tel: + 49 (0) 69 756 0050 Cell: + 49 (0) 173 3592288 Fax: + 49 (0) 69 756 00555 www.fdmgroup.com http://www.fdmgroup.com/ www.fdmacademy.com http://www.fdmacademy.com/ BRIGHTON, LONDON, MANCHESTER, LUXEMBOURG, FRANKFURT, ZURICH NEW YORK This message is from FDM Group Plc, and may contain information that is confidential or privileged. If you are not the intended recipient, please delete the message and any attachments and notify the sender. This email is not intended to create legally binding commitments on behalf of FDM Group Plc, nor do its contents reflect the corporate views or policies of FDM. Any unauthorised disclosure, use or dissemination, either whole or partial, is prohibited. FDM Group Plc is a private limited company registered in England (Reg. No. 2542980). This e-mail has been scanned for all viruses by Star
Re: [Python-Dev] draft 3.1 release schedule
On Tue, Feb 17, 2009 at 7:55 AM, Gregor Lingl gregor.li...@aon.at wrote: I've started a list on the release PEP [1]. [1] http://www.python.org/dev/peps/pep-0375/ Is the intention to release 2.7 and 3.1 in parallel? No. I suspect, comparing this to http://www.python.org/dev/peps/pep-0373/ that there is some name mangling in pep-0375? It seems I left 2.7 in the prose a few times. I've fixed that now. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] draft 3.1 release schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 17, 2009, at 8:55 AM, Gregor Lingl wrote: Is the intention to release 2.7 and 3.1 in parallel? I don't think we should this time. We want to get 3.1 out sooner than the typical 18 month development cycle, and I think we should concentrate on making that a great release without worrying about also trying to get 2.7 out. :Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSZrJ7HEjvBPtnXfVAQJEKAP/fQ/SWqCNYmPQreBdN4Y7BKC4+K0f9Kk6 7DuVEyjd/BI9luqLxeGgZFdm9cwBXNkrSQ0Vw9wGx5rjGWRxPhAzWPh3tSEUQzFb wpQCqGkwktb7dxub4f+aeYBWJ802jrapfDXY48iRuGopCstm4IevjkZCesnMwrf7 fpOX6VDx5IQ= =y5N7 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 2 very interesting projects - Python / Finance
Dear Python Development Group, First of all sorry for the unsolicited email, I have attached two very interesting long term Python projects in the Frankfurt area, Financial industry. I am working exclusively with the client on both requirements, interviews and contracts can be arranged very quickly. You will be involved in a project to develop the next generation of financial trading systems, this will be the biggest, fastest trading system of its kind in the world and will be used on a global scale. Financial experience is not a must, they are looking more for technical skills here. If the projects look interesting to you please feel free to contact me on the contact details below. Thank you for your help, Best Regards David Large Financial Institution - Frankfurt Senior Python C/C++ Developer (f/m) Tasks/Responsibilities Software developer for a complex electronic trading system. The software developer will work in the implementation team of the trading system; tasks include: - Requirements Analysis - Development of a Scripting framework based on Python - Specification - Implementation Target platform will be Linux. Qualifications/Required Skills (Mandatory) Rock Solid Python and C/C++ knowledge Integration of Python with C/C++ libraries Automated Testing Good overview and knowledge of open source software Experience of software development in large projects Good communications skills Ability to work in project teams A good command of English is a must. Additional Domain Business Skills Knowledge of derivatives trading an advantage, in particular U.S. options. Additional Information: Frankfurt am Main, Germany Start ASAP for a minimum of 6 months Rate - Negotiable This is an urgent requirement please contact me or send me your cv as soon as possible. Contact: David Russell - Account manager email: david.russ...@fdmgroup.com Tel: +49 (0) 69 756 0050 Web: www.fdmgroup.com /// Large Financial Institution - Frankfurt am Main Performance / High Availability Test Automation Engineer (f/m) Tasks/Responsibilities Developer of automated test procedures for a high-performance electronic trading system. The engineer will work in the Performance and Technical Test team of the project; tasks include: - Requirements Analysis - Development of distributed transaction feed procedures, mostly in Python - Implementation of automated result analysis - Design and implementation of test procedures for failover/recovery scenarios in a multi-tier environment - Supervision of regular runs of the automated performance test suite. Target platform will be Linux. Qualifications/Required Skills Python scripting Deep (3 years) knowledge of Linux, with a focus in the areas - Performance monitoring and tuning - Messaging architectures Performance testing experience, for latency and throughput, incl. data aggregation and reporting Good communications skills Experience of software development in large projects Good overview and knowledge of open source software Ability to work in an international project team. A good command of English is a must. Additional Domain Business Skills Knowledge of statistical data analysis methods would be an advantage. Experience in mechanisms of interfacing C/C++ and Python would also be advantageous. Frankfurt am Main, Germany Start ASAP to 31.12.09 with good extension prospects for 2010 Rate - Negotiable This is an urgent requirement please contact me or send me your cv as soon as possible. Contact: David Russell - Account manager email: david.russ...@fdmgroup.com Tel: +49 (0) 69 756 0050 Web: www.fdmgroup.com David Russell Account Manager FDM Group Beethoven Strasse 4, 60325 Frankfurt am Main Germany david.russ...@fdmgroup.com mailto:ka...@fdmgroup.com Tel: + 49 (0) 69 756 0050 Cell: + 49 (0) 173 3592288 Fax: + 49 (0) 69 756 00555 www.fdmgroup.com http://www.fdmgroup.com/ www.fdmacademy.com http://www.fdmacademy.com/ BRIGHTON, LONDON, MANCHESTER, LUXEMBOURG, FRANKFURT, ZURICH NEW YORK This message is from FDM Group Plc, and may contain information that is confidential or privileged. If you are not the intended recipient, please delete the message and any attachments and notify the sender. This email is not intended to create legally binding commitments on behalf of FDM Group Plc, nor do its contents reflect the corporate views or policies of FDM. Any unauthorised disclosure, use or dissemination, either whole or partial, is prohibited. FDM Group Plc is a private limited company registered in England (Reg. No. 2542980). This e-mail has been scanned for all viruses by
Re: [Python-Dev] Tracker cleanup report
Paul Moore wrote: 2009/2/16 Daniel (ajax) Diniz aja...@gmail.com: Hi, Here's a summary of what's been accomplished and what's almost done. This kinda marks the end of this Bug Season for me, but I'd like to do at least one more installment before PyCon. Can I, for one, offer a *huge* round of applause for what you've achieved. It's great to see the tracker getting some serious attention. Thank you, but I can only take a small part of the kudos. It's been a collective work, involving from the BDFL to issue reporters. Also, lots of people have been taking care of the tracker. Notably, Christian Heimes has done a lot of cleanup and updating in early 2008, Facundo did the same earlier (2005, IIRC) and Benjamin went through a lot of tickets during the 2.6/3.0 release cycle. Martin, Benjamin, Victor and Hirokazu have spent a lot of time tidying things up lately, and some nice fellows like Antoine, Mark, Nick Coghlan, Amaury, and most cited above are constantly reviewing tickets and offering feedback. Some people help fighting spam (e.g. Skip, IIRC). Brett is hors concours regarding time spent for any Python-related effort, so I won't mention him :D There's also those recently organizing tickets in their area of interest: Tarek is on top of distutils issues with lots of help from Akira Kitada, Georg even has auto-assignment for doc issues, Jesse Noller with multiprocessing, etc. Of course, this has always happened to some degree, so lots of people have done that in the past, then reduced their level of tracker-handling activity, are now back and helping with lots of issues, e.g. Jack Jansen and Ronald Oussoren. These are all from the top of my head, from diving into hundreds of reports and following the tracker activity. Lots of other people I fail to mention have taken the task of dealing with tickets for themselves. So kudos to everyone that invest time handling bugs, feature requests, janitorial tasks and the eventual PEBKAC. Thanks for the support! Cheers, Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Closing outdated Mac issues
Hi Ned, Ned Deily wrote: Other than Mac/Modules, the rest of the Mac/ directory is mainly stuff used for building or going into the OS X installer images, including things like IDLE.app. These are used in 2.x and in 3.x. Thanks, knowing that makes the ticket handling easier! There are 40 C files, two headers and 69 python files in /Mac in trunk. The 2.6 (and 2.5.x) docs say development has stopped and that they'd be replaced in 2.5. So ISTM closing RFEs for these modules would be an improvement. Honestly, fixing them is fine but since the modules are deprecated but still in existence in 2.x, but they are definitely nothing above a normal priority issue. OK, I'll let the bug reports open. What about RFEs? I think the reasonable thing to do is close them as not to be fixed/implemented. At this point, the chances that someone would fix them are pretty slim and, in many cases, I'm sure the module is either obsolete because other, and better supported, solutions are now available, like PyObjC or appscript. If people feel strongly about an issue, they can always ask to re-open it. OK, Ronald is helping sort them and I'll clean whatever is left based on your combined feedback. Taking a quick look at your list, the only ones that may be worth looking at are the plistlib ones since it lives on in 3.x. I think all the rest are deprecated and gone in 3.x. OK, plistlib is a keeper in my list now. Thanks a lot for the feedback (and for helping with the Mac installers!) :) Regards, Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
On Tue, Feb 17, 2009, David Russell wrote: Dear Python Development Group, First of all sorry for the unsolicited email, This is spam, and you have now jeopardized your correct posting to the Python Job Board. The other website administrators will be informed and we will discuss whether spamming python-dev warrants withdrawing it. -- Aahz (a...@pythoncraft.com) * http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Closing outdated Mac issues
Hi, Ronald, Ronald Oussoren wrote: On 15 Feb, 2009, at 21:13, Daniel (ajax) Diniz wrote: Hi, In the discussion of a feature request for MacPython[1], the OP (hhas) said: As of Python 2.6/3.0, all Mac-specific modules are deprecated/eliminated from the standard library and there are no longer any plans to submit appscript for possible inclusion. This issue should be rejected and closed. [...] So, if someone could reassure / clarify the rules for closing these in general and/or take a quick look at specific issues, that would be a great help. The Carbon bindings in 2.6 are deprecated and I don't intend to work on fixing them, and would advise against trying to fix issues with these modules unless you're personally affected by them. OK. [1] http://bugs.python.org/issue916013 Should have been closed ages ago. [snip] http://bugs.python.org/issue776533 Carbon.Snd module SPB constructor shadowed Closed as fixed (after reapplying the patch on the trunk) [...] http://bugs.python.org/issue779285 Carbon Event ReceiveNextEvent Left this open for now, I have to have a better look at the actual code to check if it is worthwhile to keep this issue open. Wow, thanks a lot for taking care of all these issues! If you need a hand to close, assign or just update any of them, I'd be glad to help. I'll put any closing of these on hold until you're done, I have no hurry :) http://bugs.python.org/issue779153 bgen requires Universal Headers, not OS X dev headers Should be closed, I'm not planning on recreating the Carbon bindings. OK, I'll add a 'will close unless someone who needs this comes forward' note on this one, but will leave it open for a while as it might help in wrapping code. http://bugs.python.org/issue602291 Bgen should learn about booleans This one is not related to OSX, appearently at least some people actually use Bgen for creating wrapper code. Thanks, will update it and leave open. http://bugs.python.org/issue775321 plistlib error handling http://bugs.python.org/issue985064 plistlib crashes too easily on bad files Plistlib is in the generic standard library in 2.6 and 3.0. I haven't checked yet if these issues are relevant at this point in time. They are not, I'll work on tests/patches for them. Thanks for handling these and for the valuable feedback, Ronald! Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker cleanup report
Brett Cannon wrote: Ditto from me! And I will eventually get to the bugs assigned to me (hopefully starting some time this week). No hurry, just let me know if you see stupid mistakes on my part (I've once or twice added an issue as its own dependency) :) Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker cleanup report
Jack Jansen wrote: I had a cursory look at these issues as they came by, and I didn't see any that struck me as still being relevant. Thanks a lot for the feedback, Jack! Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
Dear Aahz, I understand your point but the line should be drawn between somebody selling Viagra or insurance to someone like me who is offering an opportunity to a suitable candidate to work on a Python project developing a new global trading system for a world leading financial institution. I am not trying to sell something or take something away from anybody nor am I offering something that does not exist, I am broadcasting a realistic, solid opportunity to a group of people that may benefit from it. Looking at the current global job climate I would have thought this type of email would be welcomed by the Python community? If you don't agree then do what you have to do and report me to the other web administrators. Maybe you should start a list that users can join to receive project offers? It makes sense. Best regards David Russell Account Manager FDM Group Beethoven Strasse 4, 60325 Frankfurt am Main Germany -Original Message- From: Aahz [mailto:a...@pythoncraft.com] Sent: 17 February 2009 15:39 To: David Russell Cc: Python-Dev@python.org Subject: Re: [Python-Dev] 2 very interesting projects - Python / Finance On Tue, Feb 17, 2009, David Russell wrote: Dear Python Development Group, First of all sorry for the unsolicited email, This is spam, and you have now jeopardized your correct posting to the Python Job Board. The other website administrators will be informed and we will discuss whether spamming python-dev warrants withdrawing it. -- Aahz (a...@pythoncraft.com) * http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk This message is from FDM Group Plc, and may contain information that is confidential or privileged. If you are not the intended recipient, please delete the message and any attachments and notify the sender. This email is not intended to create legally binding commitments on behalf of FDM Group Plc, nor do its contents reflect the corporate views or policies of FDM. Any unauthorised disclosure, use or dissemination, either whole or partial, is prohibited. FDM Group Plc is a private limited company registered in England (Reg. No. 2542980). This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
[Aahz] ... This is spam, and you have now jeopardized your correct posting to the Python Job Board. The other website administrators will be informed and we will discuss whether spamming python-dev warrants withdrawing it. To be fair, a python-dev moderator approved the posting, so in their judgment it wasn't spam. It was in my judgment, but someone else approved it before I managed to hit the discard button. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
David: Perhaps you'd like to give me your company's internal mailing list address so I can drop your staff a line when I hear of Python conferences going on your area. Or maybe that's not what the list is for? This list, as is clearly stated at http://www.python.org/community/lists/ is for work on developing Python. Hence your posting (and your protestations of innocence) is unsolicited commercial email, AKA spam. Python users who are looking for jobs know about the jobs board, where you have already submitted vacancy notices (now jeopardized by this anti-social act). Please stop now - if you must reply, feel free to do so by private email. regards Steve David Russell wrote: Dear Aahz, I understand your point but the line should be drawn between somebody selling Viagra or insurance to someone like me who is offering an opportunity to a suitable candidate to work on a Python project developing a new global trading system for a world leading financial institution. I am not trying to sell something or take something away from anybody nor am I offering something that does not exist, I am broadcasting a realistic, solid opportunity to a group of people that may benefit from it. Looking at the current global job climate I would have thought this type of email would be welcomed by the Python community? If you don't agree then do what you have to do and report me to the other web administrators. Maybe you should start a list that users can join to receive project offers? It makes sense. Best regards David Russell Account Manager FDM Group Beethoven Strasse 4, 60325 Frankfurt am Main Germany -Original Message- From: Aahz [mailto:a...@pythoncraft.com] Sent: 17 February 2009 15:39 To: David Russell Cc: Python-Dev@python.org Subject: Re: [Python-Dev] 2 very interesting projects - Python / Finance On Tue, Feb 17, 2009, David Russell wrote: Dear Python Development Group, First of all sorry for the unsolicited email, This is spam, and you have now jeopardized your correct posting to the Python Job Board. The other website administrators will be informed and we will discuss whether spamming python-dev warrants withdrawing it. -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
Steve Holden wrote: David: Perhaps you'd like to give me your company's internal mailing list address so I can drop your staff a line when I hear of Python conferences going on your area. Or maybe that's not what the list is for? [...] Just to close this out Aahz and I received an apologetic reply by private email. regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
Tim Peters wrote: [Aahz] ... This is spam, and you have now jeopardized your correct posting to the Python Job Board. The other website administrators will be informed and we will discuss whether spamming python-dev warrants withdrawing it. To be fair, a python-dev moderator approved the posting, so in their judgment it wasn't spam. I saw it in the queue and hit reject. I think he may have signed up and reposted - either that or I *didn't* hit reject when I intended to. Michael It was in my judgment, but someone else approved it before I managed to hit the discard button. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2 very interesting projects - Python / Finance
On 17/02/2009 17:55, Steve Holden wrote: is for work on developing Python. Hence your posting (and your protestations of innocence) is unsolicited commercial email, AKA spam. Python users who are looking for jobs know about the jobs board, where you have already submitted vacancy notices (now jeopardized by this anti-social act). Please stop now - if you must reply, feel free to do so by private email. I'd like to mention that python-nl got this, too, so he probably spammed a bunch of lists. Cheers, Dirkjan ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 30-bit PyLong digits in 3.1?
A few months ago there was a discussion [1] about changing Python's long integer type to use base 2**30 instead of base 2**15. http://bugs.python.org/issue4258 was opened for this. With much help from many people (but especially Antoine and Victor), I've finally managed to put together an essentially finished patch for this (see 30bit_longdigit14.patch in the tracker). I'd like to get this in for 3.1. Any objections or comments? Is this PEP territory? Summary of the patch: * Apart from improved performance, the effects should be almost entirely invisible to users. * By default, 30-bit digits are used only when both 32-bit and 64-bit integer types are available; otherwise the code falls back to the usual 15-bit digits. For Unix, there's a configure option --enable-big-digits that overrides this default. In particular, you can use --disable-big-digits to force 15-bit digit longs. * There's a new structseq sys.int_info that looks like this: sys.int_info sys.int_info(bits_per_digit=30, sizeof_digit=4) the sizeof_digit is mostly there to help out the sys.getsizeof tests in test_sys. * Benchmarks show significant speedups (20% and more) for integer arithmetic on 64-bit systems, and lesser speedups on 32-bit systems. Operations with single-digit integers aren't affected much either way; most of the benefit seems to be for operations with small multi-digit integers. * There are more performance improvements planned (see the issue discussion for details); I left them out of the current patch for simplicity, and because they still need proper testing and benchmarking. Mark [1] http://mail.python.org/pipermail/python-dev/2008-November/083315.html ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 30-bit PyLong digits in 3.1?
I'd like to get this in for 3.1. Any objections or comments? Can you please upload it to Rietveld also? Is this PEP territory? I don't think so. Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Python 2.6.2 and 3.0.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thinking again about 3.0.2. If we'd like to do bug fix releases before Pycon, I suggest Monday March 9th for code freeze and tagging. That would mean a Tuesday March 10th release. What do you think? Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSZsbpHEjvBPtnXfVAQK5xgP/XIKmhKSbQLQ4rZvknkhDTel6R8w14/7Z lThGtuFJd3eKE4EOO3CP/zT8LT0rHTRkF1wGUZjyNoLW6bIQkGiTQYWxOsTV+Z7z Ak49VzUpf0KySd4Nwtzn/KxQ+z/i3ts3z5YRD9eWBs0ZtTAiOelZrTxievcWZt+6 0PpsQWGb+14= =caaa -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 30-bit PyLong digits in 3.1?
On Tue, Feb 17, 2009 at 7:49 PM, Martin v. Löwis mar...@v.loewis.de wrote: Can you please upload it to Rietveld also? Will do. I'm getting a 500 Server Error at the moment, but I'll keep trying. Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 30-bit PyLong digits in 3.1?
Use the upload.py script (/static/upload.py) rather than the Create Issue page. On Tue, Feb 17, 2009 at 12:36 PM, Mark Dickinson dicki...@gmail.com wrote: On Tue, Feb 17, 2009 at 7:49 PM, Martin v. Löwis mar...@v.loewis.de wrote: Can you please upload it to Rietveld also? Will do. I'm getting a 500 Server Error at the moment, but I'll keep trying. Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 30-bit PyLong digits in 3.1?
On Tue, Feb 17, 2009 at 8:42 PM, Guido van Rossum gu...@python.org wrote: Use the upload.py script (/static/upload.py) rather than the Create Issue page. Thanks. That worked. http://codereview.appspot.com/14105 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] To 3.0.2 or not to 3.0.2?
Benjamin Peterson schrieb: On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote: Didn't a test fail because of this? seems the underlying issue is that this part of the stdlib didn't have enough test coverage. It seems that having very good/improving test coverage like is recommended for 3rd-party project wanting to switch would be a good goal for 3.0 evolution too. We know from PyPy experience that while always improving the test suite coverage is quite spotty at times. No, a test didn't fail. Our new distutils maintainer, Tarek Ziade, though, has been increasing the distutils test coverage greatly. In addition to testing, this specific issue could have been found easily by running something like pylint over the stdlib, because undefined globals are one of the things they can detect with 100% accuracy... The hard thing about pylint of course is to get the signal/noise ratio right :) Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issues to be closed: objections?
On Mon, 16 Feb 2009, Daniel (ajax) Diniz wrote: http://bugs.python.org/issue809887 Improve pdb breakpoint feedback Why this one? John ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] To 3.0.2 or not to 3.0.2?
On Tue, Feb 17, 2009 at 3:02 PM, Georg Brandl g.bra...@gmx.net wrote: Benjamin Peterson schrieb: On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote: Didn't a test fail because of this? seems the underlying issue is that this part of the stdlib didn't have enough test coverage. It seems that having very good/improving test coverage like is recommended for 3rd-party project wanting to switch would be a good goal for 3.0 evolution too. We know from PyPy experience that while always improving the test suite coverage is quite spotty at times. No, a test didn't fail. Our new distutils maintainer, Tarek Ziade, though, has been increasing the distutils test coverage greatly. In addition to testing, this specific issue could have been found easily by running something like pylint over the stdlib, because undefined globals are one of the things they can detect with 100% accuracy... Oh, does pylint support py3k now? The hard thing about pylint of course is to get the signal/noise ratio right :) -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] -Qwarn and -3
If someone sets the -3 option to get py3k warnings, should the classic division warning get turned-on automatically? Right now, I get no warnings for: python -3 -c 9 / 5 Raymond ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] -Qwarn and -3
On Tue, Feb 17, 2009 at 4:50 PM, Raymond Hettinger pyt...@rcn.com wrote: If someone sets the -3 option to get py3k warnings, should the classic division warning get turned-on automatically? Right now, I get no warnings for: python -3 -c 9 / 5 I think you have a point. -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Issues to be closed: objections?
John J Lee wrote: On Mon, 16 Feb 2009, Daniel (ajax) Diniz wrote: http://bugs.python.org/issue809887 Improve pdb breakpoint feedback Why this one? Nice catch, this makes no sense. The patch even applies almost cleanly. I'll update it and set the others to pending, so further objections can be voiced. Thank for reviewing, John! Daniel ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker cleanup roadmap
On Tue, Feb 17, 2009 at 00:15, Martin v. Löwis mar...@v.loewis.de wrote: Let's improve the tracker UI to better fit our needs. Then, classify them bugs and separate garbage from real development. Lastly, bug reporters should get a better UI. That's it, any help is welcome. The plan sounds great. Yeah, the workflow needs work. I was hoping to try to clean it up once I got the current workflow documented but you beat me to it (which is a good thing). I can help with the deployment aspects (reviewing tracker patches, and deploying them on the tracker site), but not much beyond that (except for discussions, of course). Don't expect too much help from other people - I have been waiting for volunteers to show up helping with the tracker for more than a year now. We can try another volunteer call at PyCon if we want. I can plug it heavily during my talk. I suggest you prioritize things by bang for the buck (is that the right saying?) It's actually most bang for your buck, but close enough. , starting with changes that take least effort to implement. Discussions should be carried out on the tracker-discuss list, and, of course, in the meta-tracker. What Martin said. =) -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
