Apparently, os.access was forgotten when the file system encoding
was introduced in Python 2.2, and then it was again forgotten in
PEP 277.
I've now fixed it in the trunk (posixmodule.c:2.334), and I wonder
whether this is a backport candidate. People who try to invoke
os.access with a non-ASCII fi
"Phillip J. Eby" <[EMAIL PROTECTED]> writes:
> Which reminds me, btw, it would be nice while we're adding more
> execution control functions to have a way to get the current trace
> hook and profiling hook,
Well, there's the f_trace member of frame objects, but I honestly
can't remember what it's
Greg writes:
> This is one of my top two Java features [1].
...
> [1] The other is compiler recognition of "@deprecated" in doc comments.
Hmm... what a good idea! Let's see... what exactly does "@deprecated" DO in
Java? Why it causes the compiler to emit a warning if you use the function
At 10:03 AM 3/8/05 +, Michael Hudson wrote:
"Phillip J. Eby" <[EMAIL PROTECTED]> writes:
> Which reminds me, btw, it would be nice while we're adding more
> execution control functions to have a way to get the current trace
> hook and profiling hook,
Well, there's the f_trace member of frame ob
Martin v. Löwis wrote:
Apparently, os.access was forgotten when the file system encoding
was introduced in Python 2.2, and then it was again forgotten in
PEP 277.
I've now fixed it in the trunk (posixmodule.c:2.334), and I wonder
whether this is a backport candidate. People who try to invoke
os.acc
Brett C. wrote:
Martin v. Löwis wrote:
Apparently, os.access was forgotten when the file system encoding
was introduced in Python 2.2, and then it was again forgotten in
PEP 277.
I've now fixed it in the trunk (posixmodule.c:2.334), and I wonder
whether this is a backport candidate. People who try
Any objections to extending itemgetter() and attrgetter() to be able to
extract multiple fields at a time?
# SELECT name, rank, serialnum FROM soldierdata
map(attrgetter('name', 'rank', 'serialnum'), soldierdata)
# SELECT * FROM soldierdata ORDER BY unit, rank, proficiency
sorted(
Greg wished for:
... compiler recognition of "@deprecated" in doc comments.
Michael Chermside suggested:
= code =
import warnings
def deprecated(func):
"""This is a decorator which can be used to mark functions
as deprecated. It will result in a warning b
> Michael Chermside suggested:
> import warnings
>
> def deprecated(func):
> """This is a decorator which can be used to mark functions
> as deprecated. It will result in a warning being emmitted
> when the function is used."""
> def newFunc(*args, **kwargs)
The perennial "how do I remove duplicates from a list" topic came up on
c.l.py and in the discussion I mentioned the java 1.5 LinkedHashSet and
LinkedHashMap. I'd thought about proposing these before, but couldn't
think of where to put them. It was pointed out that the obvious place
would be the co
Delaney, Timothy C (Timothy) <[EMAIL PROTECTED]> wrote:
> The perennial "how do I remove duplicates from a list" topic came up on
> c.l.py and in the discussion I mentioned the java 1.5 LinkedHashSet and
> LinkedHashMap. I'd thought about proposing these before, but couldn't
> think of where to put
On 08 March 2005, Anthony Baxter said:
> I really would like to see it reverted, please.
Done.
Greg
--
Greg Ward <[EMAIL PROTECTED]> http://www.gerg.ca/
I just forgot my whole philosophy of life!!!
___
Python-Dev mailing
Steven Bethard wrote:
Delaney, Timothy C (Timothy) <[EMAIL PROTECTED]> wrote:
The perennial "how do I remove duplicates from a list" topic came up on
c.l.py and in the discussion I mentioned the java 1.5 LinkedHashSet and
LinkedHashMap. I'd thought about proposing these before, but couldn't
think o
On 09 March 2005, Anthony Baxter said (privately):
> Thanks! I really want to keep the no-new-features thing going for
> as long as possible, pending any AoG (Acts of Guido), of course.
Grumble. How do you feel about upgrading optparse to sync with Optik
1.5.1? I'm a bit embarassed that Python 2
On Sat, Apr 04, 1998 at 07:04:02AM +, Tim Peters wrote:
> [Martin v. L?wis]
> > I can't see any harm by supporting this operation also if __str__ returns
> > a Unicode object.
>
> It doesn't sound like a good idea to me, at least in part because it
> would be darned messy to implement short of
On 08 March 2005, Michael Chermside said:
> Greg writes:
> > This is one of my top two Java features [1].
> ...
> > [1] The other is compiler recognition of "@deprecated" in doc comments.
>
> Hmm... what a good idea! Let's see... what exactly does "@deprecated" DO in
> Java? Why it cause
On 09 March 2005, Delaney, Timothy C (Timothy) said:
> For those who don't know, LinkedHashSet and LinkedHashMap are simply
> hashed sets and maps that iterate in the order that the keys were added
> to the set/map. I almost invariably use them for the above scenario -
> removing duplicates without
Patch / Bug Summary
___
Patches : 279 open (-24) / 2797 closed (+33) / 3076 total ( +9)
Bugs: 851 open ( +2) / 4853 closed (+16) / 5704 total (+18)
RFE : 173 open ( +4) / 150 closed ( +2) / 323 total ( +6)
New / Reopened Patches
__
Fix for w
Greg Ward wrote:
> I'll attach another approach to the same problem, an ordered
> dictionary object. I believe the semantics of
> adding/readding/deleting keys is the same as java.util.LinkedHashMap
> -- certainly it seems the most sensible and easy-to-implement
> semantics.
That's essentially
On Tue, Mar 08, 2005, Greg Ward wrote:
> On 09 March 2005, Anthony Baxter said (privately):
>>
>> Thanks! I really want to keep the no-new-features thing going for
>> as long as possible, pending any AoG (Acts of Guido), of course.
>
> Grumble. How do you feel about upgrading optparse to sync wit
20 matches
Mail list logo