Trent Nelson [EMAIL PROTECTED] added the comment:
I've attached a patch to test_tokenizer.py and a bunch of text files
(that should be dropped into Lib/test) that highlight this issue a
*lot* better than the current state of affairs.
The existing implementation defines roundup() in the
Trent Nelson [EMAIL PROTECTED] added the comment:
Hmm, I take it multiple file uploads aren't supported. I don't want to
use svn diff for the text files as it looks like it's butchering the
bom encodings, so, tar it is! (Untar in root py3k/ directory.)
Added file:
Georg Brandl [EMAIL PROTECTED] added the comment:
Okay to close this, then?
--
nosy: +georg.brandl
resolution: - wont fix
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2278
__
Changes by Georg Brandl [EMAIL PROTECTED]:
--
assignee: - georg.brandl
nosy: +georg.brandl
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2176
__
___
Python-bugs-list
New submission from Per Cederqvist [EMAIL PROTECTED]:
If TimedRotatingFileHandler is instructed to roll over the log at
midnight or on a certain weekday, it needs to consider when daylight
savings time starts and ends. The current code just blindly adds
self.interval to self.rolloverAt, totally
Tim Golden [EMAIL PROTECTED] added the comment:
Gabriel Genellina wrote:
Gabriel Genellina [EMAIL PROTECTED] added the comment:
You aren't testing the modified code, the Popen call should say
shell=True.
I think that a more PEP8-compliant style would be nice (removing the
spaces after
New submission from Per Cederqvist [EMAIL PROTECTED]:
If nothing is logged during an interval, the TimedRotatingFileHandler
will give bad names to future log files.
The enclosed example program sets up a logger that rotates the log every
second. It then logs a few messages with sleep of 1, 2,
Per Cederqvist [EMAIL PROTECTED] added the comment:
The attached program will generate log messages with a timestamp that
are logged into a file with an unexpected extension.
To run:
mkdir badlogdir
python badlogger.py
Running the program takes about 9 seconds.
Added file:
Changes by Per Cederqvist [EMAIL PROTECTED]:
--
components: +Library (Lib)
type: - behavior
versions: +Python 2.5
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2316
__
New submission from Per Cederqvist [EMAIL PROTECTED]:
There are three issues with log file removal in the
TimedRotatingFileHandler class:
- Removal will stop working in the year 2100, as the code assumes that
timestamps start with .20.
- If you run an application with backupCount set to a
New submission from Per Cederqvist [EMAIL PROTECTED]:
In my curent project, I would like to rotate log files on the 1st of
every month. The TimedRotatingFileHandler class cannot do this, even
though it tries to be very generic.
I imagine that other projects would like to rotate the log file
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment:
Hello. I tracked down source code and found where err-text is set.
Index: Parser/parsetok.c
===
--- Parser/parsetok.c (revision 61411)
+++ Parser/parsetok.c (working copy)
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
The following Works for me:
import imp, cPickle
mymod = imp.load_module('mymod', *imp.find_module('codecs'))
cPickle.dumps(mymod.Codec(), cPickle.HIGHEST_PROTOCOL)
'\x80\x02(cmymod\nCodec\nq\x01o}q\x02b.'
Do you have a short test
New submission from Ralf Schmitt [EMAIL PROTECTED]:
The following short program raises an exception:
import UserList
class C:
pass
print isinstance(C, UserList.UserList)
-
exception:
Traceback (most recent call last):
File t.py, line 6, in module
print isinstance(C,
Ralf Schmitt [EMAIL PROTECTED] added the comment:
I used svn revision 61433.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2319
__
___
Python-bugs-list mailing list
Eric Smith [EMAIL PROTECTED] added the comment:
Fixed checked in as r61434.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2264
__
Martin v. Löwis [EMAIL PROTECTED] added the comment:
You are probably right about the source of the problem; I was confusing
it with a regular exception, e.g.
print(年,a)
However, I also fail to reproduce the problem on OSX. I get
File a.py, line 3
print �N
^
SyntaxError:
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
This was duplicated in issue726204 and fixed in r37026.
--
nosy: +belopolsky
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue448736
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
A related issue419070 was closed with no resolution (or resolution did
not survive the trip from SF), but it looks like the patch was rejected.
Some work towards this issue was done in r21437, but 7 years later it is
still marked as
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment:
I was confusing it with a regular exception, e.g.
print(年,a)
I'm now invesigating this problem. This comes from another reason.
Please look at fp_setreadl in Parser/tokenizer.c.
This function opens file using codec and doesn't seek to
New submission from Ludwig Hähne [EMAIL PROTECTED]:
Pythons subprocess module has a race condition when stdin is used. The
problem can be reproduced with the following script (based on the script
in issue #1731717/msg32210 (slightly changed to use stdin):
import sys, os, threading,
Guido van Rossum [EMAIL PROTECTED] added the comment:
Any progress?
--
nosy: +gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1950
__
___
Python-bugs-list
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment:
However, I also fail to reproduce the problem on OSX. I get
File a.py, line 3
print �N
^
SyntaxError: invalid syntax
Umm, strange... I can output correct result even if
using euc_jp (my terminal named command prompt
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Unless noted, none of Python's stdlib guarantees that it's thread safe.
So , you have to lock.
--
nosy: +benjamin.peterson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2320
Alexandre Vassalotti [EMAIL PROTECTED] added the comment:
Yes, that sounds like a good idea. Although I haven't reviewed this
patch yet, I find the naming of the `ustr` variable confusing -- e.g. is
it a bytes object or a unicode object? (It seems to be bytes). Anyway, I
will check this out
Amiga Lemming [EMAIL PROTECTED] added the comment:
On Mon, 17 Mar 2008, Alexander Belopolsky wrote:
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
A related issue419070 was closed with no resolution (or resolution did
not survive the trip from SF), but it looks like the patch was
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
This depends on issue433024 (SRE: (?flag) isn't properly scoped.)
--
nosy: +belopolsky
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue433027
Changes by Barry A. Warsaw [EMAIL PROTECTED]:
--
versions: +Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
___
Python-bugs-list mailing list
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
This is still a valid issue. (As of Python 2.6a1+ (trunk:61434, Mar 17
2008, 08:06:54).)
bool(re.match(abc(?i),AbC))
True
The documentation says that the behavior of a regex with (?letter) not
at the beginning is undefined.
Short of
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment:
I'm now invesigating this problem. This comes from another reason.
Of course, even if this line number problem is fixed, encoding
problem still remains. Probably I'll look at it next.
__
Tracker [EMAIL
Jeffrey Yasskin [EMAIL PROTECTED] added the comment:
I've fixed this in r61436 with a bunch of back pointers to the previous
issues. If anyone on old versions sees problems, we can add the flags
back conditionally.
--
resolution: accepted - fixed
status: open - closed
type: - compile
Brett Cannon [EMAIL PROTECTED] added the comment:
On Sun, Mar 16, 2008 at 4:27 PM, Guido van Rossum
[EMAIL PROTECTED] wrote:
New submission from Guido van Rossum [EMAIL PROTECTED]:
We should keep the ACKS files up to date. Have all the GHOP contributors
been added?
They have been added
Jeffrey Yasskin [EMAIL PROTECTED] added the comment:
I reverted this in r61436 to fix issue 1779871. The long double is still
around, but the gcc bundled with OS X 10.4 doesn't warn about it anymore.
--
nosy: +jyasskin
Tracker [EMAIL PROTECTED]
Guido van Rossum [EMAIL PROTECTED] added the comment:
So what's the syntax for setting multiple attributes via an email subject?
[assignee=+twouters,priority=low]?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
Jeffrey Yasskin [EMAIL PROTECTED] added the comment:
I reverted this in r61436 to fix issue 1779871. Either the test has
changed in the mean time, or the gccs bundled since OS X 10.4 now
preserve the signs of 0.
--
nosy: +jyasskin
Tracker [EMAIL
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
If any work needs to be done on this issue, it should probably be
labeled easy. (At least the writing the unit tests part. Making
... reprs consistent is another story.)
The unit tests for old-style and new-style class reprs are
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
On Mon, Mar 17, 2008 at 9:51 AM, Alexandre Vassalotti
[EMAIL PROTECTED] wrote:
Alexandre Vassalotti [EMAIL PROTECTED] added the comment:
.. Although I haven't reviewed this
patch yet, I find the naming of the `ustr` variable
New submission from Neal Norwitz [EMAIL PROTECTED]:
This patch returns more memory to the system when doing:
x = [unicode(i) for i in xrange(100)]
del x
If the above code is done, the memory before and after is quite
different. After this patch, the memory of the process as reported
Gregory P. Smith [EMAIL PROTECTED] added the comment:
I updated the subject to better reflect what this is.
My guess is that the test code itself has issues and is asserting
something that isn't quite guaranteed to be true.
--
title: py3k-pep3137: failing unit test test_bsddb -
Guido van Rossum [EMAIL PROTECTED] added the comment:
Picky!
--
assignee: gvanrossum - nnorwitz
nosy: +twouters
priority: immediate - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
Guido van Rossum [EMAIL PROTECTED] added the comment:
[assignee=guido]
Does it also work in the body of the message?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
___
Guido van Rossum [EMAIL PROTECTED] added the comment:
No.
--
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
___
Python-bugs-list mailing
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Guido van Rossum schrieb:
Guido van Rossum [EMAIL PROTECTED] added the comment:
So what's the syntax for setting multiple attributes via an email subject?
[assignee=+twouters,priority=low]?
assignee is not multilink, and the separator is
Jeff Balogh [EMAIL PROTECTED] added the comment:
Attaching a patch that fixes this issue and adds a regression test.
--
keywords: +patch
nosy: +jbalogh
Added file: http://bugs.python.org/file9690/issue2282.diff
__
Tracker [EMAIL PROTECTED]
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
nosy: +gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2282
__
___
Python-bugs-list mailing list
A.M. Kuchling [EMAIL PROTECTED] added the comment:
I intend to finish writing the 2.6 document; PyCon has been taking up
all of my free time the past few weeks, but obviously that's over now.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2305
Guido van Rossum [EMAIL PROTECTED] added the comment:
I'd rather not label this as easy yet, since there's a decision to be
made. I would welcome a doc patch though!
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue868845
Guido van Rossum [EMAIL PROTECTED] added the comment:
Confirmed. Ping, since you're looking at io.py anyway, can you fix this
too?
--
assignee: - ping
nosy: +ping
priority: - high
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2282
Gregory P. Smith [EMAIL PROTECTED] added the comment:
working on this now. foo = 'abcdefghijklmnop'
2.x 32-bit long: zlib.crc32(foo) returns -1808088941
2.x 64-bit long: zlib.crc32(foo) returns 2486878355
This is because PyInt_FromLong() happily fits the value into a signed
long internally to
New submission from Brett Cannon [EMAIL PROTECTED]:
It was mentioned by Georg on python-3000 that getargs.c needs to be
cleaned up and worked on before Python 3.0 goes out the door.
--
assignee: georg.brandl
components: Interpreter Core
messages: 63665
nosy: brett.cannon, georg.brandl
Changes by Guido van Rossum [EMAIL PROTECTED]:
--
assignee: georg.brandl - akuchling
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2305
__
___
Python-bugs-list mailing
Gregory P. Smith [EMAIL PROTECTED] added the comment:
question: should I also make 64-bit 2.x return a signed value as well to
be consistent with 32bit python 2.x?
Consistency in case someone ever pickles the value and sends it to
another python instance of a different word length would be
New submission from Brett Cannon [EMAIL PROTECTED]:
structseq and namedtuple should end up with a uniformed API.
--
components: Extension Modules
messages: 63667
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Unify structseq and namedtuple's API
versions:
Guido van Rossum [EMAIL PROTECTED] added the comment:
Sure. (Though sending pickles to 3.0 would still cause problems.
Consumers of pickled checksums would do wise to *always* take the CRC
mod 2**32 before doing comparisons.)
__
Tracker [EMAIL PROTECTED]
New submission from Brett Cannon [EMAIL PROTECTED]:
It turns out that unpickling a string from 2.6 leads to a Unicode string
in 3.0. That might fail since the encoding was never specified. This
should be documented probably in both 2.6 and 3.0.
--
assignee: georg.brandl
components:
Jeffrey Yasskin [EMAIL PROTECTED] added the comment:
Missed this. It's now fixed by r61438.
--
nosy: +jyasskin
status: open - closed
type: crash - behavior
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2319
__
New submission from Jeffrey Yasskin [EMAIL PROTECTED]:
class Meta(type):
... def __instancecheck__(self, other):
... return False
isinstance(3, Meta)
In 2.6, this results in:
Traceback (most recent call last):
File stdin, line 1, in module
RuntimeError: maximum recursion depth
New submission from Brett Cannon [EMAIL PROTECTED]:
Both the isnumeric and isdecimal methods on the unicode object need to
be documented.
--
assignee: georg.brandl
components: Documentation
messages: 63672
nosy: brett.cannon, georg.brandl
priority: immediate
severity: normal
status:
Sean Reifschneider [EMAIL PROTECTED] added the comment:
Patch is inline.
A few notes for submitter:
This also needs to include a documentation patch before it can be accepted.
Please format the docstring for a line length of 78 characters or less.
Ideally, please submit a diff -c style patch
Alec Thomas [EMAIL PROTECTED] added the comment:
Hi Neal,
This seems to be a more general problem than just unicode.
eg. Tuples:
x = [(1, 2, 3, 4, i) for i in xrange(80)]
del x
And user-defined objects:
class A(object):
... def __init__(self):
... self.x = random.random()
x =
New submission from Sean Reifschneider [EMAIL PROTECTED]:
No body included in original message.
--
assignee: - loewis
nosy: +jafo, loewis
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1230
Changes by Sean Reifschneider [EMAIL PROTECTED]:
--
assignee: - niemeyer
nosy: +niemeyer
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1250
__
___
Changes by Sean Reifschneider [EMAIL PROTECTED]:
--
type: behavior - feature request
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1230
__
___
Python-bugs-list mailing
Jesús Cea Avión [EMAIL PROTECTED] added the comment:
I store CRC in reed-solomon schema of mine. I compare with equality, so,
I think we should enforce CRC(python 32 bits) == CRC(python 64 bits).
I will need to touch my code in python 3.0, but that will be inevitable
anyway...
Guido van Rossum [EMAIL PROTECTED] added the comment:
The issue is different; there is already a bug open for this (bug 2307).
--
nosy: +gvanrossum
resolution: - invalid
status: open - closed
superseder: - Decide what to do with bytes/str when transferring pickles
between 2.6 and 3.0
Guido van Rossum [EMAIL PROTECTED] added the comment:
We have a proposed solution for 2.x - 3.x. In 3.x, an (8-bit) str
instance received from 2.x will be decoded into a (Unicode) str
instance. The encoding defaults to ASCII; you can specify a different
encoding and also an error value on the
New submission from Brett Cannon [EMAIL PROTECTED]:
Keyword-only arguments have not been backported to 2.6 from 3.0.
--
components: Interpreter Core
keywords: 26backport
messages: 63679
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Backport keyword-only
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
I think the attached patch captures the most of what can currently be
said about ... reprs.
I think the biggest offender in terms of inconsistency in the 2.x series
is the file object with the repr which does not even start with the
New submission from Jack Diederich [EMAIL PROTECTED]:
typeobject.c:type_new only allows 0 or 1 keyword arg in class creation
instead of an arbitrary number as per PEP3115.
I'm working on a patch.
--
assignee: jackdied
components: Interpreter Core
messages: 63681
nosy: jackdied
New submission from dd [EMAIL PROTECTED]:
Installation from source, python.2.4.5.tgz.
It seems that severals *.so from bsddb are missing:
import bsddb
Traceback (most recent call last):
File stdin, line 1, in ?
File /tmp/Python-2.4.5/Lib/bsddb/__init__.py, line 47, in ?
import _bsddb
Steven Bethard [EMAIL PROTECTED] added the comment:
I'll take care of this, adding a bit to section 3.6.1, String Methods.
--
nosy: +bethard
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2326
__
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
There is now issue2322 (Clean up getargs.c and its formatting
possibilities) related to this.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2298
__
Paul Winkler [EMAIL PROTECTED] added the comment:
I'm working on this (at the pycon sprint).
--
nosy: +slinkp
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1180
__
___
New submission from Guido van Rossum [EMAIL PROTECTED]:
Barry, can you update the PEP with a discussion of the schedule, so we
can refer to it?
--
assignee: barry
components: Documentation
messages: 63686
nosy: barry, gvanrossum
priority: urgent
severity: normal
status: open
title:
Sean Reifschneider [EMAIL PROTECTED] added the comment:
We've discussed this at the PyCon sprints, and here's the concensus:
os.popen inherits the parents stderr, and on Windows there is not an
existing valid stderr by default. So the parent should, to be
compatible with the Windows
New submission from Brett Cannon [EMAIL PROTECTED]:
Parameter annotations (e.g., ``def fxn(a:int) - str: pass`` need to be
backported.
--
components: Interpreter Core
keywords: 26backport
messages: 63688
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title:
New submission from Brett Cannon [EMAIL PROTECTED]:
It should be double-checked that the renaming of attributes from
functions has been completed.
--
assignee: nnorwitz
components: Interpreter Core
keywords: 26backport
messages: 63689
nosy: brett.cannon, nnorwitz
priority: immediate
New submission from Brett Cannon [EMAIL PROTECTED]:
Dict comprehensions need to be backported.
--
components: Interpreter Core
keywords: 26backport
messages: 63690
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Backport dict comprehensions
type: behavior
New submission from Brett Cannon [EMAIL PROTECTED]:
Set comprehensions need to be backported.
--
components: Interpreter Core
keywords: 26backport
messages: 63691
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Backport set comprehensions
versions: Python 2.6
New submission from Brett Cannon [EMAIL PROTECTED]:
Set literals need to be backported.
--
components: Interpreter Core
keywords: 26backport
messages: 63692
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Backport set literals
type: behavior
versions: Python
New submission from Brett Cannon [EMAIL PROTECTED]:
oct() and hex() need to use __index__ when available and then emit a
Py3K warning when they fall back on __oct__ and __hex__.
--
components: Interpreter Core
keywords: 26backport
messages: 63695
nosy: brett.cannon
priority: immediate
Sean Reifschneider [EMAIL PROTECTED] added the comment:
Marc-Andre: Is this good to be committed, or does it need to be reviewed
further?
--
assignee: - lemburg
nosy: +jafo
priority: - normal
__
Tracker [EMAIL PROTECTED]
New submission from Brett Cannon [EMAIL PROTECTED]:
A fixer to change calls from reload() to imp.reload() needs to happen.
Plus imp.reload() should come into existence.
--
assignee: collinwinter
components: 2to3 (2.x to 3.0 conversion tool)
keywords: 26backport
messages: 63697
nosy:
New submission from Brett Cannon [EMAIL PROTECTED]:
intern() needs to be added as sys.intern(). Then a 2to3 fixer needs to
be written.
--
components: Interpreter Core
keywords: 26backport
messages: 63698
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title:
Changes by Brett Cannon [EMAIL PROTECTED]:
--
components: +Interpreter Core -2to3 (2.x to 3.0 conversion tool)
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2338
__
New submission from Brett Cannon [EMAIL PROTECTED]:
PEP 3132 (extended iterable unpacking) needs to be backported.
--
components: Interpreter Core
keywords: 26backport
messages: 63699
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Backport PEP 3132 (extended
New submission from Brett Cannon [EMAIL PROTECTED]:
PEP 3114 needs to be backported. Most likely the best approach is to
backport the next() built-in but to have it call next() on the iterator
instead of __next__(). That should hopefully minimize breakage while
allowing for moving over to the
Changes by Brett Cannon [EMAIL PROTECTED]:
--
priority: - immediate
title: Catching all exceptions with 'object' - Raise a Py3K warning for
catching non-BaseException exceptions
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2291
New submission from Brett Cannon [EMAIL PROTECTED]:
Raising exceptions that do not inherit from BaseException (e.g., classic
classes) should raise a Py3K warning.
--
components: Interpreter Core
keywords: 26backport
messages: 63700
nosy: brett.cannon
priority: immediate
severity: normal
Raymond Hettinger [EMAIL PROTECTED] added the comment:
I don't think this should be backported. It leaves Py2.6 with a
confused mess of protocols. The 2-to-3 transformation is simple.
Backporting doesn't add value.
--
nosy: +rhettinger
__
Tracker
New submission from Brett Cannon [EMAIL PROTECTED]:
When you compare disparate types through something other than == and !=
a Py3K warning should be raised.
--
components: Interpreter Core
keywords: 26backport
messages: 63702
nosy: brett.cannon
priority: immediate
severity: normal
New submission from Brett Cannon [EMAIL PROTECTED]:
Using a float where an int should only be used (e.g., ``[].insert(.5,
0)``) should raise a Py3K warning.
--
components: Interpreter Core
keywords: 26backport
messages: 63704
nosy: brett.cannon
priority: immediate
severity: normal
Sean Reifschneider [EMAIL PROTECTED] added the comment:
It sounds like the Unicode FAQ has an authoritative statement on this,
is this a wontfix, or does this need more discussion? Perhaps on
python-dev or at the sprints this week?
--
assignee: - doerwalter
nosy: +jafo
priority: -
New submission from Brett Cannon [EMAIL PROTECTED]:
If you use a iteration variable from a list comprehension from outside
the list comprehension itself should raise a Py3K warning.
--
components: Interpreter Core
keywords: 26backport
messages: 63706
nosy: brett.cannon
priority:
Domen [EMAIL PROTECTED] added the comment:
The lib should give programmer choice wether to send login through TLS
or not. (as it is described in RFC 4217).
Also, there should be an optional parameter to specify port for ftp
connection.
--
nosy: +iElectric
New submission from Brett Cannon [EMAIL PROTECTED]:
If one tries to use an exception bound to a variable in an 'except'
clause it should raise a Py3K warning.
--
components: Interpreter Core
keywords: 26backport
messages: 63708
nosy: brett.cannon
priority: immediate
severity: normal
Steven Bethard [EMAIL PROTECTED] added the comment:
I've got a patch against 2.6, and the docs seem to build fine. Since
I've never committed a doc patch before, I'd appreciate it if someone
could glance at this and make sure there's nothing obviously wrong.
--
keywords: +patch
Added
Alec Thomas [EMAIL PROTECTED] added the comment:
Alec, can you find places that are using the PyMem_* interface and
create a patch to fix them. That would be great!
Sure thing! I'll see if I can finish it today, but if not I'll work on
it during the flight to Zurich tonight.
Gregor Lingl [EMAIL PROTECTED] added the comment:
This version runs under Python 2.5 and should run under python 2.6 It
still needs some amendments and polishing concerning the code as well as
the docstrings. Here it can serve as a starting point for a discussion
about necessary and/or desirable
Changes by Gregor Lingl [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file9694/xturtle-docs.txt
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1513695
_
___
1 - 100 of 356 matches
Mail list logo