Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
assignee: brett.cannon -> rhettinger
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2349>
__
___
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Fixed in revision 61651.
--
nosy: +brett.cannon
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
assignee: -> brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2227>
__
___
Python-b
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Is there any other place where this might be an issue? That's the real
question; are all reasonable cases covered.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
assignee: -> brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2343>
__
___
Python-b
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Is there a short-term solution we can come up with?
Unfortunately stat'ing for the existence of .bzr is not easy since there
is no platform-independent solution (as posixmodule.c shows). Should some
default values be used?
New submission from Brett Cannon <[EMAIL PROTECTED]>:
The magic cookie as returned by imp.get_magic() should be of the bytes
type, not bytearray as the magic cookie will not ever change during the
execution of the interpreter.
--
components: Extension Modules
messages: 6439
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I agree with Georg; a 2to3 fixer is enough.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2357>
__
__
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On another note, the warnings module should be made to work with or
without _warnings. that way IronPython, Jython, and PyPy won't have to re-
implement stuff. This also means that test cases need to be changed to
Brett Cannon <[EMAIL PROTECTED]> added the comment:
After all the threats about checking in code that break stuff, I am not
about to check this in. =)
I will get to the changes when I can and then commit after the alpha.
--
assignee: nnorwitz -> bre
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Neal's issues are addressed in this patch. I also finally filled out
warnings.h. The only thing that I didn't deal with is Neal's worry of
exposing _PyWarnings_Init(). It is not explicitly exported anywhere as
part o
Changes by Brett Cannon <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file9761/c_warnings.diff
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Changes by Brett Cannon <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file9917/c_warnings.diff
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Attached should have everything, including a pure Python fallback. As soon
as the next alpha is out I will apply.
--
status: open -> pending
Added file: http://bugs.python.org/file9920/c_warn
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Neal has the memory of an elephant or something.
Yes, I dealt with a similar issue where the recursion limit was hit, but
then normalizing the exception just caused it to hit it again. I thought
I changed it such that normaliz
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Committed in revision 62303.
--
resolution: -> accepted
status: pending -> closed
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I am going to assign this to me, but wait until Guido pronounces on PEP
3108 before moving forward with a review.
--
assignee: -> brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Closed at Doug's request. My importlib work, once it lands, will supplant
all of this.
--
resolution: -> rejected
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
New submission from Brett Cannon <[EMAIL PROTECTED]>:
The new warnings implementation tweaks how tracebacks are printed. This
introduced a bug where the exception name is indented when it shouldn't
be: e.g., ``raise KeyError`` should look like::
Traceback (most recent call last
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Forgot to mention this is probably from Python/traceback.c:tb_displayline().
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Brett Cannon <[EMAIL PROTECTED]> added the comment:
@Georg:
That is a possibility. Would need to add the proper Py3K warning to the
current builtins, though.
@Benjamin:
You don't want to warn if it will work for Py3K, so don't warn if
_
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Yep. I already did that and ran the unit test suite to verify. Now I am
just trying to figure out how to best test it. It seems it only comes up
for printing a traceback. That would mean either using subprocess to run
another interpret
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Sun, Apr 27, 2008 at 2:34 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
> Georg Brandl <[EMAIL PROTECTED]> added the comment:
>
> You could add a function to the _testcapi module to invoke PyErr_Display.
&
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I have emailed python-dev to try to decide how to handle this.
--
assignee: -> brett.cannon
nosy: +brett.cannon
priority: -> critical
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
priority: critical -> release blocker
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2705>
__
___
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Fix in revision 62555.
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
New submission from Brett Cannon <[EMAIL PROTECTED]>:
There is carbon-specific code in binhex. It really should go so that the
module is completely platform-independent. This is especially pertinent
for 3.0 as all Mac-specific modules are slated to go.
--
components: Librar
New submission from Brett Cannon <[EMAIL PROTECTED]>:
The audioop module contains a comment that is somewhat troubling from an
IP standpoint:
/* Code shamelessly stolen from sox, 12.17.7, g711.c
** (c) Craig Reese, Joe Campbell and Jeff Poskanzer 1989 */
Because of this it would b
Brett Cannon <[EMAIL PROTECTED]> added the comment:
If Raymond says it's fine, then it's also fine by me.
--
assignee: brett.cannon -> benjamin.peterson
__
Tracker <[EMAIL PROTECTED]>
<http
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Closing as out of date since it seems to have already been handled.
--
resolution: -> out of date
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Fixed in r62626. I left in the optional arguments but they are just not
called anymore by the 'warnings' machinery. I might add a
PendingDeprecationWarning so that people start to add the argument,
though
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Thu, May 1, 2008 at 7:29 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> Why don't you add a Py3k warning and keep it in Py3k?
Just ask
New submission from Brett Cannon <[EMAIL PROTECTED]>:
In svn, the module name is lost if you raise an exception at the
interpreter::
>>> import warnings
>>> warnings.warn("foo")
:1: UserWarning: foo
It should be::
>>> import warnings
>&g
Brett Cannon <[EMAIL PROTECTED]> added the comment:
So I found the problem. The C implementation of 'warnings' is not handling
the case where the module that triggered the exception does not define
__file__, __name__ == '__main__', and sys.argv[0] is a false val
Brett Cannon <[EMAIL PROTECTED]> added the comment:
r62656 has the fix.
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Sat, May 3, 2008 at 1:36 AM, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> Ronald Oussoren <[EMAIL PROTECTED]> added the comment:
>
> Have you read that code?
Not in detail, no.
> The Carbon-specific c
Brett Cannon <[EMAIL PROTECTED]> added the comment:
A key thing to realize is that test_cprofile has heavily changed in
2.6 compared to what is currently disabled in 3.0.
--
nosy: +brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http://
New submission from Brett Cannon <[EMAIL PROTECTED]>:
In order to move the warnings.showwarning() API forward to support the new
'line' argument, a DeprecationWarning is needed for implementations that
lack support for it.
>From the Python side a simple check for the &#
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Sat, May 3, 2008 at 2:11 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> Brett, can you list the places showwarning is used?
>
Lib/warni
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
keywords: +patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2750>
__
___
Python-bugs
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
priority: -> critical
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2750>
__
___
Python-b
Brett Cannon <[EMAIL PROTECTED]> added the comment:
The most critical steps are to get the code building and to get the tests
passing. Once that is working the code can be checked in and the other
steps (docs, PEP 7/8, 3.0 conversion) can happen after the fact.
--
nosy: +brett.
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Sat, May 3, 2008 at 3:19 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
>
> Christian Heimes <[EMAIL PROTECTED]> added the comment:
>
> Yeah, either make a bzr branch or an ordinary svn branch. If you need
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Branch is at http://code.python.org/python/users/brett/issue2750-
simplejson/ .
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Just so it is documented, Bob said on IRC that we do not need to keep
compatibility with any specific version of Python.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
priority: normal -> critical
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1563>
__
___
Pyt
Brett Cannon <[EMAIL PROTECTED]> added the comment:
One problem with the way the patch is now is that it will fail on non-
CPython interpreters the way it is currently coded. For instance,
json/decoder.py completely assumes that importing _json will succeed. Same
with the test suite.
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Ouch. Well then hopefully either they will get implemented or some way to
not rely on them can be developed.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Brett Cannon <[EMAIL PROTECTED]> added the comment:
This is separate from issue1563, right?
--
nosy: +brett.cannon
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Brett Cannon <[EMAIL PROTECTED]> added the comment:
r62720 and r62722 have the fix (and a fix for the fix). In the Python code
I check for an argument named 'line' and in the C code I make sure there
are at least two default arguments. Both assume a Python implementation
Brett Cannon <[EMAIL PROTECTED]> added the comment:
So there is one failing test because json.dumps() tacks on extraneous
whitespace. When you run the file through reindent it strips out the
whitespace from the docstring, causing doctest to fail.
Trying to
Brett Cannon <[EMAIL PROTECTED]> added the comment:
r62734 has it in the trunk. I had to change a doctest to use repr() in
order to get around the extraneous whitespace that pretty-printing spits
out, but otherwise I only added a Misc/NEWS entry.
__
T
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I am leaving this issue open until 'json' is ported to 3.0 (and thus why I
am assigning this to Christian).
--
assignee: benjamin.peterson -> christian.heimes
__
Tracker <[E
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
versions: -Python 2.6
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2750>
__
___
Python-bugs
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Alexandre, you have until the end of the week to commit it or someone else
will. =) I don't want this going in so close to the alphas, but it should
go in almost immediately afterwards.
__
Trac
New submission from Brett Cannon <[EMAIL PROTECTED]>:
This is to keep track of who is working on what for PEP 3108
(http://www.python.org/dev/peps/pep-3108/). Once something is complete it
should be denoted in the PEP itself, so always check the PEP to see what
is left to be done (fo
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
assignee: -> brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2775>
__
___
Python-b
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I am working on audiodev to get the basic structure of removals worked out
(testing infrastructure, etc.).
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Brett Cannon <[EMAIL PROTECTED]> added the comment:
For the TextMate users, I am going to be checking in a Python-Dev bundle
into svn soon which will include a command to insert the warnpy3k() call
for module deletions. Might want to wait for that if you want to cut out
at least one co
Brett Cannon <[EMAIL PROTECTED]> added the comment:
If you use TextMate, get the Python-Dev bundle and use the command in
there to insert the deprecation boilerplate for removing a module.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2775>
__
___
Python-bugs-list mailin
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Ralf, can you do a ``make clean`` and then try again? I had this happen to
me with an old checkout until I did that and then everything worked fine.
__
Tracker <[EMAIL PROTECTED]>
<http://
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Fixed in r62896.
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I didn't use sizeof because I didn't think of it; the solution to just
change the numbers was right in front of me and I am swamped with other
work so I went with what I knew would work.
As for removing the array, perhaps,
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Sat, May 10, 2008 at 12:29 PM, Jesse Noller <[EMAIL PROTECTED]> wrote:
>
> Jesse Noller <[EMAIL PROTECTED]> added the comment:
>
> Should DocXMLRPCServer.py be moved into xmlrpc/ as well?
Yes, and end up in th
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Just so people know, I have emailed python-dev about renaming urllib as I
realized there are some issues with the solution proposed in the PEP.
--
priority: critical -> release blocker
_
New submission from Brett Cannon <[EMAIL PROTECTED]>:
Doc/library/undoc.rst needs to be cleaned up once PEP 3108 has been
implemented.
--
assignee: brett.cannon
components: Documentation
keywords: easy
messages: 66694
nosy: brett.cannon
priority: normal
severity: normal
status
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
dependencies: +Implement PEP 3108
priority: normal -> high
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Just so people know, feel free to create new issues for stuff if you want.
Other issues can be made dependencies of this issue very easily.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Brett Cannon <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10257/queue_rename.patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Brett Cannon <[EMAIL PROTECTED]>:
cgi.parse_qs() really belongs more in urllib.parse. Move it so that people
no longer have to import cgi just for that one function.
--
assignee: brett.cannon
components: Library (Lib)
messages: 66703
nosy: brett.cannon
pr
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
assignee: brett.cannon ->
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2829>
__
___
Python-b
New submission from Brett Cannon <[EMAIL PROTECTED]>:
cgi.escape() really belong in the new 'html' package.
--
components: Library (Lib)
messages: 66704
nosy: brett.cannon
priority: normal
severity: normal
status: open
title: Copy cgi.escape() to html
type: feature
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Tue, Oct 14, 2008 at 11:05 PM, Martin v. Löwis
<[EMAIL PROTECTED]> wrote:
>
> Martin v. Löwis <[EMAIL PROTECTED]> added the comment:
>
> The patch looks fine to me, please apply.
>
Great!
> I notice t
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Sorry about that; been one of those days.
Doing a svn up and making sure it still compiles fine.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Applied in r66951.
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Looks like sqlite3 was not compiled for you. To verify, run ``make``
again and note what modules it lists at the very end as not built. I bet
it lists sqlite3 there.
--
nosy: +brett.cannon
title: import of sqlite3 fails -> co
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Obviously the big problem with that change, Benjamin, is you will be
changing the semantics. And that is a tough thing to change when it
involves the warning machinery itself so emitting a warning about a
warning might get
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Wed, Oct 22, 2008 at 3:39 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> Oh, do we not consider __warningsregistry__ an implementation detail
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Wed, Oct 22, 2008 at 4:11 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> A simple solution would be to allow warn_explicit to be overridden.
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Fri, Oct 24, 2008 at 5:27 AM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
>
> Guilherme Polo <[EMAIL PROTECTED]> added the comment:
>
> Now that the new branches are around I guess we could consider adding it
>
New submission from Brett Cannon <[EMAIL PROTECTED]>:
If you import a frozen package (e.g. __phello__), __path__ is set to
'__phello__'. But this should be a list as specified by both PEP 302
(http://www.python.org/dev/peps/pep-0302/) and the original doc
outlining the package
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Looking at Python/import.c:find_module, fixing this will require
changing the setting of __path__ for frozen packages and how frozen
modules are found. The former will require changing
PyImport_ImportFrozenModule() to use a list instea
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
nosy: +brett.cannon
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4242>
___
__
Brett Cannon <[EMAIL PROTECTED]> added the comment:
Based on your experience, Armin, is it worth having a class decorator as
well/instead?
The other comment I have is whether impl_detail is really the best name.
Would something like cpython work out better to be more obvious that the
t
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I have an attached patch that fixes the reported problem.
First, it adds a sanity check that no empty module name is checked for
(crashes the interpreter otherwise).
Second, the __path__ attribute is now a list. This does break
bac
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
stage: -> commit review
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4211>
___
__
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
nosy: +brett.cannon
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4262>
___
__
New submission from Brett Cannon <[EMAIL PROTECTED]>:
sys.version_info is just asking for a named tuple consisting of major,
minor, micro, releaselevel, and serial.
This is assuming, of course, that bootstrapping doesn't get in the way.
--
assignee: brett.cannon
components
Brett Hoerner <[EMAIL PROTECTED]> added the comment:
They have released the changes, that's what my patch (attached to the
issue) is based on.
It's working, it just needs to be cleaned up (it will fail, I believe,
for people on systems without DTrace - as I said I'm n
Brett Hoerner <[EMAIL PROTECTED]> added the comment:
On Wed, Nov 12, 2008 at 9:31 PM, Skip Montanaro <[EMAIL PROTECTED]> wrote:
> I see the reference to Apple in your original post, but can't find anything
> related to dtrace & python starting from the URL you gave. D
Brett Cannon <[EMAIL PROTECTED]> added the comment:
On Thu, Nov 13, 2008 at 08:05, Skip Montanaro <[EMAIL PROTECTED]> wrote:
>
> Skip Montanaro <[EMAIL PROTECTED]> added the comment:
>
> Brett> http://www.opensource.apple.com/darwinsource/10.5.5/python-30.
Changes by Brett Cannon <[EMAIL PROTECTED]>:
--
versions: +Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2306>
___
__
Brett Cannon <[EMAIL PROTECTED]> added the comment:
make_sure_to_copy.patch seems fine short of adding a comment to the test
referencing this issue.
--
assignee: -> benjamin.peterson
nosy: +brett.cannon
___
Python tracker <[EMAIL PROTE
Brett Cannon <[EMAIL PROTECTED]> added the comment:
And it turns out I should have looked at the other patch instead. =)
The missing comment from the test still holds. I also think you did not
need to cut out the fast path from translate as much as you did when
there is no deletion. It&#
Brett Cannon <[EMAIL PROTECTED]> added the comment:
So if you look at Python/pythonrun.c, there is a comment from Tim Peters
(from r34776) where he explicitly points out that this is possibility
but that it has never been reported before. Oops. =)
--
nosy: +brett.
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I don't think there is anything to fix here beyond the docs for __del__.
You should never expect anything to be working in __del__, and that
includes the import machinery. It should be bare-bones, not trying to
pull in new co
Brett Cannon <[EMAIL PROTECTED]> added the comment:
If you look at the 2.7 code all it requires of keys and values in
__setitem__ is that they are strings; there is nothing about Latin-1 in
terms of specific encoding (must be a 3.0 addition to make the
str/unicode transition the easiest)
Brett Cannon <[EMAIL PROTECTED]> added the comment:
OK, now I see why it is called 'dumb'; the thing literally just dumps
out the repr of two strings on each line for key/value pairs. To read it
just evals each line in the string. And whichdb detects this format by
looking f
Brett Cannon <[EMAIL PROTECTED]> added the comment:
I have attached a file that does everything internally as UTF-8 but
reads and writes to disk as Latin-1. I added some unit tests to verify
that taking a character encoded in UTF-8 or as a string still works
properly regardless of wheth
1101 - 1200 of 5934 matches
Mail list logo
