Re: [Python-Dev] Ruby-style Blocks in Python [Pseudo-PEP]

2009-03-08 Thread Matthew Wilkes
On 8 Mar 2009, at 15:13, tav wrote: Apologies for bringing up an old issue, but I think I've worked out a Pythonic syntax for doing Ruby-style blocks. The short of it is: with employees.select do (emp): if emp.salary > developer.salary: return fireEmployee(emp) else

Re: [Python-Dev] syntax warnings don't go through warnings.warn?

2009-06-01 Thread Matthew Wilkes
On 1 Jun 2009, at 17:50, Dino Viehland wrote: I’m just a little surprised by this - Is there a reason why syntax warnings are special and untrappable via warnings.warn? Why should this work? From the docs... "Python programmers issue warnings by calling the warn() function defined in this

Re: [Python-Dev] syntax warnings don't go through warnings.warn?

2009-06-01 Thread Matthew Wilkes
On 1 Jun 2009, at 18:42, Michael Foord wrote: Dino is developing Python - he's one of the core developers of IronPython Ah, sorry, I'm bad with names, don't always pick up on who is who! and I suspect he is asking whether this is intentional, and IronPython should implement the same behav

Re: [Python-Dev] FINAL PROPULSION OPEN SOURCE ENGINE VARIANT FOR THE F-35 JOINT STRIKE FIGHTER

2009-06-12 Thread Matthew Wilkes
On 13 Jun 2009, at 00:01, OMEGA RED wrote: DEVELOP THE FIRST AND ONLY COMPLETELY OPEN SOURCE VARIANT OF THE PROPULSION ENGINE FOR THE F-35 JOINT STRIKE FIGHTER You're unlikely to find many people who want to help use open-source to facilitate murder. HOW MANY OUT THERE WANT TO HELP IN T

Re: [Python-Dev] FINAL PROPULSION OPEN SOURCE ENGINE VARIANT FOR THE F-35 JOINT STRIKE FIGHTER

2009-06-12 Thread Matthew Wilkes
On 13 Jun 2009, at 01:00, Guido van Rossum wrote: That's a rather presumptuous statement. Despite the poster's use of SHOUTING I don't see a reason to tell them they should use proprietary software just because you disagree with their politics Oh, I didn't mean they should use proprietary sof

Re: [Python-Dev] surprised to "++" and "--"

2009-09-25 Thread Matthew Wilkes
I know that there is no "++" or "--" operator in python, but if "var++" or something like that in my code(you know, most of C/C++ coders may like this),there is nothing wrong reported and program goes on just like expected!! This is obscure, maybe a bug. Hi, Firstly, this list is

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

2009-11-12 Thread Matthew Wilkes
On 2009-11-12, at 1136, Sriram Srinivasan wrote: standard libraries i meant the standard libraries used. and what i asked for is for(in python) both the standard-libraries and the standard libraries used. c the term (intra and inter library management) which includes the default standard li

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

2009-11-12 Thread Matthew Wilkes
Oh, I see. use library 1.1.5 versus use library 1.1.6 #thats all now i get all features That's part of pkg_resources. It looks like this: pkg_resources.require("mylibrary==1.1.6") import mylibrary There are plenty of other ways to manage this, most people use systems like virtualenv o

Re: [Python-Dev] Contribute

2010-03-29 Thread Matthew Wilkes
On 2010-03-30, at 0006, Valerio Turturici wrote: Have you any advice for me? :) Also, have a look at Google's Summer of Code programme. It is a good way to get involved with a large project. Matthw ___ Python-Dev mailing list Python-Dev@python.

Re: [Python-Dev] Python 3.0.1

2009-01-27 Thread Matthew Wilkes
On 27 Jan 2009, at 23:56, Barry Warsaw wrote: Also, 3.0 is a special case because it is IMO a broken release. AFAICT, it is not in any distro yet. Hopefully, no one will keep it around and it will vanish silently. I stand by my opinion about the right way to do this. I also think that

Re: [Python-Dev] pprint(iterator)

2009-02-02 Thread Matthew Wilkes
On 29 Jan 2009, at 21:54, Nick Coghlan wrote: For the "reiterable" cases like dictionary views (where the object is not consumed), an appropriate __str__ or __repr__ should be written). Indeed, instead of having a __pprint__ why not just allow a __repr__ to reformat its output? dict havin