Here's some of my ideas about subject. Maybe some of them are rather
foolish, others -- rather simple and common... I just want to add my 2
cents to Python development.
1) What is the reason for making Python backwards incompatible (let it
be just 'BIC', and let 'BC' stands for 'backwards
Hi!
The current Python profilers situation is a mess.
'profile.Profile' is the ages-old pure Python profiler. At the end of a
run, it builds a dict that is inspected by 'pstats.Stats'. It has some
recent support for profiling C calls, which however make it crash in
some cases [1]. And of
On 11/19/05, Steven Bethard [EMAIL PROTECTED] wrote:
You are missing an important point here: There are intentionally no line
breaks in this string; it must be a single line, or else showerror will
break it in funny ways. So converting it to a multi-line string would
break it, dedent or
[EMAIL PROTECTED] wrote:
I would appreciate feedback concerning these patches before the next
PythonD (for DOS/DJGPP) is released.
PEP 11 says that DOS is not supported anymore since Python 2.0. So
I am -1 on reintroducing support for it.
Regards,
Martin
On Sat, Nov 19, 2005, Armin Rigo wrote:
If anyone feels like this is a bad idea, please speak up.
This sounds like a good idea, and your presentation already looks almost
like a PEP. How about going ahead and making it a formal PEP, which
will make it easier to push through the dev process?
--
Armin Rigo wrote:
If anyone feels like this is a bad idea, please speak up.
As stated, it certainly is a bad idea. To make it a good idea, there
should also be some commitment to maintain this library for a number
of years. So who would be maintaining it, and what are their plans
for doing so?
