trees. As Python continues to grow in importance[1], the number
of people interacting with Python on the distribution development teams[2]
increases, and therefor the number of people likely to run alphas for
testing increases. So even if Larry were right *now*, he isn't right
for the future, and
though their suitability for specific projects depends on the bugs found.
I think Python *could* be in this camp, if we wanted to be.
(I'm not addressing release-team load here, I'm just making an
observation.)
--David
[1] I am *not* advocating running an alpha in production, but for
ere *were* bug reports during the alpha phase. A number of regressions
were caught. Also, there were more alpha-phase bug reports than
I remember getting for 3.2. I remember thinking, "wow, cool, we're
actually getting regression bug rep
mewhere? I'd like to know more about it.
I believe it was discussed at the Language Summit at the last Pycon.
As I recall there was at least one other person interested in helping
with it, but I don't remember who.
--David
___
Python-Dev
onf that the committer used.
My understanding is that we use a specific version of autoconf.
The reason is that otherwise we end up with useless churn in the repo
as the generated file changes when different committers use different
versions. In the past we have had issues with a new autoconf ve
installer /
> runtime does not need formatted fields at all (only parsing the name,
> version, requirements to do dependency resolution).
Well, if you did want to maintain extensibility, you could go whole
hog and allow MIME types and Content-Type: mulitpart/mixed :)
--David
___
You are more likely to get action on bugs by posting to the bug tracker.
That said, since 8766 was fixed, your issue is most likely a new one.
Please open a new bug report.
--David
On Mon, 22 Oct 2012 16:31:34 +0300, anatoly techtonik
wrote:
> Could anybody reopen http://bugs.python.
cused
on Python bug fixing this Saturday from some time in the AM until about
18:00, GMT -4. If no one else shows up I'll just have a personal bug
day, but I'm guessing at least a few people might show up despite the
lack of a wider formal announcement.
--David
__
cal variable referenced before assignment" *is*
a pointer to the concept of when global variables become local...perhaps
there is a better wording, do you have a suggestion?
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
IDLE in general is an interesting idea, but is not the immediate
question.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
past, I would guess).
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka
wrote:
> Another counterintuitive (and possible wrong) example:
>
>>>> {print('foo'): print('bar')}
>bar
>foo
>{None: None}
http://bugs.python.org/issue11205
--David
___
rack of the location of every assignment
that makes a variable local and writing it in to the .pyc file is a very
non-trivial change to how the Python bytecode compiler works, I think, and
probably not worth the overhead in order to improve this error message.
(And note that raising an error at compile
NONASCII.
>
> This change should improve code coverage on heterogeneous environments.
Alexandre's point was that the string did not appear to be arbitrary,
but rather appeared to specifically be a string containing surrogates.
Is this not the case?
--David
___
way, the .close is only attempted if the open succeeds.
Could you open an issue for this on the tracker, please? That
way we won't forget to fix it.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
> >
> > What convention and typing optimization is this? I hope you aren't
> > suggesting it should be dict("x"=1) or dict("x":1)?
>
> Try the canonical {'x':1}. Only dict allows the special
> initializat
;python-dev" user that way:
> http://bugs.python.org/user13902
I'm pretty sure it's because python-dev is the 'from' address
used when the messages are sent...and the configuration of
that user is what allows them to be accepted.
I
e you reading?
He's reading the operator module documentation. I just ran into that
same thing the other day, but didn't think to file a bug report. It
looks like the ``args`` stuff was incorrectly copy and pasted from the
methodcaller docs, where it is act
mails.
I'm not sure how one would go about integrating the above with an App
Engine app. I suspect that not quite enough information is available
through the XML-RPC interface to replicate that script, but maybe you
could manage just the open-close counting part of it.
did you end up with?
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
The repo I worked on the email features in is still available, too, if
anyone is crazy enough to want to know about those intermediate steps...
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
wants it to stay backward compatible. I'm thinking
specifically of the platform module, which I'm pretty sure has that
restriction. So, it has to be considered on a case by case basis.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://m
s like
> test_pydoc and test___all__ to a separate process might be worth the
> effort.
Adding something to regertest (or unittest?) so that certain nominated
test modules are run in a subprocess has been discussed previously, but
so far no one has stepped up to implement it :) (I think this came up
originally for test_site, but I don't remember for sure.)
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
e. It would be nice if one of the past disutils maintainers
> > > gave their approval too, but they don't seem very active.
> > FWIW I think Nick is perfect for this job.
>
> I meant approval for the PEP, not for Nick :)
Well, if Nick is "perfect" for the job, this
n extended period. It could be that the
nosy committers have just forgotten about it.
In the future, it best way to approach this situation (patch that seems
ready but no action has been taken) is to ping the issue first, and if
you don't get a response after
On Fri, 04 Jan 2013 10:40:10 -0500, Todd V Rovito wrote:
> On Jan 4, 2013, at 10:23 AM, "R. David Murray" wrote:
>
> > On Fri, 04 Jan 2013 10:04:14 -0500, Todd V Rovito
> > wrote:
> >> I submitted a simple patch for updates to IDLE's documentation
On Fri, 04 Jan 2013 18:56:22 +0200, Serhiy Storchaka
wrote:
> On 04.01.13 18:51, R. David Murray wrote:
> > (To automate such monitoring we would need some sort of 'commit ready'
> > flag in the tracker and a protocol for when it gets set...which might
> > not be a
in a cut-and-pasteable fashion.
Perhaps someone will be motivated to work on a fix :)
--David
PS: as long as I'm writing this, Xu, that error you got looks like a
transient error possibly caused by your local name server...if that is
the only failure you got, your Python is working perfectly
the tests, because that
> reminds me of what pickle does.
Handling this case is why having a context-manager form of
import_fresh_module was suggested earlier in this meta-thread. At
least, I think that would solve it, I haven't tried it :)
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
has to be done in setUpModule for test discovery to work
> > +global crypt
> > +crypt = support.import_module('crypt')
>
> Yikes.
> Couldn't unittest support SkipTest being raised at import instead?
> setUpModule is an ugly way to do t
is probably not the best language for
> them.
>
> It is also ironic how the executable size went up since then (from 0.6
> to more than 1.5 MB) :-)
200K can make a difference. It does on the QNX platform, for example,
where there is no virtual memory. It would be nice to reduce that
urllib.urlopen raising
> exceptions and only afterwards realize that you called into some third
> party library code that decided to change the timeout.
What is stopping some some third party library code from calling
socket.settimeout(0.1)?
--David
___
On Sun, 27 Jan 2013 21:56:06 +0100, Ralf Schmitt wrote:
> "R. David Murray" writes:
>
> > On Sun, 27 Jan 2013 19:42:59 +0100, Ralf Schmitt wrote:
> >> Guido van Rossum writes:
> >>
> >> > It's like calling socket.settimeout(0.1)
http://bugs.python.org/issue11344 evolved into a patch for 'splitpath',
similar to splitall. Antoine's pathlib (PEP 428) is also mentioned
at the end, which is probably what Guido is thinking of.
--David
On Wed, 30 Jan 2013 13:26:08 -0800, Guido van Rossum wrote:
> Thought
these that the way to make
progress on it was to break everything down into the to smallest
independent patches possible. So far no one has followed through on
it, obviously.
[And no, I'm not interested in the port myself, either :)]
--David
___
Py
checks is that we prefer to operate via
"duck typing", which means that if an object behaves like the expected
input, it is accepted. Here, if we did an explicit type check for str,
it would prevent join from working on an "act alike" object that had
On Sat, 09 Feb 2013 14:35:33 +, Thomas Scrace wrote:
> R. David Murray bitdance.com> writes:
>
> > The reason we avoid such type checks is that we prefer to operate via
> > "duck typing", which means that if an object behaves like the expected
> > input
On Sat, 09 Feb 2013 13:57:41 -0500, Terry Reedy wrote:
> On 2/9/2013 8:31 AM, R. David Murray wrote:
> Changing AttributeError to TypeError only requires try-except, which is
> cheap if there is no error, not an early type check.
>
> > The reason we avoid such type checks is
If these don't get reported as tracker issues they will probably get
lost.
--David
On Mon, 11 Feb 2013 14:47:00 +, Developer Developer
wrote:
> Same thing in the function: "_parse_doctype_attlist":
>
> if ")" in rawdata[j:]:
> Â Â j = rawdata.find(
build a string doesn't mean that "".join() is the clean
> idiomatic way to do it.
If 'idiomatic' (a terrible term) means "the standard way in this
language", which is how it is employed in the programming community,
then yes, "".join() is the idio
eal
> documentation that explains things in more detail.
> Maybe that could be a way to get people to actually read.
There used to be a HOWTO with this goal, but its opinions were
considered outdated and/or contentious, and it was deleted:
http://docs.python.org/2.6/howto/doanddont.html
-
piler Version 13.10.3077 for 80x86
Copyright (C) Microsoft Corporation 1984-2002. All rights reserved.
--
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
This is the place to say things
like "operating on every character of a string is seldom efficient."
--
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubs
Brett C. wrote:
A few things can be done to make sure that development goes smoothly when
experimenting with Python's bytecode. One is to delete all .py(c|o|w)
Don't you mean ".pyc or .pyo (remember such files in zips as well)"
.pyw is normal python source.
-- Scott
s a new place to pool knowledge.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
PEP.
I can open a pseudo-file for STORED files in binary read mode, for
example, to allow reading zip-in-zip files without fully occupying
memory.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.
Josiah Carlson wrote:
Scott David Daniels <[EMAIL PROTECTED]> wrote:
I'm hoping to add BZIP2 compression to zipfile for 2.5. My primary
motivation is that Project Gutenberg seems to be starting to use BZIP2
compression for some of its zips. What other wish list things do
people aroun
Brett C. wrote:
Scott David Daniels wrote:
I'm hoping to add BZIP2 compression to zipfile for 2.5. My primary
motivation is that Project Gutenberg seems to be starting to use BZIP2
compression for some of its zips. What other wish list things do
people around here have for zipfile? I th
tents.)"
This means to me we can put these in Python's library, but it is
definitely something to start deciding now.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/
." I believe our current policy is that the author
warrants that the code is his/her own work and not encumbered by
any patent.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailma
Terry Reedy wrote:
"Scott David Daniels" <[EMAIL PROTECTED]>
I believe our current policy is that the author warrants that the code
is his/her own work and not encumbered by any patent.
Without a qualifier such as 'To the best of my knowledge', the latter is an
impossibl
one-time-only
overhead you can afford to reduce the per-search-character cost.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.
do
about 300 probes once the table is set (the underscores below):
not the xyznot the xyznot the xyz...
not ther_
not the__
not ther_
not the__
not ther_
...
-- Scott David
cause much code would get broken.
But, is it going to be considered for sometime in the future? 3.0 maybe?
And, would it really break so much code? Wouldn't it instead bring to the
day light many bugs that are already there (but failing in a more silent
way)?
Tha
erhaps your final summary
could be a personal view of PyCon for those of us unable to get there.
If you make no more contribution to Python than you have so far, you
will have done us a great service.
Hip-hip-hooray-ly y'rs
--Scott David Daniels
a twenty-two
page document with no real content. Really, the twenty two pages
included an introduction, conclusion, table of contents, appendix,
and index. It just didn't have anything but section headings. It
was a thrilling triumph of form over function; a real Suahuab
aesthetic, to coi
he data structures with:
converter('flour', 'bread')(BakingClass)
_But_ (at least for the app I was fiddling with) decorating at the top
of declaration helps show the purpose of the class.
Have a look at:
http://aspn.activesta
Brett C. wrote:
... I figured I would take up the idea. So hear
^^ here ^^
we go.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.p
#x27;f\x061.#INF') == 1.0
Should loads raise an exception?
Somehow, I thing 1.0 is not the best possible representation for +Inf.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.o
detect code if that is what is wanted.
I just want to know what the consensus is on the "should." If we cause
exceptions, should they be one encode or decode or both? If not, do we
replicate all NaNs, Infs of both signs, Indeterminates?
--Scott David Daniels
[EMAIL PROTECTED]
__
"not all marshalled float text read");
+ return NULL;
+ }
return PyFloat_FromDouble(dx);
}
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
h
rrent Python "best practice" for what it does, and it
could be really simply made into a live demo of the itertools module.
David.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
to PEP
> 3000 instead.
Since PEP 313 has been rejected, the trailing L no longer introduces
ambiguity in the representation of roman(40) vs. roman(10L).
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://
Chermside, Michael wrote:
> ... I will say that if there were no legacy I'd prefer the tounicode()
> and tostring() (but shouldn't itbe 'tobytes()' instead?) names for Python 3.0.
Wouldn't 'tobytes' and 'totext' be better for 3.0 where text == un
stock profits, rather than a solid value proposition.
Trying to satisfy the profit-lust of angels has redirected more than one
company.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/l
t; I certainly have
use for implementations that can give better guarantees, and I'd
like to be able to distinguish the two.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/li
ackage "py". Would
'std' do as well for the top level, or should we use "python"
for the python-coded versions?
--
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.p
ke groupby() for this sort of
> thing, with the aforementioned caveats. Functional code seems a little
> clearer to me, although I realize that preference is not held
> universally.
However, sorted requires ordering. Try seq = [1, 1j, -1, -1j] * 5
Alex's tally works, but yours does no
ame ancestors as
CheeseShop, but is True simply because issubclass(SillyWalks, Sketch)
is True. More a document issue than anything, but to be considered.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
htt
ot sure about your compiler, but if I remember the standard
correctly, the following code shouldn't complain:
PyObject_CallFunction((PyObject*) (void *) &PyRange_Type,
"lll", start, start+len*step, step)
-- Scott David Daniels
[EMAIL PROTECTED]
Martin v. Löwis wrote:
> Scott David Daniels wrote:
>> ... if I remember the standard
>> correctly, the following code shouldn't complain:
>>
>> PyObject_CallFunction((PyObject*) (void *) &PyRange_Type,
>> "lll"
the code based on old behavior (it might be
nice only when the jailer is around). So, reading your restrictions is
a capability I'd like to be able to control.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python
Rush Limbaugh was detained and questioned for transporting a possible
illegal Viagra prescription into the country.
Well... a least we know his back is feeling better.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev
Aahz wrote:
> On Thu, Jun 29, 2006, Scott David Daniels wrote:
>> .
> I'm hoping this was a typo of an e-mail address for sending, because
> this is not appropriate for python-dev.
This absolutely was a matter of clicking the wrong spot. I completely
agree it would be in
>
>> Maybe 'turtleplus' or something?
>
> When it goes into Python, it will be 'turtle'.
>
Perhaps in the meantime (if xturtle is not loved),
you could go with "turtle_" as in "like the standard
turtle, but my definition."
--
-- Sco
Michael Hudson wrote:
> Gary Robinson <[EMAIL PROTECTED]> writes:
>>... bus error 100% of the time ...:
We've boiled it down pretty far, and I've sent him off to
the mac-python folks (looks gcc-compilerish to me, or maybe
fallout from slight changes in C function call s
.html
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
dynamic blocks with no distance codes
* Fix crc check bug in gzread() after gzungetc()
* Do not return an error when using gzread() on an empty file
I'd guess this belongs in 2.5, with a possible retrofit for 2.4.
--Scott David Daniels
[EMAIL PROT
ass of KeyboardInterrupt or SystemExit.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
may start generating something silly
like divide-by-zero. Not the end of an App, but the end of a Phase.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubsc
s reading from compressed data
sources unnecessarily inefficient.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/opti
Michael Hudson wrote:
> How does a copying gc differ much from a non-copying non-refcounted gc
> here?
One important issue for C coded modules is that addresses may change
when a GC is invoked, so no remembering addresses in your module; you
must recalculate before each use.
-- Scott
emselves:
Installer:
http://members.dsl-only.net/~daniels/dist/to_int-0.10.win32-py2.4.exe
Just the 2.4 dll:
http://members.dsl-only.net/~daniels/dist/to_int-0.10.win32.zip
Sources:
http://members.dsl-only.net/~daniels/dist/to_int-0.10.zip
--Scott David Daniels
[EMAIL PROTEC
Well, wouldn't you know it.
I get the code right and mess up the directions.
Scott David Daniels wrote:
> if you build this module, I'd suggest using
> "from to_int import chomp" to get a function that works like int
> (producing a long when needed and so on).
We
t directory, cd to that dir, and
run test_hi_powers.py. Let me know if the tests pass or fail.
Thanks.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
Since I am fiddling with int/long conversions to/from string:
Is the current behavior intentional (or mandatory?):
v = int(' 5 ')
works, but:
v = int(' 5L ')
f
ated feature
> - Generate deprecation warnings when it is used?
>(This might be too much.)
Perhaps "The __ name convention is designed for 'mixins'; as a means of
enforcing "private" it is both ineffective and annoying. For example,
distutils.msvccompiler uses a
Jeremy Hylton wrote:
> On 12/12/05, Scott David Daniels <[EMAIL PROTECTED]> wrote:
>> Perhaps "The __ name convention is designed for 'mixins'; as a means of
>> enforcing "private" it is both ineffective and annoying. For example,
>> distutils.m
can then easily go in a Python25.zip).
My (admittedly weak) understanding of how packages work is that all
parts of a package should lie off the same node of the PYTHONPATH.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@
Barry Warsaw wrote:
> On Wed, 2005-12-14 at 09:56 -0800, Scott David Daniels wrote:
>> One good reason for this is that the .pyd's or .so's cannot necessarily
>> be used from zip files
> When you say "cannot necessarily", are the situations where they can be
more than a single
process. If the .egg strategy is followed, I expect that either the
file shared is in a user(or even process)-specific location or there
is a shared folder that is writable by many processes from which
executable code can be run. The one solution reduces sharing, the
othe
Michael Chermside wrote:
> ... a meme will spread which says (and PLEASE don't quote this!)
> "ElementTree has a great API, but it's just too slow for real work."
+1 DNQOTW :-) (Do Not Quote Of The Week)
--Scott Davi
g zip formats that
are starting to be created from other sources). Would it make
sense to include bzip2 in here as well (if the zipfile changes
go in)?
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.
ing an explicit __lt__
> isn't much of an extra burden, and will make
> the ordering much more useful for debugging
> and output.
Tell me:
>>> a = [0] * 3
>>> b = [0] * 3
>>> a[0] = b
>>> b[0] = a
What order should a and b have?
--Scott David
"license" for more information.
>>> Let's add another line that says
>>> Type "quit()" to exit
>>> ...
Or, perhaps:
class _Quitter(str):
def __call__(self): raise SystemExit
quit = _Quitter('The quit command. Typ
ttest.TestCase.failureException:
pass
else:
raise BrokenTest(test_method.__name__, reason)
return replacement
wrapper.todo = reason
return wrapper
So your use looks like:
class SomeTests(unittest.TestCase
rator function in unittest.
Here is where the recipe is, for those who want to comment further:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/466288
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
Fredrik Lundh wrote:
> Scott David Daniels wrote:
>> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/466288
>
> my main nit is the name: the test isn't broken in itself, and doesn't need
> to be fixed; it's just not expected to succeed at this time
Fred L. Drake, Jr. wrote:
> Scott David Daniels wrote:
> > Would "expect_fail", "expect_failure", "expected_fail", or
> > "expected_failure", work for you?
>
> None of these use the same naming convention as the other unittest
erting to base-64 and other weird formats, as
well as providing decimal conversion into some unicode number ranges
outside the ASCII group.
--Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/ma
2001 - 2100 of 2106 matches
Mail list logo
