Re: [Python-Dev] segfault (double free?) when '''-string crosses line

Jean-François Piéronne wrote: > I (and a few others guys) work on the VMS port,also, HP has publish in > the VMS technical journal an article about Python on VMS. > What do you need? In the specific case: an answer to Tim Peter's question (where is vms__StdioReadline, and how can its memory alloca

[Python-Dev] PSF Contributor Agreement for pysqlite

Posting here because I don't know a better place: Federico di Gregorio and me have both faxed PSF contributor agreements to the PSF for integration of pysqlite into Python 2.5. -- Gerhard ___ Python-Dev mailing list Python-Dev@python.org http://mail.py

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

Gerhard Häring wrote: > Posting here because I don't know a better place: > > Federico di Gregorio and me have both faxed PSF contributor agreements > to the PSF for integration of pysqlite into Python 2.5. Thanks! I should make the list of names of people available somewhere which have signed t

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

As far as I know, I've never signed one. I probably should, or is there some grandfathering rule for people who've been contributing from before the new agreement came in? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

Anthony Baxter wrote: > As far as I know, I've never signed one. I probably should, or is > there some grandfathering rule for people who've been contributing > from before the new agreement came in? No - those people will have to fill out the agreement covering past contributions also: http://

Re: [Python-Dev] need info for externally maintained modules PEP

Brett Cannon wrote: > OK, I am going to write the PEP I proposed a week or so ago, listing > all modules and packages within the stdlib that are maintained > externally so we have a central place to go for contact info or where > to report bugs on issues. This should only apply to modules that wan

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

On Tuesday 11 April 2006 00:56, Martin v. Löwis wrote: > No - those people will have to fill out the agreement covering past > contributions also: > > http://www.python.org/psf/contrib-form-python.html > > And yes, you are right - you haven't filed one, so far. Righto - I will try to get to this s

Re: [Python-Dev] I'm not getting email from SF when assignedabug/patch

Brett Cannon wrote: > Can someone (Martin, Barry?) post this on python.org (I don't think > this necessarily needs to be put into svn and I don't have any access > but svn) so Fredrik can free up the space on his server? Did I ever respond to that? I put the file on http://svn.python.org/snapshot

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

Anthony Baxter wrote: > Righto - I will try to get to this sometime this week. Is it worth > sending out emails to as many people as can be found to try to rustle > up more of these? It's unclear to me just how important these are to > the state of Python. I think I twice mailed everybody in Mi

[Python-Dev] PEP 302 support for traceback, inspect, site, warnings, doctest, and linecache

Here's my plan for implementing PEP 302 support (``__loader__`` sensitivity) for the above modules: * Change all of the ``linecache`` API functions (except ``clearcache()``) to add an optional ``module_globals`` argument, which they will use to obtain the ``__name__`` and ``__loader__`` in the

Re: [Python-Dev] need info for externally maintained modules PEP

Brett Cannon wrote: > OK, I am going to write the PEP I proposed a week or so ago, listing > all modules and packages within the stdlib that are maintained > externally so we have a central place to go for contact info or where > to report bugs on issues. Based on the recent interchange regardin

[Python-Dev] DRAFT: python-dev summary for 2006-02-01 to 2006-02-15

Sorry about the delay folks. Here's the summary for the first half of February. I'm going to try to get the ones out for the second half of February and first half of March shortly. Please send me any comments/corrections! = Announcements = -

[Python-Dev] Failing "inspect" test: test_getargspec_sublistofone

I seem to recall some Python-dev discussion about this particular behavior, but can't find it in Google. Is this test currently known to be failing? If so, why, and what's the plan for it? ___ Python-Dev mailing list Python-Dev@python.org http://mail

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

On Mon, 10 Apr 2006, "Martin v. Löwis" wrote: I think I twice mailed everybody in Misc/ACKS. In principle, we want to have agreements from everybody who ever contributed, so that we can formally change the license (and so that it is clear to Python users what the legal standing is). [...] Not s

[Python-Dev] pdb segfaults in 2.5 trunk?

Is anybody else getting this? Python 2.5a1 (trunk:45237, Apr 10 2006, 15:25:33) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import pdb >>> def x(): ... if 'a' in 'b': ... pass ... >>> pdb.run("

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

On 4/10/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > Is anybody else getting this? Neal had originally reported that test_trace failed with a segfault, and it's essentially exercising the same code. I don't see a failure there or here at the moment. If there is a bug, though, it's likely to b

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

4On 4/10/06, Jeremy Hylton <[EMAIL PROTECTED]> wrote: > On 4/10/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > > Is anybody else getting this? > > Neal had originally reported that test_trace failed with a segfault, > and it's essentially exercising the same code. I don't see a failure > there or

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

On 4/10/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: Is anybody else getting this? > (2)x()(Pdb) s Segmentation faultI'm not able to reproduce this in 32bit or 64bit mode (debian unstable.) Does 'make distclean' before configure/compile fix it? If not, can you unlimit coredumpsize and check to see

Re: [Python-Dev] PSF Contributor Agreement for pysqlite

John J Lee wrote: > On Mon, 10 Apr 2006, "Martin v. Löwis" wrote: >> I think I twice mailed everybody in Misc/ACKS. In principle, we want >> to have agreements from everybody who ever contributed, so that we >> can formally change the license (and so that it is clear to Python >> users what the leg

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

Phillip J. Eby wrote: > Is anybody else getting this? I can't reproduce this, on Debian, gcc 4.0.3, trunk:45237. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://ma

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

At 09:47 PM 4/10/2006 +0200, Thomas Wouters wrote: >On 4/10/06, Phillip J. Eby ><[EMAIL PROTECTED]> wrote: >>Is anybody else getting this? > >> > (2)x() >>(Pdb) s >>Segmentation fault > >I'm not able to reproduce this in 32bit or 64bit mode (debian unstable.) >Does 'mak

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

On 4/10/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > > It appears the problem is an object/mem mismatch: both PyOS_Readline in > pgenmain.c, and PyOS_StdioReadline use PyObject_MALLOC, but bltinmodule.c > is freeing the pointer with PyMem_FREE. This (Readline using PyObject) was due to my recen

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

[Phillip J. Eby] > ... > #0 0x401bbaa4 in _int_free () from /lib/libc.so.6 > #1 0x401baa3c in free () from /lib/libc.so.6 > #2 0x080a253e in builtin_raw_input (self=0x0, args=0x4050862c) at > Python/bltinmodule.c:1759 > > It appears the problem is an object/mem mismatch: both PyOS_Readline in >

[Python-Dev] updating PyExpat (Was: need info for externally maintained modules PEP)

[Martin v. Loewis wrote] > Brett Cannon wrote: > > - expat > > Not sure whether you mean the Expat parser proper here, or the pyexpat > module: both are externally maintained, also; pyexpat is part of PyXML. > OTOH, people can just consider PyXML to be part of Python, and I > synchronize the Pytho

Re: [Python-Dev] Failing "inspect" test: test_getargspec_sublistofone

On 4/10/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > I seem to recall some Python-dev discussion about this particular behavior, > but can't find it in Google. Is this test currently known to be > failing? If so, why, and what's the plan for it? Only failing for 2.4 IIRC: http://python.org/s

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

On 4/10/06, Tim Peters <[EMAIL PROTECTED]> wrote: > It's documented (after a fashion) at the declaration of > PyOS_ReadlineFunctionPointer. Yesterday that read: > > """ > /* By initializing this function pointer, systems embedding Python can >override the readline function. > >Note: Python

Re: [Python-Dev] updating PyExpat (Was: need info for externally maintained modules PEP)

Trent Mick wrote: > I was going to be updating Modules/expat/... to Expat 2.0 relatively > soon. Must I then go via the PyXML folks to do this update then or can I > checkin to Python's SVN directly? Please check in directly. I'm going to update PyXML some time. Regards, Martin __

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

[Guido] > Shouldn't it at least match call_readline() in Modules/readline.c, > which uses PyMem_Malloc()? I'm not sure what "it" means there, but, like I said, it's messy regardless. That's why we ended up with a large number of mismatches to begin with: there are many allocation and free'ing si

[Python-Dev] DRAFT: python-dev summary for 2006-02-16 to 2006-02-28

Ok, here's the summary for the second half of February. Again, comments and corrections are greatly appreciated! (And thanks to those who already gave me some for the last summary.) = Announcements = --- Python release schedule ---

Re: [Python-Dev] Who understands _ssl.c on Windows?

[Tim Peters wrote] > Trent (and anyone else who wants to play along), what happens if you > do this by hand in a current trunk or 2.4 build?: > > import socket > s = socket.socket() > s.settimeout(30.0) > s.connect(("gmail.org", 995)) > > On my box (when gmail.org:995 responds at all), the connec

Re: [Python-Dev] Who understands _ssl.c on Windows?

On 4/10/06, Trent Mick <[EMAIL PROTECTED]> wrote: > > Sorry that I took so long to run this. It is a little unfortunate that > with the last build step being "clean", I couldn't just cd into the > build directory and try to run this. Maybe we should clean before we configure/compile? That would l

Re: [Python-Dev] I'm not getting email from SF when assignedabug/patch

On 4/10/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Brett Cannon wrote: > > Can someone (Martin, Barry?) post this on python.org (I don't think > > this necessarily needs to be put into svn and I don't have any access > > but svn) so Fredrik can free up the space on his server? > > Did I eve

Re: [Python-Dev] need info for externally maintained modules PEP

On 4/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Brett Cannon wrote: > > OK, I am going to write the PEP I proposed a week or so ago, listing > > all modules and packages within the stdlib that are maintained > > externally so we have a central place to go for contact info or where > >

Re: [Python-Dev] Who understands _ssl.c on Windows?

[Neal Norwitz wrote] > On 4/10/06, Trent Mick <[EMAIL PROTECTED]> wrote: > > > > Sorry that I took so long to run this. It is a little unfortunate that > > with the last build step being "clean", I couldn't just cd into the > > build directory and try to run this. > > Maybe we should clean before

[Python-Dev] DRAFT: python-dev summary for 2006-03-01 to 2006-03-15

Ok, if I summarize any more of python-dev, my brain's going to explode. ;-) Here's the summaries for the first half of March. Let me know what to fix! = Announcements = --- Webstats for python.org --- Thomas Wouters set up webaliz

Re: [Python-Dev] Who understands _ssl.c on Windows?

[Trent] > C:\trentm\src\python\python\PCbuild>python_d > Python 2.5a1 (trunk, Apr 10 2006, 14:48:00) [MSC v.1310 32 bit (Intel)] > on win32 > Type "help", "copyright", "credits" or "license" for more information. > >>> import socket > [25133 refs] > >>> s = socket.socket()

Re: [Python-Dev] Who understands _ssl.c on Windows?

[Neal Norwitz] > Maybe we should clean before we configure/compile? That would leave > the last build in tact until the next run. It doesn't matter much to me -- I do all changes and checkins from a non-buildbot checkout. The one thing I like about the current scheme is that when I run my daily

Re: [Python-Dev] Who understands _ssl.c on Windows?

[Tim Peters wrote] > In fact, that reminds me I added a "delete all the .pyc files" step to > the Windows buildbot clean.bat precisely so I didn't have to burn time > and space backing up 1600 stale files each day. So -0 on changing. Good enough for me. Let's not bother. Trent -- Trent Mick [E

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

Tim Peters wrote: > The PyObject_ memory family is generally faster and more > memory-efficient for small allocations than the PyMem_ memory family. > Lines of source code, and encoding strings, are usually small enough > to exploit that. The "ob" in obmalloc.c doesn't really have anything > to

Re: [Python-Dev] pdb segfaults in 2.5 trunk?

[Greg Ewing] > However, if they're not exclusively for objects, > having "Object" in the name would seem to be > highly confusing, perhaps dangerously so. (Person > A writes PyObject_Alloc(some_chars), Person B > writing the code to free it thinks "What??? > That can't be right!" and uses PyMem_Fre