Andrew Berg bahamutzero8...@gmail.com wrote:
He hasn't replied to his last two troll threads, though. It does seem
odd to write a wall of text and then not respond to replies. To be fair,
though, most replies either mock him or point out that he's a troll. :D
His recent rants do seem a lot
On 07/29/2011 11:43 PM, Chris Angelico wrote:
On Sat, Jul 30, 2011 at 6:44 AM, Corey Richardson kb1...@aim.com wrote:
Excerpts from rantingrick's message of Fri Jul 29 13:22:04 -0400 2011:
* New path module will ONLY support one path sep!
People who use windows are used to \ being their
On Aug 1, 3:19 am, Teemu Likonen tliko...@iki.fi wrote:
* 2011-07-30T10:57:29+10:00 * Steven D'Aprano wrote:
Teemu Likonen wrote:
Pathnames and the separator for pathname components should be
abstracted away, to a pathname object.
Been there, done that, floundered on the inability of
On Tue, Aug 2, 2011 at 5:03 PM, rantingrick rantingr...@gmail.com wrote:
This thread was intended to expose another PyWart and get the
community juices flowing. os.path is broken and cannot be repaired
because os.path was an improper API to begin with. The only way to
solve this problem is to
* 2011-07-30T10:57:29+10:00 * Steven D'Aprano wrote:
Teemu Likonen wrote:
Pathnames and the separator for pathname components should be
abstracted away, to a pathname object.
Been there, done that, floundered on the inability of people to work
out the details.
On 7/29/2011 8:50 PM, Steven D'Aprano wrote:
Guido has a rule of thumb: No constant arguments. Or another way to put
it: if a function takes an argument which is nearly always a constant
(usually, but not always, a flag) then it is usually better off as two
functions.
I do not really
On 2011-07-30, Michael Poeltl michael.poe...@univie.ac.at wrote:
join 'Python-Dev'-mailinglist and tell them!
from now on I will just ignore threads you initiated
does trolling really make that much fun?
RR must think so, considering how much effort he
On 2011.07.30 10:33 AM, Grant Edwards wrote:
RR must think so, considering how much effort he seems to put into it.
He hasn't replied to his last two troll threads, though. It does seem
odd to write a wall of text and then not respond to replies. To be fair,
though, most replies either mock him
On 7/29/11 8:50 PM, Steven D'Aprano wrote:
Andrew Berg wrote:
os.path.exists(path, ignoreSymLnks=False)
I actually agree with you on these, which I suppose is interesting.
Guido has a rule of thumb: No constant arguments. Or another way to put
it: if a function takes an argument which is
--
Overview of Problems:
--
* Too many methods exported.
* Poor choice of method names.
* Non public classes/methods exported!
* Duplicated functionality.
On 2011.07.29 12:22 PM, rantingrick wrote:
* New path module will ONLY support one path sep! There is NO reason
to support more than one. When we support more than one path sep we
help to propagate multiplicity.We should only support the slash and
NOT the backslash across ALL OS's since the
Andrew Berg wrote:
* New path module will ONLY support one path sep! There is NO reason
to support more than one. When we support more than one path sep we
help to propagate multiplicity.We should only support the slash and
NOT the backslash across ALL OS's since the slash is more widely
Dnia Fri, 29 Jul 2011 14:41:22 -0500, harrismh777 napisał(a):
The backslash sep is an asinine CPM/80 | DOS disk based carry-over which
does not fit well with the modern forward direction. The disk based file
system carry-over is bad enough; but, propagating multiple ways of doing
simple
* 2011-07-29T10:22:04-07:00 * rantingr...@gmail.com wrote:
* New path module will ONLY support one path sep! There is NO reason
to support more than one.
Pathnames and the separator for pathname components should be abstracted
away, to a pathname object. This pathname object could have a path
On Sat, Jul 30, 2011 at 3:22 AM, rantingrick rantingr...@gmail.com wrote:
~
3. Non Public Names Exposed!
~
* genericpath
* os
* stat
* sys
* warnings
And you intend to do what, exactly, with these?
- splitunc -- Unix specific!
1)
Excerpts from rantingrick's message of Fri Jul 29 13:22:04 -0400 2011:
--
Proposed new functionality:
--
* New path module will ONLY support one path sep! There is NO
reason to support more than
On Fri, 29 Jul 2011 10:22:04 -0700, rantingrick wrote:
--
Overview of Problems:
--
* Too many methods exported.
* Poor choice of method names.
* Non public classes/methods exported!
*
On 2011.07.29 04:21 PM, Alister Ware wrote:
instead of all this negativity why don't you try being productive for a
change either make a suggestion for an addition (ie something that does
not yest exits) or better yet give us all the benefit of your supreme
coding talent provide some code?
On Sat, Jul 30, 2011 at 6:44 AM, Corey Richardson kb1...@aim.com wrote:
Excerpts from rantingrick's message of Fri Jul 29 13:22:04 -0400 2011:
* New path module will ONLY support one path sep!
People who use windows are used to \ being their pathsep. If you show
them a path that looks like
On 7/29/2011 1:22 PM, rantingrick wrote:
* Introduce a new method named partition which (along with string
splitting methods) will replace the six methods basename, dirname,
split, splitdrive, splitunc, splittext. The method will return
a tuple of the path split into four parts: (drive, path,
join 'Python-Dev'-mailinglist and tell them!
from now on I will just ignore threads you initiated
does trolling really make that much fun?
* rantingrick rantingr...@gmail.com [2011-07-29 19:25]:
--
Overview
Andrew Berg wrote:
os.path.exists(path, ignoreSymLnks=False)
I actually agree with you on these, which I suppose is interesting.
Guido has a rule of thumb: No constant arguments. Or another way to put
it: if a function takes an argument which is nearly always a constant
(usually, but not
Teemu Likonen wrote:
* 2011-07-29T10:22:04-07:00 * rantingr...@gmail.com wrote:
* New path module will ONLY support one path sep! There is NO reason
to support more than one.
Pathnames and the separator for pathname components should be abstracted
away, to a pathname object.
Been
On 2011.07.29 07:50 PM, Steven D'Aprano wrote:
Especially if the implementation looks like this:
def get_thing(argument, flag):
if flag:
return one_thing(argument)
else:
return another_thing(argument)
Well, that would be annoying, but wouldn't it be even more
Ben Finney said:
But this is all getting rather generic and abstract. What specific
real-world examples do you have in mind?
regex match vs regex search?
--
http://mail.python.org/mailman/listinfo/python-list
25 matches
Mail list logo
