ver executed to ensure
that there is no other forgiven testcase?
Victor
Le vendredi 01 juillet 2011 à 03:06 +0200, victor.stinner a écrit :
> http://hg.python.org/cpython/rev/00a874ad4fc9
> changeset: 71104:00a874ad4fc9
> branch: 3.2
> parent: 71101:7c60c1b41da9
> user:
Le vendredi 01 juillet 2011 à 11:24 +0200, Antoine Pitrou a écrit :
> On Thu, 30 Jun 2011 23:25:59 +0200
> victor.stinner wrote:
> > http://hg.python.org/cpython/rev/0c49260e85a0
> > changeset: 71103:0c49260e85a0
> > user:Victor Stinner
> > date:
Le vendredi 01 juillet 2011 à 08:17 -0400, Tim Lesher a écrit :
> On Thu, Jun 30, 2011 at 15:13, Ulrich Eckhardt
> wrote:
> > Hi!
> >
> > This is a request for clarification for the thread "how to call a function
> > for
> > evry 10 seconds" from the user mailinglist/newsgroup.
> >
> >
> > The gi
Le vendredi 01 juillet 2011 à 14:55 +0200, Ross Lagerwall a écrit :
> On Fri, 2011-07-01 at 11:18 +0200, Victor Stinner wrote:
> > I tried to find which commit removes TemporaryFileTests from the
> > testcase list (to see if there is a good reason to do that, or if it's
>
Le vendredi 01 juillet 2011 à 16:43 +0200, Antoine Pitrou a écrit :
> On Fri, 1 Jul 2011 09:38:04 -0500
> Brian Curtin wrote:
> > On Fri, Jul 1, 2011 at 09:01, David P. Riedel wrote:
> >
> > > Hi
> > >
> > > Python 3.2.1 was scheduled to be released on 6/19, I believe but there is
> > > no menti
Le vendredi 01 juillet 2011 à 17:54 +0200, r.david.murray a écrit :
> http://hg.python.org/cpython/rev/f8ece8c93918
> changeset: 71119:f8ece8c93918
> branch: 3.2
> parent: 71117:3f30cfe51315
> user:R David Murray
> date:Fri Jul 01 11:51:50 2011 -0400
> summary:
> #118
Le lundi 04 juillet 2011 à 18:23 +0200, Antoine Pitrou a écrit :
> On Mon, 04 Jul 2011 18:06:53 +0200
> victor.stinner wrote:
> > http://hg.python.org/cpython/rev/7eef821ab20d
> > changeset: 71197:7eef821ab20d
> > user:Victor Stinner
> > date:
Le mardi 05 juillet 2011 11:49:03, Antoine Pitrou a écrit :
> On Tue, 05 Jul 2011 04:11:45 +0200
>
> ned.deily wrote:
> > LIBSUBDIRS=tkinter tkinter/test tkinter/test/test_tkinter \
> >
> > tkinter/test/test_ttk site-packages test \
> >
> > - test/capath \
> > +
Le mardi 05 juillet 2011 à 07:59 -0400, Eric Smith a écrit :
> On 7/4/2011 8:28 AM, victor.stinner wrote:
> > http://hg.python.org/cpython/rev/4f14050a963f
> > changeset: 71194:4f14050a963f
> > user: Victor Stinner
> > date:Mon Jul 04 14:28:45 2011 +02
---
PEP: xxx
Title: Deprecate codecs.StreamReader and codecs.StreamWriter
Version: $Revision$
Last-Modified: $Date$
Author: Victor Stinner
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 28-May-2011
Python-Version: 3.3
Abstract
io.TextIOWrapper and
Le 07/07/2011 03:16, Benjamin Peterson a écrit :
2011/7/6 Victor Stinner:
codecs.open() will be changed to reuse the builtin open() function
(TextIOWrapper).
This doesn't strike me as particularly backwards compatible, since
you've just enumerated the differences between StreamWri
Le 07/07/2011 05:26, Nick Coghlan a écrit :
Victor, could you please check this into the PEPs repo? It's easier to
reference once it has a real number.
How do I upload it? Should I contact a PEP editor? How?
Victor
___
Python-Dev mailing list
Python-D
Le 07/07/2011 10:07, M.-A. Lemburg a écrit :
The PEP's arguments for deprecating two essential codec design
components are very one sided, by comparing "issues" to "features".
Yes, please help me to write an unbiased PEP. I don't know which tool is
more appropriate to write a PEP with many autho
Le 07/07/2011 13:43, Nick Coghlan a écrit :
Or just check it in to hg.python.org/peps (claiming the next number in
sequence - 400 at the time of writing this email). I asked if that
approach was OK quite some time ago and David said yes - PEP 1 is
written the way it is because not everyone that w
Le 07/07/2011 12:53, Vinay Sajip a écrit :
I've no issue with telling people to use open() rather than codecs.open() when
moving code from 2.x to 3.x. But in 2.x, is there any other API which allows you
to wrap arbitrary streams?
Yes, io.TextIOWrapper.
Victor
___
B. Retain the full codecs module API, but reimplement relevant parts
in terms of the io module.
This solution would not break backward compatibility, or less than my
PEP. I didn't try to implement this solution. It should be possible for
StreamReader (-> TextIOWrapper), StreamWriter (-> TextIO
Le 07/07/2011 19:33, Terry Reedy a écrit :
On 7/7/2011 7:28 AM, Antoine Pitrou wrote:
The main point of the PEP, IMO, is actually the deprecation itself. By
deprecating, we signal that something isn't actively maintained
anymore, and that a (allegedly better) alternative is available.
I think t
Le 14/07/2011 13:33, Georg Brandl a écrit :
Would it make sense to not propagate the signal in one case (e.g. SIGUSR1),
i.e. just display the traceback in this case?
I opened this issue for buildbots. If the test suite doesn't fail
anymore because of a SIGALRM or SIGUSR1, we may miss a bug i
Done:
changeset: 71337:66e519792e4c
tag: tip
user:Victor Stinner
date:Thu Jul 14 22:28:36 2011 +0200
files: Lib/cgi.py Lib/test/test_cgi.py Misc/NEWS
description:
Add cgi.closelog() function to close the log file
Le 14/07/2011 14:57, Ezio Melotti a écrit
Le 20/07/2011 17:58, Éric Araujo a écrit :
Do we have a policy of not adding new test files to stable branches?
New logging tests failed during some weeks. If we add new tests, we may
also break some stable buildbots. I don't think that we need to add
these new tests to a stable version.
Vict
On 21/07/2011 00:07, Vinay Sajip wrote:
Victor Stinner haypocalc.com> writes:
New logging tests failed during some weeks. If we add new tests, we may
also break some stable buildbots. I don't think that we need to add
these new tests to a stable version.
Just for my informatio
Arguments in favor of specific errors
-
Using specific errors avoids the need of "import errno". The import is
sometimes done in the except block, which may raise a new error (and may
be slow).
I like specific exceptions because it avoids the need of re-raise
On 25/07/2011 02:24, Antoine Pitrou wrote:
Hello,
By the way, is it faster to not handle and than re-raise unwanted
exceptions?
You mean "is it faster to not handle than re-raise unwanted
exceptions?". It probably is, yes.
I asked if:
try:
...
except FileNotFound:
pass
is faster than
Hi,
Three weeks ago, I posted a draft on my PEP on this mailing list. I
tried to include all remarks you made, and the PEP is now online:
http://www.python.org/dev/peps/pep-0400/
It's now unclear to me if the PEP will be accepted or rejected. I don't
know what to do to move forward. I ask
Hi,
Three weeks ago, I posted a draft on my PEP on this mailing list. I
tried to include all remarks you made, and the PEP is now online:
http://www.python.org/dev/peps/pep-0400/
It's now unclear to me if the PEP will be accepted or rejected. I don't
know what to do to move forward.
Vic
Le 28/07/2011 00:36, Guido van Rossum a écrit :
Sorry Victor, I somehow didn't see that message even though I received
it (I probably thought it was a continuation of the python-dev thread
which I've been ignoring).
No problem.
no, there's no particular hurry
That's why it's a deprecation p
Le 28/07/2011 06:10, Benjamin Peterson a écrit :
there any reason to continue using codecs.open()?
It's the easiest way to write Unicode friendly code that spans both 2.x and 3.x.
Even on 2.6, where the io module exists?
io on 2.6 is fairly broken and dead slow. The advantage of codecs.open
Le 28/07/2011 11:03, M.-A. Lemburg a écrit :
Victor Stinner wrote:
Hi,
Three weeks ago, I posted a draft on my PEP on this mailing list. I
tried to include all remarks you made, and the PEP is now online:
http://www.python.org/dev/peps/pep-0400/
It's now unclear to me if the PEP wi
Le 28/07/2011 11:28, Victor Stinner a écrit :
Please do keep the original implementation
around (e.g. renamed to codecs.open_stream()), though, so that it's
still possible to get easy-to-use access to codec StreamReader/Writers.
I will add your alternative to the PEP (except if you would
ous
call to os.unlink().
The module list is hardcoded: it's the list of CPython modules written in C.
More informations about Fusil:
http://fusil.hachoir.org/trac
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mail
Hi,
I filled 14 issues about bugs found by fuzzing (see my other email "Play with
fuzzing" for more informations). Most bugs are now closed, cool :-) Last
bugs:
== Trivial open bugs ==
segfault on locale.gettext(None)
- http://bugs.python.org/issue3302
- attached patch is trivial: fix the PyA
have to be reviewed.
(b) Fix PyObject_Del/PyObject_DEL to remove object from the object list
(c) Create new macro which is PyObject_Del/PyObject_DEL + remove the object
from the list
(d) Never use Py_TRACE_REFS :-)
I wrote many informations in http://bugs.python.org/issue32
Hi,
Le Saturday 19 July 2008 15:14:44, vous avez écrit :
> Thank you Victor - I didn't want to change any underlying
> multiprocessing code until we had the test suite in a better state
> (which we do now) (...)
>
> One suggestion would be to include tests to prove the bugs is fixed if
> possible
file.
It's hard to check bytecode without execute it. It's maybe better to add
checks directly in the VM.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/m
Le Monday 21 July 2008 15:33:19 A.M. Kuchling, vous avez écrit :
> On Sun, Jul 20, 2008 at 10:45:39PM +0200, Victor Stinner wrote:
> > Hum... how can I say it? It's trivial to crash _sre :-) So I blacklisted
> > _sre.compile() in my fuzzer.
>
> We should certainly try
Hi,
Since Python 2.4 (maybe 2.2 or older), fileobj.read(4.2) displays an error and
works as fileobj.read(4).
>>> i=open('/etc/issue')
>>> i.read(4.2)
__main__:1: DeprecationWarning: integer argument expected, got float
It should raises an error instead of a warning, it has no sense to read a
p
ion "strict mode" which disallow dangerous
cast? Especially in PyArg_Parse*() functions.
--
I hate "transparent" cast, like C and PHP do everywhere. The
worst "transparent" cast in Python (2.x) is between str (bytes) and u
Guido van Rossum wrote:
The underscore at the beginning of _sre clearly indicates that the module is
not recommended for direct consumption, IMO. Even the functions that don't
themselves start with an underscore...
I've written a re-code verifier for the Google App Engine
... which means tha
l ctypes module and Python 2.5 with
included ctypes)
I have no other computer to test other CPUs :)
ctypes allows to write code working on CPython 2.4, 2.5, 2.6 and 3.0 (with
2to3), but also on PyPy! Jython plans also to support ctypes.
So, please, retry ctypes ;-)
--
Victor Stinner aka
Hi,
Le Saturday 16 August 2008 15:43:28 Facundo Batista, vous avez écrit :
> The test_raiseMemError() in test_unicode.py is complicating me the
> regression tests: tries to use all the memory in my system, which
> starts to swap as crazy, and almost freezes everything.
On UNIX, it's possible to l
a new
type).
Convert bytes to unicode (replace)
----------
unicode_filename = unicode(bytes_filename, charset, "replace")
Ok, you will get valid unicode strings which can be used in os.path.join() &
friends, but open() or unlink() will fails because this fil
Le Saturday 27 September 2008 14:04:25 Victor Stinner, vous avez écrit :
> I read that Python 2.6 is planned to Wednesday. One bug is is still open
> and important for me: Python 2.6/3.0 are unable to use filename as byte
> strings. http://bugs.python.org/issue3187
Ooops, as amaury not
review and/or discussion (on the mailing list or the bug tracker. So I
will after the final versions (2.6 and 3.0) to commit. Or would it be
possible to have a "mentor"? Someone to ask questions about Python SVN/bug
tracker, or someone who reviews my patchs/commits.
--
Victor St
t:
-
$ 2to3 -d test.rst
(...)
RefactoringTool: Can't parse test.rst: ParseError: bad input: type=28,
value='==', context=('', (2, 0))
(...)
-
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
king the
permissions and arguments). So is there somewhere a document to explain to
current status of Python security?
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
posts are about the best you are going
> to find
I will try to write a document about Python and security next week.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/
impossible because on of his
filename was invalid (maybe a file from a Windows system). So he switched to
raw (bytes) filenames.
In a perfect world, everybody uses Linux with utf-8 filenames and only
programs in Python using space indentation :-D
--
Victor Stinner aka haypo
http://www.haypoca
the operating system expects
bytes? To get the best compatibility, we have to use the native types, at
least when str(filename, fs_encoding) fails and/or str(filename,
fs_encoding).encode(fs_encoding) != filename.
--
Victor Stinner aka haypo
http://w
creen, he can uses:
text = str(filename, fs_encoding, "replace")
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
we don't
choose the right solution.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/
Patches are already avaible in the issue #3187 (os.listdir):
Le Monday 29 September 2008 14:07:55 Victor Stinner, vous avez écrit :
> - listdir(unicode) -> unicode and raise an error on invalid filename
Need raise_decoding_errors.patch (don't clear Unicode error
> - listdir(b
#x27;re right. So i wrote a new patch: os_getcwdb.patch
With my patch we get (Python3):
* os.getcwd() -> unicode
* os.getcwdb() -> bytes
Previously in Python2 it was:
* os.getcwd() -> str (bytes)
* os.getcwdu() -> unicode
--
Victo
y call longjmp(),
smaller stack might also works.
Does other VM support such feature? JVM, Mono, .NET, etc. ?
I had the idea of catching SIGSEGV after reading the issue 1069092 (stack
overflow because of too many recursive calls).
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
en(filename):
...
We need an "if" to choose the directory. The second "if" is only needed to
display the filename. Using bytes, it would be possible to write better code
detect the real charset (eg. ISO-8859-1 in a UTF-8 file system) and so
display correctly the filena
coded
in ISO-8859-1 whereas the second argument is encoding in Unicode. It's
something like that:
str(b'dossi\xc3\xa9', 'ISO-8859-1') + '/' + 'fichi\xe9'
Whereas the correct (unicode) result should be:
'dossié
Le Tuesday 30 September 2008 01:31:45 Adam Olsen, vous avez écrit :
> The alternative is not be valid unicode, but since we can't use such
> objects with external libs, can't even print them, we might as well
> call them something else. We already have a name for that: bytes.
:-)
__
Modules/posixmodule.c | 83
++
5 files changed, 62 insertions(+), 65 deletions(-)
TODO:
- review this patch :-)
- support non-ASCII bytes in fnmatch.filter()
- fix other functions, eg. posixpath.isabs() and fnmatch.fnmatchcase()
- fix
ly as part of this patch, but somewhere related? I
> don't know what they would do, but it does seem quite likely that code
> which was previously correct under 2.6 (using bytes) would suddenly be
> mixing bytes and unicode with these APIs.
It looks like 2to3 convert all text '
to change the existing code, but it doesn't fix the problem, it's just
move problems which be raised later.
I didn't get an answer to my question: what is the result + ? I guess that the result is
instead of raising an error
(invalid types). So again: why introducing a new type inste
r getcwd)
and fix the test_unicode_file.py
listdir() change (ignore invalid filenames) is important to avoid strange bugs
in os.path.*(), glob.*() or on displaying a filename.
I can generate a specific patch for these issues. It's just a subset of my
last patch.
--
Victor Stinner aka
I don't know if it would help the discussion, but Java uses its own modified
UTF-8 encoding:
* NUL byte is encoded as 0xc0 0x80 instead of 0x00
* Java doesn't support unicode > 0x (boh!)
http://java.sun.com/javase/6/docs/api/java/io/DataInput.html#modified-utf
.getcwdu() and introduces os.getcwdb(). A fixer should
replace "os.getcwdu()" to "os.getcwd()". See for example attached fixer
(which also replaced "getcwdu()" to "getcwd()").
--
Victor Stinner aka haypo
http://www.haypocalc.com/
008-09-30)
http://bugs.python.org/issue4004
|--> trivial fix
\--> patch
=== Improvments ===
Support bytes for os.exec*() (2008-10-03)
http://bugs.python.org/issue4035
Support bytes for subprocess.Popen() (2008-10-03)
http://bugs.python.org/issue40
wait for
Python 3.1 (maybe 3.0.1)?
--
People wants to try the new Python version! Python3 introduces new amazing
features like "keyword only arguments". The bytes/unicode problem is old and
only affects broken systems
Windows (90% of the computers in the world?) only uses characters
ed 39 days ago
+ reviewed by amaury and georg.brandl
http://bugs.python.org/issue3880 (fix _tkinter._flatten)
+ patch posted 44 days ago
+ reviewed by gpolo
http://bugs.python.org/issue3632 (ensure GIL in _PyObject_Dump)
+ patch posted 70 days ago
+ reviewed by amaury
--
Victor Stinner
roject. I contributed to
many many projects, and I can say that Python is already one of the most
reactive project! But it can be better ;-)
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python
st on the HTML view)? It helps to see quickly many
informations and generates smaller reports. We can have an icon for each
keyword.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
some types are missing)
Some functions to ease ctypes development:
http://python-ptrace.hachoir.org/trac/browser/trunk/ptrace/ctypes_tools.py
- bytes2type() and bytes2array() are useful to convert a bytes array
to a ctypes object
Should I open issues?
--
Victor Stinner aka haypo
http://
obox
change).
About the old issues, is it possible to write a script setting the stage using
the same rules (using the keywords and status)?
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
to speed up Python.
With my last patch, with GMP, Python is 2% *slower*.
My patch can be improved, but I expected +20% to +100% to no -2% :-/
And there is also the license issue...
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-D
% (Python is slower with GMP). I used pystone which is not a
math application.
More details at:
http://bugs.python.org/issue1814
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.p
sts more than using a smaller base. Only a benchmark
can answer ;-)
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail
d somewhere
that someone wrote a document explaining how to port a C extension to
Python3.
What about a link to the "What's new in Python 2.6" document? Most people are
still using Python 2.4 or 2.5. And Python3 is Python 2.5 + + .
--
Victor Stinner aka haypo
http://www.hayp
beta phase (so far to
be stable and robust). Or can we at least include the needed patches?
Especially th threading + fork issue:
http://bugs.python.org/issue874900
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev m
.000.000 integers
=> don't use pystone!
I don't have a solution working on any CPU with all numbers, this email is
just a summary of the interesting integer patches.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Pytho
applied to 2.6?
All optimisations patches are long and may introduce new regressions. It's
better to wait for 2.7/3.1.
But it would be nice to get numbits() method (or property?) in Python 3.0(.1)
and/or Python 2.6.1.
--
Victor Stinner aka haypo
htt
> n.numbits: method or property?
Fredrik Johansson and me agree to use a property.
My last patch (numbits-4.patch) implement numbits as a property. Examples:
>>> (1023).numbits
10
>>> x=1023L; x.numbits
10L
>>> x=2**(2**10); x.numbits
1025L
>>> x=2**(2**10); x.numbits.numbits # combo!
11L
Vict
.5)
>>> (d - epoch) / timedelta(seconds=1) # integer
34930.5
>>> (d - epoch) // timedelta(seconds=1) # float
34930L
datetime.totimestamp() can be implemented to produce a float in range [-2**31;
2**31-1]. Why a float? To be symetric with fromtimestamp()! If you need
old
> datetime.totimestamp() can be implemented to produce a float in range
> [-2**31; 2**31-1]
An implementation of this method is proposed as a patch in issue #2736.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailin
ess natural (pythonic?) than:
dt // timedelta(days=7)
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
Le Saturday 15 November 2008 02:01:42 Victor Stinner, vous avez écrit :
> > 1- convert a datetime object to an epoch value (numbers of seconds since
> >the 1st january 1970), eg. with a new totimestamp() method
> > 2- convert a timedelta to a specific unit (eg. seconds, da
Le Tuesday 18 November 2008 11:03:02 Facundo Batista, vous avez écrit :
> 2008/11/17 Barry Warsaw <[EMAIL PROTECTED]>:
> > Martin suggests, and I agree, that we should release Python 3.0 final and
> > 2.6.1 at the same time. Makes sense to me. That would mean that Python
> > 2.6.1 should be ready
subprocess.Popen is much SLOWER than os.popen() on Mac and Solaris.
The goal is to read the output of a command (through a pipe) as fast as
possible. The problem is the pipe buffering (the reader file in the Python
process).
Today, subprocess.Popen() uses bufsize=0 by default. It should be
buf
>
> Did you use the suppressions file as suggested in Misc/README.valgrind?
>
>--suppressions=Misc/valgrind-python.supp
To be able to use the suppressions, Python have to be compiled with
Py_USING_MEMORY_DEBUGGER. Edit Object/obmalloc.c near line 680.
--
Vi
lease, don't do that! Bytes are not characters!
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailm
iables is a regression from Python2 (for my program). On
UNIX, filenames are bytes and the environment variables are bytes. For the
best interoperability, Python3 should support bytes. But the default choice
should always be characters (unicode) and to never mix the bytes and str
types
Hi,
I started to write a short article about Python security on the wiki:
http://wiki.python.org/moin/Security
Nothing useful yet.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http
this:
I prefer the current behaviour :-)
> Why do you think that glob.glob('*.py') is special and should not traceback?
It's not special. glob() reuses listdir(), and it was an example to show
that "it just works".
> I just differ in that I think lack of tracebacks
> ('strict', 'ignore', 'replace', 'xmlcharrefreplace')
replace (or xmlcharrefreplace) is just useless because you will not be unable
to open or rename the file... You just know that there is a strange file in
the directory.
___
Python-Dev mailing list
ameEx()).
I would appreciate a review, especially for the patch in Python/ceval.c.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscri
eg. for the GIL, I call PyGILState_Ensure()
- etc.
I choosed the exceptions MemoryError and ArithmeticError, but we could use
specific exceptions based on BaseException instead of Exception to avoid
catching them with "except Exception: ...".
on is totally broken after a segfault, it is maybe not a good idea :-)
I guess that sigsetjmp() and siglongjmp() hack can be avoided in
Py_EvalFrameEx(), so ceval.c could be unchanged.
New pseudocode:
set checkpoint
if error:
get the backtrace
display the backtrace
fast exit (eg
t the
message "segmentation fault". It's not a problem if displaying the backtrace
produces new fault because it's already better than just the
message "segmentation fault". Even with my SIGSEVG handler, you can still use
gdb because gdb catchs the sig
prefer to see that as a bug and so replace cStringIO by StringIO. So can you
open an issue?
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
he bug? Maybe write an unit test?
I don't know poll(), so I can't help for this issue.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
')
(None, 'c')
>>> retcode=os.system('echo -n $A|hexdump -C')
ff|.|
0001
>>> retcode=os.system('echo -n $B|hexdump -C')
63|c|
0001
Discu
pen issues (and so more and more lost patches) :-( I
will be able to work faster using the svn.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/
e to commit the patch, I will test it before. My
computer has a public IPv6 address :-)
http://bugs.python.org/issue1664
> You don't have to pay attention to me,
No, your opinion is interresting. I hope that my answers will help you to
understand my expectations about an svn account :-)
ind fewer and fewer bugs ;-) Most of the time I rediscover bugs already
reported to the tracker, but not fixed yet. So the fuzzing job is mostly
done ;-)
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python
ons, it's just an email to restart the discussion about
bytes ;-) Martin also asked for a PEP to change the posix module API to
support bytes.
--
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
___
Python-Dev mailing list
Python-Dev@python.
2601 - 2700 of 3215 matches
Mail list logo
