Once the cron job works it magic, the updated PEP 343 should be available on
the website.
As far as I am aware, there aren't any more open issues, so it is once again
ready for BDFL pronouncement.
I also tinkered with the example naming a bit, and added a new example for the
nested context
Atsuo Ishimoto wrote:
I'm +0.1 for non-ASCII identifiers, although module names should remain
ASCII. ASCII identifiers might be encouraged, but as Martin said, it is
very useful for some groups of users.
Thanks for these data. This mostly reflects my experience with German
and French users:
On Sat, 2005-10-29 at 10:56 +0200, Martin v. Löwis wrote:
Atsuo Ishimoto wrote:
I'm +0.1 for non-ASCII identifiers, although module names should remain
ASCII. ASCII identifiers might be encouraged, but as Martin said, it is
very useful for some groups of users.
Thanks for these data.
Thanks for these data. This mostly reflects my experience with German
and French users: some people would like to use non-ASCII identifiers
if they could, other argue they never would as a matter of principle.
Of course, transliteration is more straight-forward.
FWIW, being French, I don't
FWIW, being French, I don't remember hearing any programmer wish (s)he
could use non-ASCII identifiers, in any programming language. But
arguably translitteration is very straight-forward (although a bit
lossless at times ;-)).
I think typeability and reproduceability should be weighted
Antoine Pitrou wrote:
FWIW, being French, I don't remember hearing any programmer wish (s)he
could use non-ASCII identifiers, in any programming language. But
arguably translitteration is very straight-forward (although a bit
lossless at times ;-)).
My canonical example is François Pinard,
Hello!
On Fri, Oct 28, 2005 at 09:29:09PM -0400, Tim Peters wrote:
- Finding out what's changed in your sandbox. Use svn status
svn diff uses locally saved copies of files. This increases speed by
trading for the disk space. It also decreases net traffic; that's important
for those who have
On 27 okt 2005, at 19.57, Martin v. Löwis wrote:
Michael Hudson wrote:
Do checkins to svn.python.org go to the python-checkins list already?
They do indeed - you should have received one commit message by now
(me testing whether committing works, on PEP 347).
Could the subject lines of
Simon Percivall wrote:
Could the subject lines of those messages please be changed to something
more informative? Having which files were changed in the subject seems
better than having only the new rev and the folders the files are in.
I'm neither sure whether that should be done, or whether
On Sat, 2005-10-29 at 12:44, Martin v. Löwis wrote:
What do others think? I personally found those long subject lines
listing all the changed files very ugly and unreadable.
Me too. At work our subject lines contain something like:
Subject: [SVN][reponame] checkin of r12345 -
On Friday 28 October 2005 21:29, Tim Peters wrote:
- Finding out what's changed in your sandbox. Use svn status
for that. Bonus: in return for creating zillions of admin files,
svn status
is a local operation (no network access required). Do svn status -u
to get, in addition, a
On Saturday 29 October 2005 15:40, [EMAIL PROTECTED] wrote:
Author: martin.v.loewis
Date: Sat Oct 29 21:40:21 2005
New Revision: 41352
Modified:
python/trunk/ (props changed)
python/trunk/.cvsignore
...
Add *.pyc to svn:ignore.
Add libpython*.a to .cvsignore and
Hello,
I have thought about freezing for some time, and I think that it is a
fundamental need - the need to know, sometimes, that objects aren't
going to change.
This is mostly the need of containers. dicts need to know that the
objects that are used as keys aren't going to change, because if
Hi,
FWIW, I opened a bug report on Subversion some time ago so that patterns
like *.pyc and *.pyo are ignored by default in Subversion. Feel free
to add comments or vote for the bug:
http://subversion.tigris.org/issues/show_bug.cgi?id=2415
Regards
Antoine.
That might be reasonable. I just noticed that it is convenient to do
svn propset svn:ignore -F .cvsignore .
Without a file, I wouldn't know how to edit the property, so I would
probably do
svn propget svn:ignore . ignores
vim ignores
svn propset svn:ignore -F ignores .
rm ignores
Noam Raphael [EMAIL PROTECTED] wrote:
Hello,
I have thought about freezing for some time, and I think that it is a
fundamental need - the need to know, sometimes, that objects aren't
going to change.
I agree with this point.
This is mostly the need of containers. dicts need to know
16 matches
Mail list logo
