On Wed, 25 Jul 2012 13:07:03 +1000, Ben Finney wrote:
Maarten maarten.sn...@knmi.nl writes:
You just missed it:
22/7
Which is appropriate, since 22/7 misses π by a wide margin. (355/113 is
my favourite approximation to π, and is far more accurate.)
Approximation? Pffft. I use the exact
Am 24.07.2012 17:01, schrieb cpppw...@gmail.com:
reader = codecs.getreader(encoding)
lines = []
with open(filename, 'rb') as f:
lines = reader(f, 'strict').readlines(keepends=False)
where encoding == 'utf-16-be'
Everything works fine, except that lines[0] is equal to
On 25/07/2012 07:07, Steven D'Aprano wrote:
On Wed, 25 Jul 2012 13:07:03 +1000, Ben Finney wrote:
Maarten maarten.sn...@knmi.nl writes:
You just missed it:
22/7
Which is appropriate, since 22/7 misses π by a wide margin. (355/113 is
my favourite approximation to π, and is far more
Mark Lawrence breamore...@yahoo.co.uk writes:
Any civil engineers reading this who would find 22/7 perfectly
adequate for their task?
Civil engineering? Pffft, that deals with only a few orders of magnitude
range at most. “π is roughly 3” is usually good enough in that arena :-)
--
\
On 25/07/2012 07:43, Ben Finney wrote:
Mark Lawrence breamore...@yahoo.co.uk writes:
Any civil engineers reading this who would find 22/7 perfectly
adequate for their task?
Civil engineering? Pffft, that deals with only a few orders of magnitude
range at most. “π is roughly 3” is usually
Hi!
I just had an idea, it occurred to me that the pass statement is pretty
similar to the print statement, and similarly to the print() function,
there could be a pass() function that does and returns nothing.
Example:
def pass():
return
try:
do_something()
except:
On 25.07.12 08:09, Ulrich Eckhardt wrote:
Am 24.07.2012 17:01, schrieb cpppw...@gmail.com:
reader = codecs.getreader(encoding)
lines = []
with open(filename, 'rb') as f:
lines = reader(f, 'strict').readlines(keepends=False)
where encoding == 'utf-16-be'
Everything
On Wednesday, July 25, 2012 11:02:01 AM UTC+2, Walter Dörwald wrote:
On 25.07.12 08:09, Ulrich Eckhardt wrote:
gt; Am 24.07.2012 17:01, schrieb cpppw...@gmail.com:
gt;gt; reader = codecs.getreader(encoding)
gt;gt; lines = []
gt;gt; with open(filename, #39;rb#39;) as f:
Unlike the print statement, pass has no overboarding complexity (like
, printing tuples, etc.) - it just serves as a marker (and
practicality beats purity).
And you don't ever want to use pass as a value (say, for map() or the
right side of an assignment). In fact, if pass were a function, users
On Wed, Jul 25, 2012 at 9:40 AM, Ulrich Eckhardt
ulrich.eckha...@dominolaser.com wrote:
What do you think?
I enjoyed the question, but actually I don't think this is a good idea.
1. If you really needed something like this, you could define it easily.
def do_nothing(*args, **keywords):
2012/7/23 Chris Angelico ros...@gmail.com:
That would probably be correct. However, I still think you may be
fighting against the language instead of playing to its strengths.
I've never fiddled with sys.modules like that, but I know some have,
without problem.
ChrisA
--
On Wed, Jul 25, 2012 at 4:40 AM, Ulrich Eckhardt
ulrich.eckha...@dominolaser.com wrote:
What do you think?
retort:
def foo():
None
-- Devin
--
http://mail.python.org/mailman/listinfo/python-list
Hello,
very often I have the following problem: I write a program that processes many
files which it assumes to be encoded in utf-8. Then, some day, I there is a
non-utf-8 character in one of several hundred or thousand (new) files. The
program exits with an error message like this:
On Wed, 25 Jul 2012 10:40:45 +0200, Ulrich Eckhardt wrote:
Hi!
I just had an idea, it occurred to me that the pass statement is pretty
similar to the print statement,
[...]
try:
do_something()
except:
pass()
What's the point of this? If you intend to do nothing,
On 7/25/2012 6:05 AM, jaroslav.dob...@gmail.com wrote:
What I really want to do is use something like
try:
# open file, read line, or do something else, I don't care
except UnicodeDecodeError:
sys.exit(Found a bad char in file + file + line + str(line_number)
Yet, no matter
Hi Jaroslav,
you can catch a UnicodeDecodeError just like any other exception. Can
you provide a full example program that shows your problem?
This works fine on my system:
import sys
open('tmp', 'wb').write(b'\xff\xff')
try:
buf = open('tmp', 'rb').read()
buf.decode('utf-8')
except
On Wednesday, July 25, 2012 1:35:09 PM UTC+2, Philipp Hagemeister wrote:
Hi Jaroslav,
you can catch a UnicodeDecodeError just like any other exception. Can
you provide a full example program that shows your problem?
This works fine on my system:
import sys
open(#39;tmp#39;,
I have some long running processes that do very long simulations which
at the end need to write things on a database.
At the moment sometimes there are network problems and we end up with
half the data on the database.
The half-data problem is probably solved easily with sessions and
sqlalchemy
On 07/25/2012 09:56 AM, andrea crotti wrote:
I have some long running processes that do very long simulations which
at the end need to write things on a database.
At the moment sometimes there are network problems and we end up with
half the data on the database.
The half-data problem is
2012/7/25 Jack tdl...@gmail.com
Since you know the content of what the sql code is, why not just build
the sql file(s) needed and store them so that in case of a burp you can
just execute the code file. If you don't know the exact sql code, dump
it to a file as the statements are
On Tuesday, July 24, 2012 9:09:02 PM UTC+5:30, (unknown) wrote:
Dear Group,
I was looking for the following solutions.
(i) a Python Hidden Markov Model(HMM) library.
(ii)a Python Conditional Random Field(CRF) library.
(iii) I am using Python 3.2.1 on Windows 7(64 bit) and also like to get
On Wed, Jul 25, 2012 at 6:40 PM, Ulrich Eckhardt
ulrich.eckha...@dominolaser.com wrote:
I just had an idea, it occurred to me that the pass statement is pretty
similar to the print statement, and similarly to the print() function, there
could be a pass() function that does and returns nothing.
Ulrich Eckhardt wrote:
I just had an idea, it occurred to me that the pass statement is pretty
similar to the print statement, and similarly to the print() function,
there could be a pass() function that does and returns nothing.
Example:
def pass():
return
try:
On Wed, Jul 25, 2012 at 12:05 PM, Chris Angelico ros...@gmail.com wrote:
Simple way of making the iterator display its yielded result. I cannot
imagine any circumstance in which you'd want to map pass over
everything. But then, as Teresa said, I'm only one, and possibly I'm
wrong!
True. But
Hi,
I'm currently experimenting with IMAP using Python 2.7.3 and IMAP4 from
imaplib. I noticed the performance to be very bad. I read 5000 files
from a directory and append them to an IMAP INBOX. The hole procedure of
reading and appending is taking about 210 seconds.
I set up the exact
On Jul 25, 2012 10:51 AM, Devin Jeanpierre jeanpierr...@gmail.com wrote:
True. But it might be nice to use pass both in lambdas and regular
functions, or to use pass as a variable name.
You can already use pass (or the equivalent) in a lambda.
lambda: None
--
On Wed, Jul 25, 2012 at 2:14 PM, Ian Kelly ian.g.ke...@gmail.com wrote:
You can already use pass (or the equivalent) in a lambda.
lambda: None
This lacks my foolish consistency.
-- Devin
--
http://mail.python.org/mailman/listinfo/python-list
On 07/25/2012 08:09 AM, jaroslav.dob...@gmail.com wrote:
On Wednesday, July 25, 2012 1:35:09 PM UTC+2, Philipp Hagemeister wrote:
Hi Jaroslav,
you can catch a UnicodeDecodeError just like any other exception. Can
you provide a full example program that shows your problem?
This works fine on
On 7/25/2012 11:58 AM, subhabangal...@gmail.com wrote:
As most of the libraries give so many bindings and conditions best way
is to make it. Not very tough, I made earlier, but as some files were
lost so was thinking instead of a remake if ready versions work. Or may
look change from Python 3
Simon Pirschel sp at abusix.org writes:
Hi,
I'm currently experimenting with IMAP using Python 2.7.3 and IMAP4
from imaplib. I noticed the performance to be very bad. I read 5000
files from a directory and append them to an IMAP INBOX. The hole
procedure of reading and
Ulrich Eckhardt wrote:
I just had an idea, it occurred to me that the pass statement is pretty
similar to the print statement,
[...]
try:
do_something()
except:
pass()
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote:
What's the point of this?
Remember
On 07/25/12 12:47, Simon Pirschel wrote:
I'm currently experimenting with IMAP using Python 2.7.3 and
IMAP4 from imaplib. I noticed the performance to be very bad. I
read 5000 files from a directory and append them to an IMAP
INBOX. The hole procedure of reading and appending is taking
about
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote:
What's the point of this?
Ross Ridge wrote:
Remember everything you've said about why its a good thing the that
print statement is now a function? That.
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote:
I can't believe I
On Thu, Jul 26, 2012 at 1:30 PM, Ross Ridge rri...@csclub.uwaterloo.ca wrote:
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote:
I can't believe I actually have to point this out explicitly, but pass is
not print. Apart from them both starting with the letter P, they are
nothing alike.
Ross Ridge rri...@csclub.uwaterloo.ca wrote:
No, they're very much alike. That's why all your arguments for print
as function also apply just as well to pass a function. Your arguments
had very little to do what what print actually did.
Chris Angelico ros...@gmail.com wrote:
Except that
On Jul 26, 11:42 am, Ross Ridge rri...@csclub.uwaterloo.ca wrote:
Remember everything you've said about why its a good thing the that
print statement is now a function? That.
You regularly have the need to override the behaviour of pass?
Are you _really_ saying you see no distinction between
On Jul 26, 1:30 pm, Ross Ridge rri...@csclub.uwaterloo.ca wrote:
No, they're very much alike.
Repetition isn't evidence. You keep making this claim, so support it.
That's why all your arguments for print
as function also apply just as well to pass a function. Your arguments
had very little
Ross Ridge wrote:
Ross Ridge rri...@csclub.uwaterloo.ca wrote:
No, they're very much alike. That's why all your arguments for print
as function also apply just as well to pass a function. Your arguments
had very little to do what what print actually did.
Chris Angelico ros...@gmail.com
Ulrich:
If you take a look at pep 3105 you find five rationales.
http://www.python.org/dev/peps/pep-3105/#rationale
If the first were the only one then your suggestion would have merit.
There are also the other 4 in which pass and print dont really
correspond.
Steven wrote earlier:
I have an
If we want pass(), then why not break() and continue()? And also
def() and class()? for(), while(), if(), with(), we can make them all
callable objects!
Except that they are control statements. They are not objects, they
have no type, and they can never be evaluated in an expression. And
most
Hi python-list,
I wrote a patch for Python 3.2.3 to expose the function
SSL_CTX_set_msg_callback in the module _ssl.
I was actually surprise this function was not already in the
standard library as it is really handy:
SSL_CTX_set_msg_callback() or SSL_set_msg_callback() can be used
to define a
On Wed, Jul 25, 2012 at 8:47 PM, Thiébaud Weksteen thieb...@weksteen.fr
wrote:
Hi python-list,
I wrote a patch for Python 3.2.3 to expose the function
SSL_CTX_set_msg_callback in the module _ssl.
I was actually surprise this function was not already in the
standard library as it is really
Serhiy Storchaka storch...@gmail.com added the comment:
It seems to be the latter: Žiga Seilnacht
Then Misc/ACKS should be corrected too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15444
Chris Jerdonek chris.jerdo...@gmail.com added the comment:
Is there a reason not to correct that spelling in this issue? Otherwise, we
could create a new issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15444
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't know how Doc ACKS is maintained, but I think the devguide is fine as it
stands, whether or not Doc ACKS is preserved or not. People should put
themselves into Misc/ACKS if they made a contribution, period.
If people need to be
Martin v. Löwis mar...@v.loewis.de added the comment:
There was a long-standing opposition by Guido to use UTF-8 in that file, and
also complaints about legibility. Not sure what the current status is.
It doesn't matter much to me, even though the spelling of my name is affected.
--
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15445
___
___
Python-bugs-list
Serhiy Storchaka storch...@gmail.com added the comment:
Well, here is updated patch. Also fixed names of Walter Dörwald (was Walter
D�rwald) and Martin von Löwis in Misc/HISTORY.
All changed files (documentation, ACK-files, Misc/HISTORY) already in UTF-8 and
contains non-ASCII names.
Löwis
STINNER Victor victor.stin...@gmail.com added the comment:
See the PEP 410.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15443
___
___
STINNER Victor victor.stin...@gmail.com added the comment:
The following change is a major change on how Python handles undecodable
filenames on Windows:
-return PyUnicode_DecodeMBCS(s, size, NULL);
+return PyUnicode_DecodeMBCS(s, size, surrogateescape);
I disagree with this change,
Mark Dickinson dicki...@gmail.com added the comment:
[Martin]
The patch that Meador committed is incorrect: METH_NOARGS functions
still take a PyObject* args argument, which will be NULL.
Hmm. I see this usage in a lot of places---e.g. see unicode_capitalize,
unicode_casefold, unicode_title
Marc-Andre Lemburg m...@egenix.com added the comment:
Vincenzo Ampolo wrote:
Vincenzo Ampolo vincenzo.amp...@gmail.com added the comment:
This is a real use case I'm working with that needs nanosecond precision
and lead me in submitting this request:
most OSes let users capture network
STINNER Victor victor.stin...@gmail.com added the comment:
If a file name was invalid byte character, os.chdir() raises
UnicodeDecodeError() instead of WindowsError.
I realized that the problem is in the error handling: raising the OSError fails
with a UnicodeDecodeError because
Atsuo Ishimoto ishim...@gembook.org added the comment:
Yes, I know #13374, that's why I wrote
This is a byte-api issue on Windows, so we may be able to simply skip
this test.
Do you think we need a patch to avoid UnicodeDecodeError raised?
Or should we change test to skip this?
--
Marc-Andre Lemburg m...@egenix.com added the comment:
Thank you for taking the initiative. Regarding use of UTF-8 for text files:
I think we ought to acknowledge that UTF-8 has become the defacto standard
for non-ASCII text files by now and with Python 3 being all Unicode, it
feels silly not
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset a82fd35e28be by Martin v. Löwis in branch '3.2':
Issue #15318: Prevent writing to sys.stdin.
http://hg.python.org/cpython/rev/a82fd35e28be
--
nosy: +python-dev
___
Python
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset fa7d4ecc6357 by Martin v. Löwis in branch '2.7':
Issue #15318: Prevent writing to sys.stdin.
http://hg.python.org/cpython/rev/fa7d4ecc6357
--
___
Python tracker
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15318
___
Mark Dickinson dicki...@gmail.com added the comment:
Agreed that this is at worst a doc issue.
[Antoine]
and in all honesty I don't know the difference between the ** operator
and the built-in pow() function :-)
None, as far as I know, apart from the pow function's ability to take a 3rd
Martin v. Löwis mar...@v.loewis.de added the comment:
I will happily fix it, but if it is wrong one place, then it is wrong
everywhere.
Yes, it is wrong everywhere. METH_NOARGS functions do take an
args argument, see ceval.c:call_function.
--
___
Martin v. Löwis mar...@v.loewis.de added the comment:
Hmm. I see this usage in a lot of places---e.g. see
unicode_capitalize, unicode_casefold, unicode_title etc. in
Objects/unicodeobject.c. So it looks like we're relying on the
(PyCFunction) cast to convert from a one-argument function
STINNER Victor victor.stin...@gmail.com added the comment:
Do you think we need a patch to avoid UnicodeDecodeError raised?
Or should we change test to skip this?
It's a bug, the test should not be skipped. You should get an OSError
because the chdir() failed, not an UnicodeDecodeError.
Martin v. Löwis mar...@v.loewis.de added the comment:
As for your patch: you are missing the point of the test. The file name is
assumed to be valid, despite it not being in the file system encoding.
--
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
IMO, it is ok to skip the test on Windows; it was apparently targeted for Unix.
If we preserve it, we should pick a file name (on Windows) which is encodable
in the file system encoding.
--
___
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset f72965374b2a by Martin v. Löwis in branch '3.2':
Issue #7163: Propagate return value of sys.stdout.write.
http://hg.python.org/cpython/rev/f72965374b2a
--
nosy: +python-dev
Martin v. Löwis mar...@v.loewis.de added the comment:
Thanks for the patch!
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7163
___
New submission from Arseniy sen...@gmail.com:
a=lambda:a
print eval(a + () * 99)
--
components: None
messages: 166378
nosy: senyai
priority: normal
severity: normal
status: open
title: Recursion SIGSEGV
type: crash
versions: Python 2.7, Python 3.3
Martin v. Löwis mar...@v.loewis.de added the comment:
I think this should apply to all systems, and I think the proper escaping is
with ./, see TclpNativeSplitPath (in Tcl's source code).
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
Mark Dickinson dicki...@gmail.com added the comment:
The compiler has no chance to find out. You cast the pointer to
PyCFunction, telling the compiler that it really is a PyCFunction.
True; I was thinking that the compiler should have the necessary information to
warn about the suspicious
Stefan Krah stefan-use...@bytereef.org added the comment:
A quick question: Prior to this patch test_memoryview.py exercised
both mbuf_clear() and memory_clear(). Now gcov shows no coverage.
Is this expected? Is it still possible to construct tests that
exercise the code?
--
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
I think it is sufficient for 2.7, 3.2 and 3.3 to just update the documentation,
as Graham says, using note markup so that it stands out.
I can look at ast.literal_eval as an option for 3.4.
--
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg rep...@bugs.python.org
wrote:
... full C double precision for the time part of a timestamp,
which covers nanoseconds just fine.
No, it does not:
import time
t =
Stefan Krah stefan-use...@bytereef.org added the comment:
Everywhere is nowhere close to the truth. There are tons of
NOARGS functions which have the correct signature.
When I started writing C-extensions, I used the PyObject *unused
idiom. Then I saw Meador's version in so many places in the
Marc-Andre Lemburg m...@egenix.com added the comment:
Marc-Andre Lemburg wrote:
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg rep...@bugs.python.org
wrote:
... full C double precision for the time part of a
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: - duplicate
stage: - committed/rejected
status: open - closed
superseder: - stack overflow evaluating eval(() * 3)
title: Recursion SIGSEGV - Eval Recursion SIGSEGV
___
Python
Marc-Andre Lemburg m...@egenix.com added the comment:
Alexander Belopolsky wrote:
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg rep...@bugs.python.org
wrote:
... full C double precision for the time part of a
Marc-Andre Lemburg m...@egenix.com added the comment:
[Roundup's email interface again...]
x = 86400.0
x == x + 1e-9
False
x == x + 1e-10
False
x == x + 1e-11
False
x == x + 1e-12
True
--
___
Python tracker rep...@bugs.python.org
Jesús Cea Avión j...@jcea.es added the comment:
I think that C standard actually documents the parameter order placement, so
you can left out the last ones in the actual function definition.
So, that this is working is not an accident, it is a C standard requirement.
I think...
--
Ezio Melotti ezio.melo...@gmail.com added the comment:
I don't know about a decent way of doing benchmarks for the changes.
Any recommendation?
You could make a script that uses the timeit module.
If this patch is applied I think it would be good to change
posixpath too.
I agree and I'd
Martin v. Löwis mar...@v.loewis.de added the comment:
Jesús: this is a (common) mistake. Standard C makes it undefined behavior to
call a function with an incorrect number of arguments, see 6.5.2.2p9
# If the function is defined with a type that is not compatible with the
# type (of the
New submission from Anton Barkovsky swarmer...@gmail.com:
webbrowser._invoke opens /dev/null, never closes it and a warning is
printed.
I'm attaching a patch.
The diff looks messy, but I'm just wrapping the code in a try-finally
block, the rest is just indented.
--
components: Library
Martin v. Löwis mar...@v.loewis.de added the comment:
Stefan: not sure whether raising this to python-dev really helps; see also
msg42177, msg58196, issue1648268, and msg75239. Feel free to raise it, though.
--
___
Python tracker
R. David Murray rdmur...@bitdance.com added the comment:
Thanks. Is this warning printed by the webbrowser unit tests? If not can you
see a way to add one that does?
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
Anton Barkovsky swarmer...@gmail.com added the comment:
The warning is printed by the file object when it closes itself in __del__:
ResourceWarning: unclosed file _io.TextIOWrapper name='/dev/null' mode='r+'
encoding='UTF-8'
There isn't much to test, or is there?
--
Anton Barkovsky swarmer...@gmail.com added the comment:
To clarify, I discovered this when I was simply running webbrowser.open
in REPL.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15447
Ross Lagerwall rosslagerw...@gmail.com added the comment:
Are there any webbrowser unit tests?
(this could probably use the new subprocess.DEVNULL constant in 3.3)
--
nosy: +rosslagerwall
___
Python tracker rep...@bugs.python.org
Ramchandra Apte maniandra...@gmail.com added the comment:
[+1 for removing pow from the builtins and shunting three-argument pow to the
math module in Python 500.]
Me too.
Anybody who uses pow with to arguments can use arg1**arg2
Anybody who uses pow with three is doing something
R. David Murray rdmur...@bitdance.com added the comment:
@Anton: That's what I was guessing. If we had a unit test in test_webbrowser
that did the same thing, we'd have seen the resource warning when running the
tests and fixed it. However, it looks like there aren't *any* tests for
Stefan Krah stefan-use...@bytereef.org added the comment:
Here's a patch for 3.3, which consists mostly of tests. A couple of points:
o I removed the len view-len check in PyBuffer_ToContiguous(), since
the function is not documented and silently accepting output buffers
that are too
Anton Barkovsky swarmer...@gmail.com added the comment:
Adding a patch that uses subprocess.DEVNULL instead.
Writing tests for webbrowser should be a separate issue, right?
--
Added file: http://bugs.python.org/file26513/fileclose_devnull.patch
___
Stefan Krah stefan-use...@bytereef.org added the comment:
Ramchandra Apte rep...@bugs.python.org wrote:
[+1 for removing pow from the builtins and shunting three-argument pow to
the math module in Python 500.]
Anybody who uses pow with three is doing something mathematical and has most
Mark Dickinson dicki...@gmail.com added the comment:
Wouldn't that reinforce the misconception that math is for arbitrary
precision number theoretical functions?
Perhaps. We already have math.factorial, though; adding math.powmod wouldn't
seem so much of a stretch. Just to be clear, I'm
R. David Murray rdmur...@bitdance.com added the comment:
You could do it either way. Normally we prefer to have a test along with any
fix; in this case adding a test involves adding the test module as well, but it
is not different in principle. If you want to work on it and prefer to have it
Meador Inge mead...@gmail.com added the comment:
While looking this up in the C Standard (ISO/IEC 9899:TC3) I also noticed
6.3.2.3p8:
A pointer to a function of one type may be converted to a pointer to a function
of another
type and back again; the result shall compare equal to the original
Richard Oudkerk shibt...@gmail.com added the comment:
Is it possible that the use of test.support.gc_collect() in test_memoryview
made the difference?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14930
Chris Jerdonek chris.jerdo...@gmail.com added the comment:
To be clear on this issue's scope, I would state in a single comment a white
list of which directories or individual files are being corrected (or if
necessary, the rules to determine such a list, e.g. any file whose name root is
Ezio Melotti ezio.melo...@gmail.com added the comment:
Make sure that it's still possible to generate the pdf of the docs (with `make
latex` and then `make all-pdf` in build/latex/).
Latin1 should be fine, but IIRC non-latin1 will break (sorry Žiga).
--
nosy: +ezio.melotti
Ezio Melotti ezio.melo...@gmail.com added the comment:
FWIW including Misc/ACKS in the doc will probably break the generation of the
pdf version of the doc, since it contains non-latin1 characters (see
msg166408). I don't think it's necessary to include the names in the doc.
I don't know
Martin v. Löwis mar...@v.loewis.de added the comment:
OK, I propose to completely drop the Doc/ACKS.txt from the documentation, and
replace it with the words
Many people have contributed to the Python language, the Python standard
library, and the Python documentation. See Misc/ACKS in the
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't think the docs should display Misc/ACKS. Instead, I propose the
following wording
Many people have contributed to the Python language, the Python standard
library, and the Python documentation. See Misc/ACKS in the Python source
1 - 100 of 161 matches
Mail list logo
