alking about AMD64 OpenIndiana buildbots. Haven't check others.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Interesting development.
http://syntensity.com/static/python.html
http://syntensity.blogspot.com/
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es
you must deal
with it, like you deal with other flaky OS corners, like exhausting
memory or whatever.
I would suppose that if Python exposes AIO and in some OS support is
underpar, the exposing would incentivate a better support for OS. Like
happened to threads and linux years ago.
-
t touch the values!).
This seems to be a bug in Python 3.2. Any suggestion?.
PS: The bytestream is protocol 2.
PPS: If there is consensus that this is a real bug, I would create an
issue in the tracker and try to get a minimal testcase.
- --
Jesus
. Python 3.1.3 imports the pickle just fine. So busy
migrating my projects to 3.2 (it was my compromise two years ago :), I
don't have time to debug this :).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http
tible pickle testcase in only 41 bytes.
Seems to be a SERIOUS regression in 3.2.
I can't progress further. Pickle internals are out of my expertise.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/
s time I was already convinced
that I had hit an ugly and serious bug.
Issue filed. It already has a patch. That was fast!. Now I can sit back
waiting for 3.2.1 before touching my project again :). Mixed feelings
about the waiting. I hope it is short.
Life sucks sometimes :). Thanks $DEITY ther
mote development machine) instead of
uploading private keys.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I see <http://hg.python.org/peps/>, but last change was a year ago.
I changes PEP 11 time ago, and I can't see the changes there. So the
repository seems a bit outdated. Or, maybe, are we still using SVN for
PEPs?.
- --
Jesu
set. I can't see easily if my changeset is being
tested now, or when...
Ideally I would like to see WHO pushed the changeset under test and,
moving my mouse over it, see the commit message and a link to the mercurial.
- --
Jesus Cea Avion _/_/ _/_/_/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/03/11 18:07, Antoine Pitrou wrote:
> On Mon, 14 Mar 2011 17:59:27 +0100
> Jesus Cea wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Traditionally I could see who was the committer who push
seful, since anybody (with push privileges) can
fake commit attributions. I know that people like Mozilla actually store
this information (via a push hook, if I am not mistaken).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/
ed 9a817ab166e0 to "3.x" because I don't know what
plans Raymond has for 6544accfefc3. I guess he is waiting for buildbot
results before merging to 3.x.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/03/11 02:15, Antoine Pitrou wrote:
> On Wed, 16 Mar 2011 02:00:42 +0100
> Jesus Cea wrote:
>>
>> The standard approach in mercurial is for her to pull the changes and to
>> do a merge before trying to push again (and
mmitting.html#forward-porting
I beg your pardon. 3AM in Spain. Time to get some sleep, it seems...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber /
d it didn't
automatically close the issue :).
Sorry for being so picky ;-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/
d it didn't
automatically close the issue :).
Sorry for being so picky ;-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/
apsule was
an undesired pain, but the actual support has been painless.
What problems are you finding trying to support both CObject and Capsule?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_
Too bad I don't have the time myself to
keep up with python-dev & python-ideas... Forwarding the request to
python-es mailing list. Crossing fingers.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/
yday. When I have a 200 element
list, I don't mind about the "O(nlog(n))" nature of "cmp", instead of
"O(n)" of key.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@j
way, it is risk free and you can experiment locally before pushing.
Since rebase is in HG core these days, I am getting comfy with "hg pull
- --rebase". But I find rewriting history too scary when merging between
branches and complicated changeset graphs. I want to be able to drop
quot; can be
a bit unusual for us, but pretty moot. we are getting used to it, yet.
No forgeting up-porting changesets is a massive improvement with the
late svnmerge practice (nobody cared about automatic merging, but
merging by hand anyway, cherrypicking revisions).
- --
Jesus Cea Avion
n the complete testsuite
in all changed branches. Resolving a "+1 head" here is tricky, if I
*WANT* the other developer to manage her own merging by herself. As it
should.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/
ing out of using a Python-based DVCS...
Beware, mercurial API is not stable. That is, it can change anytime.
Paradoxically, the stable "API" is the commandline, IIRC.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/11/10 16:46, Matthias Klose wrote:
> On 26.11.2010 05:11, Jesus Cea wrote:
>> I have installed GDB 7.2 32 bits and 32 bits buildslaves are green.
>> Nevertheless 64 bits buildslaves are failing test_gdb.
>>
>> Is ther
guy.
The other committer could merge her changeset to 3.x and, if my merge
between the two heads is not trivial, she must notice it and do a second
merge.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/03/11 13:35, Jesus Cea wrote:
> Tonight I was thinking about doing a merge inside the branch, to solve
> the "+1 branch". Something like transforming:
Another thing I was thinking about tonight was... dropping the "+1 head
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 13:19, Jesus Cea wrote:
> Would be acceptable to change something like:
>
> """
> add_library_path("/usr/local/lib")
> """
>
> to something similar to:
>
> "&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/03/11 14:10, Brian Curtin wrote:
> On Thu, Mar 17, 2011 at 07:41, Jesus Cea <mailto:j...@jcea.es>> wrote:
[..]
> Each developer is responsible of merging HIS heads. If somebody
> "forgets", nothing wrong w
it (push hooks), except
social pressure.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
afe to axe it, instead of the regular 3.x
deprecates, 3.(x+1) cleans up.
In this way we can keep the improvements, while not leaving people just
migrating from 2.7 behind.
The problem will be to decide when to do the cleanup...
- --
Jesus Cea Avion _/_/ _/_
0 behaviour actually broke some other extensions out there (when
used with warnings active). Details in the tracker, somewhere. I am
offline now, can't use the browser.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/
ots and, if the patch applies cleanly to the branch tip, actually
apply it, build & test.
That would be amazing, security aside :).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/
ith all the little details, collapsing
outgoing commits, "+1 head", merging real conflicts, linealizing
history, moving the patch thru branches, etc.
But the fact is that some of us are still experimenting.
- --
Jesus Cea Avion _/_/
t, this sandbox could add your
patch automatically to the assigned issue (bugs.python.org).
We already have "cloned in the server" repositories, but I am not sure
how to delete them, how to push them to the buildbots (is it efficient?,
of the buildbots must pull the comple
ce, "hg log --follow-first".
We could have a trivial "push hook" to enforce that the current tip be
the "left/first" parent for any merge.
- --
Jesus Cea Avion _/_/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/03/11 18:38, Jesus Cea wrote:
> Most of our problems are related to trying to keep a lineal history, and
> races with pull-patch-commit-push cycle. I propose the following workflow.
The points of my proposal are:
1. The hg.pyth
like a year ago. Somebody else said he was
planning a PEP... not done yet, I guess.
Digging the archive:
<http://mail.python.org/pipermail/python-dev/2010-April/099237.html>
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - h
or a buildbot cycle.
Also, you have to deal with whatever problem you have during the merge
yourself (for instance, the API changed and the merge is not trivial),
when this work should be done by the original committer.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/
ature or bug you're trying to land might be
> enough.
Would be amazing if the test system could detect which files were
changed and only do the tests that cover them. Not a 100% safety net,
provided by the full test suite, but not a bad star
be "socket-like", but how much "socket-like" in
the API sense?. Do you need to implement "getpeername()" for injecting
in smtplib?.
If you agree that this is a nice idea, what other libs do you think that
could benefice of being "injected", beside "socke
olumn link). What do you think?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@
at-of-shame I should wear because breaking the build? :).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber /
rors in 3.3 and remove in 3.4,
according to PEP11. A heads-up warning and request for help in "Python
Insider" is the way to go, too.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es
t;http://mercurial.selenic.com/wiki/PurgeExtension>. Do you want me to
activate this extension in my buildbots? (OpenIndiana machine).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.
2.7, 3.1 and 3.2
installed in my machine (Ubuntu 10.04) because I need to support code
spanning such a range of python versions. I remember that compiling 2.3
or 2.4 was a bit painful.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jc
already mentioned, this will be a bug fix release only; no new
| features allowed.
As current bsddb module maintainer, I was wondering if 2.5.2 will
support BerkeleyDB 4.6 :-?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Holden wrote:
|> Sorry if this is a repeat.
Published also in Slashdot.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/_/
jabber / x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just trying to open a new bug in bssdb module and assign it to me :-).
Seems I have no permissions to do that :-).
The issue is http://bugs.python.org/issue1976
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL
DB 4.6 support
seems reasonable (to me). If I'm wrong, please educate me :-).
This backport would include also stability patches. For example, I just
solved a memory leak.
Greg, any opinion?.
Beware, new kid in the block! :).
- --
Jesus Cea Avion _/_/ _/_/_/
ntain bsddb tracking outside python one, to reduce your burden?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL PROT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This will be my last email today, I don't want to waste (more of) your
*valuable* time.
http://bugs.python.org/issue1391
http://bugs.python.org/msg61892
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROT
apped my build directory then reran
|
| configure ;; make ;; make test
|
| Seems to be working better now.
Feel free to post a bug in the tracker. I would look at it.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www
I have tried to sign the Python Contributor Agreement, but I am not
sure about current pybsddb license terms. Help welcomed.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/_/
jabbe
:-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL PROTECTED
.
PS: Yes I tried also ZODB+BerkeleyDB. It was ugly and unusable (sigh!),
but I don't know why you suppose BerkeleyDB was the one to blame.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _
leyDB :-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL PROT
ython License" on your contributor form and submit it.
But Python license is not accepted for Python Contributor Agreement.
This is even in the FAQ. MIT is not accepted either. Software patents
sucks :p
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTE
this issue?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL
be
send to me.
I think this is the only way when integrating a project outside python
SVN. Suggestions?.
PS: I can't comment on Win64. It is an alien world to me :).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_
What is wrong with:
for lineno,line in enumerate(file) :
~ print lineno+1,line
:-?
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL P
ns, and transactions are write-synchronous.
In my system, runnning all tests serially (you can run all of them in
parallel, if you wish) takes about 15-20 seconds. Far faster than
current tests in python svn, and that can be improved even more.
- --
Jesus Cea Avion _/_/ _/_/_/
location. Or something from tempfile.
I'm worried about the case when a test crashes and leave garbage
behind... that will crash future test runs.
I guess I would delete the directory before using it, but I guess
somebody already had this problem and solved it, somehow. :-?
- --
Jesus Cea
. Let me know if you need anything from me.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabbe
ved in the wild,
verified against 5 different python releases and 8 different Berkeley DB
ones.
And I will love to do additional work in python, aside bsddb.
Let me show you that I can do it...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - htt
ny Solaris related issue. Just ask.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL
cumentation/berkeley-db/xml/api_c/db_set_flags.html#DB_CHKSUM>
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabb
. That done, I will update python version.
PS: pybsddb 4.7.0 will support Berkeley DB 4.0 to 4.7. So, the buildbots
don't need to be upgraded.. unless we decide that Python 4.6/3.0 will
have Berkeley DB 4.7.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent Nelson wrote:
| Indeed. Where do we stand with regards to svn commit e-mails
| being sent for 'external'? DB 4.6 is ~16MB...
I just committed bsddb3 4.7.0. Please install Berkeley DB >=4.7.25.
- --
Je
ser/admin has control over BDB upgrades. But since MS Windows
Python bundles BDB, we need to be extra-careful there.
Someday we need to talk about pybsddb3 "eggs" (via pypi) supporting BDB
DLL bundled by stock python in MS Windows. Current approach needs a n
releases because the
buildbots are outdated :(
| If it passes the entire test suite
| several times on windows x86 and amd64 builds when built with
| BerkeleyDB 4.7 (once Jesus commits the support code) I'm inclined to
| say we should ship with it and only revert back to 4.5 if someone ha
eed to adjust Tools/msi/external.bat to have the slaves export
| the new version.
I was thinking about the Unix buildbots.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL PRO
/test/regrtest.py -v -u bsddb test_bsddb test_bsddb3" to
| reproduce exactly how it is run yourself).
What about changing that file to read the testsuite from
"Lib/bsddb/test", directly, to avoid skipping new tests again?.
I would like to print the Berkeley DB release used, also.
n 3.0 via "2to3", for a long time. In the C side, I plan keeping
the same codebase, with conditional compilation. Ideas?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M.-A. Lemburg wrote:
| If you use PyBytes APIs, you expect to find PyBytes functions in
| the libs and also set breakpoints on these.
Very good point.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED
t is, "fire and forget" code, with little communication).
How is implemented "thread.setDaemon()"?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.j
n the morning, in Spain.
bsddb will be ready for python 3.0.
(writting this while compiling new 2.6 and 3.0 beta2 :-) )
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[
otherwise, I will add it to PEP 3108.
03:31 AM in the morning in Spain. Just working in porting bsddb to
python3000. I have a lot of issues compiling the C code and with the
2to3 automated conversion, but I'm pretty sure can get it ready for
october release.
I'm still loooking for a *GOOD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
| On Sun, May 25, 2008 at 6:25 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
|> Since I need to port bsddb3 to py3k, what I need to know?. Is any
|> *updated* document out there?.
|
| No, but there is a not yet complet
to see the tests passing on MS Windows :-p. I'm a bit surprised,
actually O:-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
, you can use the already in stdlib "gdbm"
module. Just remember it is not transactional, so beware diskfulls,
application crashes, etc.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_
aily :-p.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAIL PROTECTED] _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
&qu
e issue is. Past mistakes and maintenance
nightmares WILL NOT be repeated.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
j
m not lazy, but it is so sunny outside...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
| On Mon, Jul 21, 2008 at 11:06, Jesus Cea <[EMAIL PROTECTED]> wrote:
|> I'm *VERY* interested in 2.6->3.0 migration guide for C module
|> extensions. 3.0 is around the corner and the API is changing almost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subversion 1.5 solves the "repeated merge" problem. At last!!.
Somebody is considering upgrading python svn to 1.5, and allowing only
commits coming from 1.5 clients?.
- --
Jesus
tep-test/0>
Thanks in advance for your time and attention.
Of course, any other help appreciated :-)
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:[EMAI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesus Cea wrote:
| Trent, I was wondering if you could look at some test failures in MS
| Windows builds. I can't debug Windows issues myself :-(. This is a MS
| free environment...
I will be out of the city, 100% offline, until monday/tuesd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amaury Forgeot d'Arc wrote:
| I see that some tests use os.unlink. They should use
| test_support.unlink() instead.
Old stuff. Fix just committed.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] -
s are rejected.
To easy testsuite porting, I've defined some minimal proxy/adapter
objects to facade unicode strings from/to "bytes". So, current testsuite
works for every supported python release, with the minimal conditional
code. These adapter objects ARE NOT INTENTED to b
any
list/contact info out there.
I already updated my mailman subscriptions months ago. My old email can
vanish without warning.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/
ion code
> becomes more complex by having to avoid calling read(0) at all).
How do you differenciate between that empty string (when doing
"read(0)"), from EOF (that is signaled by an empty string)?.
- --
Jesus Cea Avion _/_/
lass instances. Note the
name aliasing.
I don't understand why these functions exist. It causes a few problems,
like being unable to subclass the bsddb classes, for example.
For future bsddb4.6.4 (Late october, I think) I plan to remove the
Factory functions, exporting the classes directly, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isaac Morland wrote:
> On Tue, 2 Sep 2008, Jesus Cea wrote:
>
>>> Indeed. read(0) is quite often generated as an edge case when one is
>>> computing buffer sizes, and returning an empty string is most
>>> defi
ar" python objects.
If you use bsddb, please consider to subscribe to pybsddb mailing list.
It has pretty low traffic and you can guide bsddb evolution (for
example, prioritize Berkeley DB binding additions).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL P
o, so installing bsddb externally will not "magically" make
it available to 3.0 shelve. I can't comment about the python-dev plans here.
PS: Remember that if you are installing bsddb as a separate package, its
name will be "bs
could work to trying to comply :).
Yes, we are all very busy guys, but still...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
[EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_
p as to simultaneously permit a migration from Python 2.x to
> 3.0 of an internal project that relies on bsddb, while at the same time
> banning those performing the migration from installing the 3.0
> compatible version of pybsddb, then they have much bigger problems than
> which mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Titus Brown wrote:
> On Thu, Sep 04, 2008 at 03:23:22PM +0200, Jesus Cea wrote:
> -> Brett Cannon wrote:
> -> >> Related but tangential question that we were discussing on the pygr[0]
> -> >> mailing list --
t;something" safe, scalable, configurable and being able to give you
opaque objects when an OID (Object ID) is presented. Compare a terabyte
Python "shelve" object, ease of use, transparence, etc., with keeping
the objects in a SQL database server.
101 - 200 of 245 matches
Mail list logo
