On 1/3/07, Martin v. Löwis [EMAIL PROTECTED] wrote:
Neal Norwitz schrieb:
By private, I mean internal only to python and don't need to prefix
their identifiers with Py and are subject to change without backwards
compatibility. Include/graminit.h is one example of what I mean.
Some others
Neal Norwitz schrieb:
I'm a Python embedder and I want to know what's available to me. I
look in Include and see a ton of header files. Do I need all these?
What do I *need* and what can I *use*? I only want to see the public
stuff that is available to me. Thus I want anything that has
On 2007-01-03 01:42, Brett Cannon wrote:
On 1/2/07, M.-A. Lemburg [EMAIL PROTECTED] wrote:
+Open Issues
+===
+
+Consolidate dependent modules together into a single module or
package?
...
+Consolidate certain modules with similar themes together in a
package?
On 2007-01-04 07:59, Neal Norwitz wrote:
The current schedule looks like it's shaping up to be:
Wed, Jan 24 for 2.5.1c1
Wed Jan 31 for 2.5.1
It would be great if you could comment on some of the bug reports
below. I think several already have patches/suggested fixes.
It's not clear to
Martin v. Löwis wrote:
Neal Norwitz schrieb:
Wow, I didn't realize I was that much of a broken record. :-)
I don't even remember talking to Thomas about it, only Guido. I
definitely would like to see all private header files clearly denoted
by their name or directory.
What is a
Ron,
I agree that pydoc could benefit a bit from some cleanup.
As you point it out, the ability to write quick viewers would be
very helpful. I came across that when wanting to develop script
on a remote web server for which I only had FTP access: I ended
up having to study pydoc more than I
It would be nice if this simple fix could be included (main branch and 2.5.1):
https://sourceforge.net/tracker/?func=detailaid=1598181group_id=5470atid=105470
[ 1598181 ] subprocess.py: O(N**2) bottleneck
I submitted the trivial fix almost two months ago, but apparently nobody feels
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2007, at 4:17 AM, Martin v. Löwis wrote:
As specified, above, it is incompatible with the current API. I think
#include Python.h
should be preserved. I personally see no problem with a single header
file, and would prefer that include
Laurent Gautier wrote:
Ron,
I agree that pydoc could benefit a bit from some cleanup.
As you point it out, the ability to write quick viewers would be
very helpful. I came across that when wanting to develop script
on a remote web server for which I only had FTP access: I ended
up having
Barry Warsaw schrieb:
I agree. I don't mind if Python.h is just a wrapper around #includes
from python/*.h. I think we should add structmember.h and structseq.h
to Python.h and perhaps move everything else into a 'python' subdirectory.
For the python subdirectory, there is the issue that the
On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
For the python subdirectory, there is the issue that the framework
includes in OSX magically look for python.framework when searching for
python/foo.h, which they find, so that may get us the wrong version.
Somebody would have to
On 1/4/07, Ralf W. Grosse-Kunstleve [EMAIL PROTECTED] wrote:
It would be nice if this simple fix could be included (main branch and 2.5.1):
https://sourceforge.net/tracker/?func=detailaid=1598181group_id=5470atid=105470
[ 1598181 ] subprocess.py: O(N**2) bottleneck
I submitted the trivial
On 1/4/07, M.-A. Lemburg [EMAIL PROTECTED] wrote:
On 2007-01-03 01:42, Brett Cannon wrote:
On 1/2/07, M.-A. Lemburg [EMAIL PROTECTED] wrote:
+Open Issues
+===
+
+Consolidate dependent modules together into a single module or
package?
...
+Consolidate certain modules
On 4 Jan, 2007, at 17:56, Fred L. Drake, Jr. wrote:
On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
For the python subdirectory, there is the issue that the framework
includes in OSX magically look for python.framework when searching
for
python/foo.h, which they find, so that may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2007, at 2:36 PM, Ronald Oussoren wrote:
On 4 Jan, 2007, at 17:56, Fred L. Drake, Jr. wrote:
On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
For the python subdirectory, there is the issue that the framework
includes in OSX
Brett Cannon wrote:
[ ... ]
Yep. PEP 3108 does have some basic package suggestions in the Open
Issues section and people seem to support them. I will be making a
separate push for them on python-3000 once the whole discussion of what
modules to remove has settled down.
Then again,
On Thu, Jan 04, 2007 at 10:22:54AM -0800, Mike Klaas wrote:
[ 1598181 ] subprocess.py: O(N**2) bottleneck
I submitted the trivial fix almost two months ago, but apparently nobody
feels responsible...
Is Peter Astrand still actively maintaining the module? I've been
assigning subprocess
Hi Ron and Laurent,
I welcome attempts to improve pydoc (especially since I don't have
much time to work on improving it myself). I definitely agree that
moving to CSS is long overdue, though I would like some input on
the style of the produced pages.
It's probably a good idea to explain how
Patch / Bug Summary
___
Patches : 418 open ( +5) / 3522 closed ( +1) / 3940 total ( +6)
Bugs: 959 open (+13) / 6405 closed ( +5) / 7364 total (+18)
RFE : 250 open ( +2) / 245 closed ( -1) / 495 total ( +1)
New / Reopened Patches
__
update
Ka-Ping Yee wrote:
Hi Ron and Laurent,
I welcome attempts to improve pydoc (especially since I don't have
much time to work on improving it myself). I definitely agree that
moving to CSS is long overdue, though I would like some input on
the style of the produced pages.
Additional input
Ron Adam wrote:
Improving pydoc has been suggested before by me and others. I've been working
on a version that is probably 80% done and would like to get feed back at this
point to determine if I'm approaching this in the best way.
Just asking--are you going in a PEP-287-ly way as you work?
I fixed the crash that was due to raising a warning on shutdown. I
have heard about crashes at shutdown and wonder if this was the cause.
There might be similar bugs lurking that assume PyModule_GetDict()
always returns a valid pointer. It doesn't, it can return NULL.
I'm not sure if the
Larry Hastings wrote:
Just asking--are you going in a PEP-287-ly way as you work? If not,
would your work make PEP 287 easier to implement?
Pydoc does no reformatting or changes to doc strings. They are displayed as
is in plain text. About the only formatting that is done is to wrap long
Ron Adam wrote:
Larry Hastings wrote:
For those of us without eidetic memories, PEP 287 is use
reStructuredText for docstrings:
http://www.python.org/dev/peps/pep-0287/
Thanks for the link. PEP 287 looks to be fairly general in that it expresses
a
general desire rather than a
On Thu, Jan 04, 2007 at 09:35:16PM -0800, Neal Norwitz wrote:
I fixed the crash that was due to raising a warning on shutdown. I
have heard about crashes at shutdown and wonder if this was the cause.
There might be similar bugs lurking that assume PyModule_GetDict()
always returns a valid
Ron Adam wrote:
Thanks for the link. PEP 287 looks to be fairly general in that it
expresses a general desire rather than a specification.
I thought it was pretty specific. I'd summarize PEP 287 by quoting
entry #1 from its goals of this PEP section:
* To establish reStructuredText as a
Whoever is subscribed to python-dev with a broken corporate
autoresponder that sends everyone who posts to the list this useless
response multiple times please unsubscribe yourself. Its highly
annoying and entirely useless since its not even identifying the list
subscriber(s) deserving the blame.
Larry Hastings wrote:
Ron Adam wrote:
Thanks for the link. PEP 287 looks to be fairly general in that it
expresses a general desire rather than a specification.
I thought it was pretty specific. I'd summarize PEP 287 by quoting
entry #1 from its goals of this PEP section:
* To
28 matches
Mail list logo
