On Fri, Dec 4, 2009 at 17:20, Antoine Pitrou wrote:
> Hello,
>
> I was going to suggest adding ccbench and iobench to the Tools directory,
> so I wonder whether there are any rules for putting stuff there?
>
>
Much like the Demos directory, there are no rules.
-Brett
> Thank you
>
> Antoine.
Hello,
I was going to suggest adding ccbench and iobench to the Tools directory,
so I wonder whether there are any rules for putting stuff there?
Thank you
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
I can't afford to attend PyCon beyond the language summit and the conference
itself this year (down to about my last year of my PhD and need every last
dime I have left in saving to avoid school debt), so for the first time
since PyCon started back in 2003, I have to miss out on attending the
sprin
I ran across this while trying to upgrade our company's internal Windows CE
build from 2.5.2 to either 2.6 or 3.1.
In the 2.5 era, the Windows version of make_buildinfo used to fall back to
just copying the getbuildinfo.c file from \Modules if subwcrev failed; since
2.6, make_buildinfo fails the b
ACTIVITY SUMMARY (11/27/09 - 12/04/09)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2501 open (+17) / 16755 closed (+14) / 19256 total (+31)
Open issues with patches: 998
Average
"Martin v. Löwis" writes:
> Well, python-dev and the PSF have not much to do with each other,
> either. You can reach the PSF at p...@python.org.
Okay, thanks.
Folks, I consider this thread on ‘python-dev’ done. I'll start again
with a new thread crossing between the PSF at the address Martin g
Ben Finney wrote:
> On 03-Dec-2009, Benjamin Peterson wrote:
>> Hi Ben,
>> Could I ask why you cced this to python-dev, too? I thought the last
>> string of pypi related emails, we agreed the correct place for this
>> was the catalog-sig.
>
> I did consider that. But it seems this change is being
