Anthony Baxter wrote:
Ok, I'm convinced - Martin, can you check this in?
Done!
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/arch
Robey Pointer <[EMAIL PROTECTED]> writes:
> (I've been lurking for a while but this is my first post. I maintain
> paramiko and enjoy harrassing people on sourceforge to fix the
> new-style Exception bug that vexes me. Nice to meet you all.) :)
Well, hey, you can review my patch if you like:
On Sunday 13 March 2005 18:35, Robey Pointer wrote:
> [on the os.access unicode fix]
Ok, I'm convinced - Martin, can you check this in?
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing li
On Mar 13, 2005, at 08:35, Robey Pointer wrote:
In other words, I don't think that the argument "users may have
written code to work around the bug" is a valid reason to not fix a
bug.
+1, as long as the bugfix doesn't break the workaround (and os.access's
bug seems to meet this criterion).
Ale
Anthony Baxter wrote:
So here's a list of open items I'm thinking about for the 2.4.1
release.
- os.access handling unicode filenames
I'm still thinking over whether this is going to cause more problems
for people who find it works for some Python 2.4 and not others. I'm
leaning towards s
[Anthony Baxter]
> So here's a list of open items I'm thinking about for the 2.4.1
> release.
>
> [... sorry, but my editor automatically deletes all paragraphs
> mentioning problems with Unicode ...]
> - The unitest changes>Changes to unitest to fix subclassing broke Zope's
>unittes
Anthony Baxter wrote:
I'm now pretty sure we need a 2.4.1rc2 for this week, and a 2.4.1 final the
week after. There's been a few too many changes for my tastes to say that
going straight to a 2.4.1 final is a prudent course of action.
"The week after" will by the PyCon week, in which I won't be ab
