Re: TLP Name
On 5/16/07, Gregory (Grisha) Trubetskoy [EMAIL PROTECTED] wrote: Quetzalcoatl It's not *that* hard to say - and it's far and away my favorite. Terrarium is the next best alternative I've seen so far. My $.02. -- justin
Re: [jira] Created: (MODPYTHON-184) Memory leak apache.table()
On 8/16/06, Jim Gallacher [EMAIL PROTECTED] wrote: Actually I don't think apr_pool_destroy() in table_dealloc is actually destroying the pool. I've been poking around in the code and there is something odd going on here. I would actually love to test this, but I can't build trunk on Mac OS X. The definitions of PyLFS (LINKFORSHARED) refer to values that I don't have: LINKFORSHARED= -u __dummy -u _PyMac_Error -framework System $(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK) -framework CoreServices -framework Foundation That's not the right line. It should be looking at LDSHARED and PYTHONFRAMEWORK instead. Ideally, we should switch to a format like what Subversion uses to detect the values: which queries Python directly. See: http://svn.collab.net/repos/svn/trunk/build/get-py-info.py The sed magic going on in autoconf is just too creaky. (Subversion builds against Python on Mac OS X just fine.) If we import get-py-info.py to MP, we should prepend it with the license block from: http://svn.collab.net/repos/svn/trunk/subversion/LICENSE (That script doesn't have a license block, but it really should. I'll poke other SVN devs about fixing that, but importing that LICENSE block is a safe compromise in the meantime.) Thanks. -- justin
Building on Mac OS X was [jira] Created: (MODPYTHON-184) Memory leak apache.table()
On 8/16/06, Graham Dumpleton [EMAIL PROTECTED] wrote: I would actually love to test this, but I can't build trunk on Mac OS X. Huh! Do you have more than one version of Python installed? Nope. I just have Python from /usr/bin/python. Nothing special. I do all my work on Mac OS X and have no problem. I only have the standard OSE supplied version of Python installed though. Not sure what you mean by OSE - do you mean OS? Anyway, I just rely on what comes with the OS. I'm sure it worked at some point, but that's probably years ago. I have: Python 2.3.5 (#1, Mar 20 2005, 20:38:20) [GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin FWIW, am using Mac OS X 10.4.7 at present. So am I. mod_python.so doesn't link as the LINKFORSHARED values don't expand properly. It's not even the right value to be bringing in from Python's Makefile! Because of other stuff, have been ignoring the table object issues, but maybe I should start paying more attention. :-) I'm more than happy to fix up autoconf to stop doing the insanity with sed and determine those values within Python directly. I'll try to do so this weekend: time permitting. (Greg and I and the other SVN devs solved this problem already within Subversion.) However, since I can't build, this means that I can't debug this pool problem. =( -- justin
Re: svn commit: r394455 - in /httpd/mod_python/trunk: Doc/appendixc.tex src/hlist.c src/include/hlist.h src/include/mod_python.h src/include/mod_python.h.in src/mod_python.c src/requestobject.c test/h
On 4/19/06, Jim Gallacher [EMAIL PROTECTED] wrote: I don't know to what extent Debian-derived distributions such as Ubuntu use the stock Debian patches, but I wouldn't be suprised if we had compilation problems there as well. It's not too much of a stretch to think a similar patch may be applied in other distributions such as Redhat either. I don't believe Ubuntu has any noticable diffs for Debian for apache2. (So, yes, the regex issue is on Debian as well.) -- justin
Re: mod_python 3.3.0-dev-20060321 available for testing
On 3/22/06, Graham Dumpleton [EMAIL PROTECTED] wrote: That is the error I was getting from ab in Apache 2.2. Change test.py to explicitly use ab from Apache 2.0 and see if they go away. Here is the previous information I posted about core_input_filter errors caused by ab test tool in Apache 2.2. http://www.mail-archive.com/python-dev@httpd.apache.org/msg01535.html I believe that this is the APR kqueue bug on Mac OS X. (ab uses the pollset API.) This should be worked around with the just-released APR 1.2.6 - which will be included in the forthcoming httpd 2.2.1. I will note that if you see odd stuff like this with httpd or APR, please don't hesitate to post to [EMAIL PROTECTED] or to [EMAIL PROTECTED] Your issue would have been identified way earlier if you had posted there. =) -- justin
Re: site.
On 2/12/06, Jim Gallacher [EMAIL PROTECTED] wrote: As a result of the nudge from Justin I've hacked out a minimum build system for us to play with, based on the httpd doc infrastructure. You can download it from: http://people.apache.org/~jgallacher/mod_python/mp-website-build.tgz Untar and check the README for further instructions. The generated output can be found at http://people.apache.org/~jgallacher/mod_python/website-test. I'll gently prod that this would be *really* nice to deploy - even as a placeholder while you add even more content. =) -- justin
Re: Cross-platform query: _FILE_OFFSET_BITS in python and httpd
On 3/14/06, Gregory (Grisha) Trubetskoy [EMAIL PROTECTED] wrote: What the output on Fedora Core 4 means is that essentially Python and APR/httpd are compiled in an incomatible way - in APR the size of an inode (ino_t) is 32 bits and in Python it is 64 bits (this is what _FILE_OFFSET_BITS 64 does). APR 1.0+ has LFS turned on by default. This means that httpd 2.0.xx will have 32-bit files by default, but that LFS should be activated for 2.1 and beyond. The mod_perl guys have some tricks to get around this conflict as they run into this same mismatch as well. -- justin
Re: My plans for mod_python changes (260206).
On 3/4/06, Graham Dumpleton [EMAIL PROTECTED] wrote: Actually, if want to get that pedantic and formalised, it does look like one can select an alternate workflow. The level of administration access we have probably does not allow us to change it, let alone see what options exist. Come up with the workflow that everyone here feels that best suits mod_python and open a JIRA issue to get our JIRA admins to set it up as you want it. (Given I have almost no idea how this works in JIRA, I'd want Jeff or someone more knowledgable setting it up.) Use the JIRA component under the Infra project: https://issues.apache.org/jira/browse/INFRA Anyway, digging around with the XML-RPC interface into JIRA, found the list of issue codes with descriptions at end of this email. You can see that some other project must have a customised work flow, don't know which project though. Cocoon and MyFaces have their own workflow. -- justin
Re: JIRA Housekeeping
On 2/19/06, Graham Dumpleton [EMAIL PROTECTED] wrote: Grisha, if you are reading this, what do I need to do to get admin JIRAaccess on mod_python stuff? I recollect asking you but can't rememberwhat you said. I thought perhaps you were going to organise it, but also can't remember.I've added you to the mod_python-developers group, so you should be able to close issues now. Is there anyone else who should be added?I'm not quite clear who can add folks to that group ( i.e. if someone in that group can add other members or only the project admin - Grisha - can do so), but I'll be keeping an eye out here.Thanks. -- justin
Re: mod_python license
On 2/21/06, Graham Dumpleton [EMAIL PROTECTED] wrote: Technically speaking, if you make a change to the file, you should be ensuring you add the current years date. Ie., not replace it. Thus, presuming no changes were made in 2005, you would have: * Copyright 2004, 2006 Apache Software Foundation If you have a string of consecutive years, ie., changes were also made in 2005, you would use the following it you didn't want to enumerate all the years: * Copyright 2004-2006 Apache Software Foundation At least that is how I understand copyright stuff. Apache folks may want it done differently. It should *only* be the first year of publication: i.e. 2004 is correct. (httpd does it wrong.) Note that the ASF will be updating our standard licensing template soon to conform better with legal requirements. Now that you guys should be on the HTTP Server PMC soon, you should be seeing the emails from our Legal folks with the new template. I hope that we'll see this within the next month, but who knows... Keep your eyes open on that front; when that comes down, there will be a bunch of commits to a lot of files across the entire foundation. =) Thanks. -- justin
Re: site.
On 2/11/06, Jim Gallacher [EMAIL PROTECTED] wrote: The underlying html from httdp.apache.org makes heavy use of tables for layout and formating. If we end up using this layout I'd want to rewrite it in css. Tables are just so last century. :) You realize that httpd.apache.org is auto-generated from XML through Velocity templates, right? The XML source is here (see the xdocs directory): http://svn.apache.org/repos/asf/httpd/site/trunk/ HTH. -- justin
Re: site.
On 2/11/06, Jim Gallacher [EMAIL PROTECTED] wrote: No, I was not aware that it is auto-generated, but I'm hardly suprised. :) The point was mostly to kick off a discussion. The point is that you needn't muck with HTML directly and can focus on the content instead. =) -- justin
Re: site.
On 2/10/06, Jim Gallacher [EMAIL PROTECTED] wrote: So we would have our own httpd instance in the zone, right? infra@ allocates zones to a PMC. So, you'd have to 'share' the server with the rest of the httpd PMC. But, I'm sure we can work something out. -- justin
