Jesus Cea wrote:
> Good night everybody!.
>
> Working on the Python3.0 support for bsddb I see that "Py_FindMethod"
> was just removed in Python last beta.
>
> Most uses of "Py_FindMethod" can be resolved as (as far as I know):
>
> 1. Delete the getattr routine.
> 2. Put a "0" in the getattr slot i
2008/7/21 Jesus Cea <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Trying to find why I can't import bsddb in python3.0, I have found that
> this code fails:
>
> """
> ~/* Some magic to make DBNotFoundError and DBKeyEmptyError derive
> ~ * from both DBError and K
In a debug-build 3k, do this (32-bit machine):
Python 3.0b2+ (py3k:65171M, Jul 21 2008, 20:08:20)
[GCC 4.2.4 (Gentoo 4.2.4 p1.0)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> "a"*10
instinstTraceback (most recent call last):
File "", line 1, in
M
Mark Hammond wrote:
...
>
> It seems that it would be a huge help to extension authors if porting tricks
> and hacks could be encapsulated in code that everyone can use. In most
> cases some cool tricks in header files might be all that is necessary, but
> other cases may require special purpose h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trying to find why I can't import bsddb in python3.0, I have found that
this code fails:
"""
~/* Some magic to make DBNotFoundError and DBKeyEmptyError derive
~ * from both DBError and KeyError, since the API only supports
~ * using one b
Hi!
I just had a look at issue 3039 that reports a bug in tarfile.py's
TarFileCompat class and I came to the conclusion that I really would like to
remove the TarFileCompat class from Python 3.0.
Some details: The ZipFile and TarFile classes both have very different
interfaces. The original inten
On Mon, Jul 21, 2008 at 8:16 AM, nirinA raseliarison
<[EMAIL PROTECTED]> wrote:
> Terry Reedy
>> I'm interested also. Done and done.
>> http://bugs.python.org/issue3366
> patch is submitted. it is tested only on linux-2.6.26
> with gcc-4.3.1.
Thanks for doing this. In the patch, wouldn't it be g
Terry Reedy
> I'm interested also. Done and done.
> http://bugs.python.org/issue3366
patch is submitted. it is tested only on linux-2.6.26
with gcc-4.3.1.
Raymond Hettinger
> Discussions of "my approximation is better/faster/etc than yours"
> can be interminable.
> Recommend you put together your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Hammond wrote:
|In most
| cases some cool tricks in header files might be all that is necessary, but
| other cases may require special purpose helper functions designed
purely to
| aid people trying to keep code working in both environments.
+1
Hi,
Georg Brandl gmx.net> writes:
> * 3134 -- exception chaining
There are few things to correct/clean up:
(1) The "C API" paragraph contains incorrect information:
- the sentence "The PyErr_Set* calls for setting exceptions will not set the
'__context__' attribute on exceptions" is wrong. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guilherme Polo wrote:
| On Sat, Jul 19, 2008 at 9:09 AM, Lars Immisch <[EMAIL PROTECTED]> wrote:
|> Hi,
|>
|>>> I'm still loooking for a *GOOD* python2->python3 conversion guide for C
|>>> language modules.
|> Me too, but I haven't even found not so g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josiah Carlson wrote:
| I'm still curious as to what deep features people are using in bsddb.
| Anyone have any pointers to open source software?
I'm using replication and distributed transactions. Database encryption
and page integrity checks. Abusi
There are some "accepted" PEPs that are, AFAIK, fully implemented.
There shouldn't be much work left to bring them to "final" state:
* 358 -- bytes object
* 370 -- per-user site-packages directory
* 371 -- multiprocessing
* 3101 -- adv. string formatting
* 3106 -- dict.keys() etc.
* 3116 -- ne
13 matches
Mail list logo
