[EMAIL PROTECTED] wrote:
> Martin> The natural question then is: what operating system, what
> Martin> subversion version are you using?
>
> Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort
> of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I bui
Noam Raphael <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> It seems that we both agree that freezing is cool (-; . We disagree on
> whether a copy-on-write behaviour is desired. Your arguments agains
> copy-on-write are:
> 1. It's not needed.
> 2. It's complicated to implement.
>
> But first of all
On Sunday 30 October 2005 18:37, Gustavo Niemeyer wrote:
> I'd like to apply the following patch:
+1
Might want to include SystemExit as well, though I think that's less likely to
be seen in practice.
-Fred
--
Fred L. Drake, Jr.
___
Python-De
On 10/30/05, François Pinard <[EMAIL PROTECTED]> wrote:
> All development is done in house by French people. All documentation,
> external or internal, comments, identifier and function names,
> everything is in French. Some of the developers here have had a long
> programming life, while they on
[Martin von Löwis]
> My canonical example is François Pinard, who keeps requesting it,
> saying that local people where surprised they couldn't use accented
> characters in Python. Perhaps that's because he actually is Quebecian
> :-)
I presume I should comment a bit on this.
People here are
Le dimanche 30 octobre 2005 à 19:08 -0600, [EMAIL PROTECTED] a écrit :
> Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort
> of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built
> from source back in the May timeframe. Should I upgrade to 1.2.3 as a
>
Martin> The natural question then is: what operating system, what
Martin> subversion version are you using?
Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort
of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built
from source back in the May time
> It allows everything in Python to be both mutable and hashable,
I don't understand, since it's already the case. Any user-defined object
is at the same time mutable and hashable.
And if you want the hash value to follow the changes in attribute
values, just define an appropriate __hash__ method
The StreamHandler available under the logging package is currently
catching all exceptions under the emit() method call. In the
Handler.handleError() documentation it's mentioned that it's
implemented like that because users do not care about errors
in the logging system.
I'd like to apply the fol
Hello,
It seems that we both agree that freezing is cool (-; . We disagree on
whether a copy-on-write behaviour is desired. Your arguments agains
copy-on-write are:
1. It's not needed.
2. It's complicated to implement.
But first of all, you didn't like my use cases. I want to argue with that.
>
On Oct 26, 2005, at 20:02, Evan Jones wrote:
> In the process of doing this, I came across a comment mentioning that
> it would be desirable to separate the parser. Is there any interest in
> doing this? I now have a vague idea about how to do this. Of course,
> there is no point in making changes
[EMAIL PROTECTED] wrote:
> I tried "svn up" to bring my sandbox up-to-date and got this output:
>
> % svn up
> UInclude/unicodeobject.h
> subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017)
> svn: Checksum mismatch for
> 'Objects/.svn/text-base/unicodeobject.c.svn-base
[EMAIL PROTECTED] wrote:
> I went ahead and used Tim's note as the basis for a page on the wiki:
>
> http://wiki.python.org/moin/CvsToSvn
>
> It's linked from the PythonDevelopers page (a page of previously dubious
> necessity).
I have pretty much the same reservations against Wikis as Brett
[EMAIL PROTECTED] wrote:
> Fred> Shouldn't we simply remove the .cvsignore files? Subversion
> Fred> doesn't use them, so they'll just end up getting out of sync with
> Fred> the svn:ignore properties.
>
> Is there some equivalent? If so, can we convert the .cvsignore files before
>
[EMAIL PROTECTED] wrote:
> I tried "svn up" to bring my sandbox up-to-date and got this output:
>
> % svn up
> UInclude/unicodeobject.h
> subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017)
> svn: Checksum mismatch for
> 'Objects/.svn/text-base/unicodeobject.c.svn-base
Tim> Excellent suggestions! I have a few to pass on:
skip> These are precisely the things the Wiki would be good for.
I went ahead and used Tim's note as the basis for a page on the wiki:
http://wiki.python.org/moin/CvsToSvn
It's linked from the PythonDevelopers page (a page of pre
I tried "svn up" to bring my sandbox up-to-date and got this output:
% svn up
UInclude/unicodeobject.h
subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017)
svn: Checksum mismatch for
'Objects/.svn/text-base/unicodeobject.c.svn-base'; expected:
'8611dc5f592e7cbc6070524a
Fred> Shouldn't we simply remove the .cvsignore files? Subversion
Fred> doesn't use them, so they'll just end up getting out of sync with
Fred> the svn:ignore properties.
Is there some equivalent? If so, can we convert the .cvsignore files before
deleting them?
Skip
___
Tim> Excellent suggestions! I have a few to pass on:
...
Tim,
Thanks for the tips. As a new svn user myself, I find these helpful.
These are precisely the things the Wiki would be good for. They don't
prescribe policy. They help people in a general way to migrate from cvs to
svn mo
Noam Raphael wrote:
> Won't "svn propedit svn:ignore ." do the trick?
It certainly would. Thanks for pointing that out.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
20 matches
Mail list logo
