On 1/8/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
>
> many test frameworks support "expected failures" for this purpose.
> how hard would it be to add a
>
> unittest.FailingTestCase
>
> class that runs a TestCase, catches any errors in it, and signals an
> error ("test foo passed unexpectedly
On 1/8/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Georg Brandl wrote:
> > >>> "%f" % 1.0
> > '1.00'
> > >>> u"%f" % 1.0
> > u'1,00'
> >
> > Is this intended? This breaks test_format on my box when test_builtin
> > (method
> > test_float_with_comma) is executed first.
>
> No. %-fo
On 1/8/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
> > I know very little about locale's. /f assigned me a bug
> > http://python.org/sf/1391872 which suggests I run all the tests in a
> > different locale than C. I think this
On 1/8/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Georg Brandl wrote:
> > >>> import locale
> > >>> locale.setlocale(locale.LC_NUMERIC, "")
> > '[EMAIL PROTECTED]'
> > >>> u"%f" % 1.0
> > u'1,00'
> >
> > Is this intended? This breaks test_format on my box when test_builtin
> > (meth
On 1/9/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> ...
>
> [Tim]
> >> That's no more or less painful than using C99's huge pile of PRId8,
> >> PRId16, PRId32 (etc, etc) macros, defined there for similar purposes.
>
> [Martin]
> > Right - and I consider them just as painful.
> >
> > If you believe t
On 1/9/06, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> I'd like to create a patch for the logging package, but before I do, I
> need to know whether someone else is working on the package and whether
> my patch is likely to be accepted. Is there another group I should talk to?
Vinay (copied) main
On 1/9/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> >
> > I would have expected the first call to setlocale() to return de_DE.
>
> No, it shouldn't. We are providing C semantics here, which is that
> no locale functionality is activated unless the application explicitly
> asks for it.
Thanks
On 1/10/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
> centurion:~ > python < .
> Segmentation fault
I fixed that in Oct in head and 2.4 branch. Although Skip filed a bug
since Py_FatalError() is called which generates a core dump in debug
builds at least. http://python.org/sf/1353504
I'm no
On 1/10/06, Trent Mick <[EMAIL PROTECTED]> wrote:
> [Fredrik Lundh wrote]
> > Can buildbot deal with custom test/validation scripts, and collect the
> > output
> > somewhere ?
>
> Yes, it should be able to. However, it might change the part of the the
> master.cfg file that defines the build steps
On 1/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> One concern might be performance. All buildbot slaves are contributed
> hardware. I don't mind the load on my Mac (it's a dual processor g5), but
> it may be an issue for other people.
I've "contributed" 2 machines. One is my personal
On 1/17/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> > The difference between hex() and oct() and the proposed binary() is
>
> I'd propose bin() to stay in line with the short abbreviated names.
Are these features used enough to have 3 builtins?
Would format(number, base) suffice?
format
On 1/10/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>
> We'd also have to make sure that old extensions don't
> just import with a warning, since the change will introduce
> buffer overflows and seg faults in extensions that are not
> aware of the change.
I agree that on 64-bit platforms we shoul
On 1/18/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> Guido, we may be converging on a consensus for my proposal:
>
> base(value, radix=2)
>
> So far no one has shot at it, and it has gathered +1's from Steven,
> Alex, Brett, and Nick.
+1 for me too, but I'd also like to deprecate hex() a
I would really like to stabilize a bunch of the current rough edges in
2.5. We are likely to have enough instability with the PEP 353
changes, so it would be better to fix some of these issues sooner
rather than later. There are a bunch of tests that are not stable.
It would really help to get p
On 1/11/06, Trent Mick <[EMAIL PROTECTED]> wrote:
> > > Does that make sense? We would just need /f's script in SVN.
> >
> > in python/Tools/something or sandbox/something ?
>
> python/Doc/tools/something?
Fredrik were you still working on that? I can make the changes to the
bb master. I though
On 1/25/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
> Because the server doesn't set listener_ready until after the server
> has done listen(), and the client waits for that event, it "should
> be" 100% reliable that the client's connect() succeeds.
>
> Or do you have some other race in mind?
Tha
On 1/26/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> any progress ? does the script work in the buildbot setting, or
> does it need tweaking ?
I haven't gotten to it and won't be able to in the next week+. If no
one beats me to it, I will get to it in a few weeks. I've got most of
the buildbo
On 2/7/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> >
> > what's the current release plan for Python 2.5, btw? I cannot find a
> > relevant PEP, and the "what's new" says "late 2005":
> >
> but I don't think that anyone followed up on this. what's the current
> status ?
Guido and I had a brief
On 2/7/06, Christopher Armstrong <[EMAIL PROTECTED]> wrote:
>
> > Twisted is wonderful, powerful, rich, and very large. Perhaps a small
> > subset could be carefully extracted
>
> The subject of putting (parts of) Twisted into the standard library
> comes up once every 6 months or so, at least on
On 2/7/06, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
> It looks like we need a Python 2.5 Release Schedule PEP.
Very draft: http://www.python.org/peps/pep-0356.html
Needs lots of work and release managers. Anthony, Martin, Fred, Sean
are all mentioned with TBDs and question marks.
n
On 2/11/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>> [Tim telling how I broke pyuthon]
> [Martin fixing it]
Sorry for the breakage (I didn't know about the Windows issues).
Thank you Martin for fixing it. I agree with the solution.
I was away from mail, ahem, "working".
n
_
On 2/10/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> Next, the schedule. Neal's draft of the schedule has us releasing 2.5
> in October. That feels late -- nearly two years after 2.4 (which was
> released on Nov 30, 2004). Do people think it's reasonable to strive
> for a more aggressive (by
On 2/10/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
> I am not experienced in releasing, but with the multitude of new things
> introduced in Python 2.5, could it be a good idea to release an early alpha
> not long after all (most of?) the desired features are in the trunk?
In the past, all new
501 - 523 of 523 matches
Mail list logo
