2013/11/16 Maciej Fijalkowski :
> Can I see some writeup how -OO benefit embedded devices?
You get smaller .pyc files. In an embedded device, the whole OS may be
written in a small memory, something like 64 MB or smaller. Removing
doctrings help to fit in 64 MB.
I don't know if dropping "assert"
2013/11/11 Charles-François Natali :
> After several exchanges with Victor, PEP 454 has reached a status
> which I consider ready for pronuncement [1]: so if you have any last
> minute comment, now is the time!
So, what's going on? The deadline is Saturday, in 5 days.
If the PEP is accepted (I ho
rged later. Charles-François told me that he would like to review
the code after he reviewed the PEP.
Victor
>
> On Tue, Nov 19, 2013 at 4:09 PM, Victor Stinner
> wrote:
>>
>> 2013/11/11 Charles-François Natali :
>> > After several exchanges with Victor, PEP 454 has
2013/11/20 Christian Heimes :
> The PEP has landed in revision
> http://hg.python.org/cpython/rev/adb471b9cba1 . I don't expect any test
> failures as I have tested the PEP on a lot of platforms. The new code
> compiles and passes its tests on Linux, Windows, BSD, HUPX, Solaris with
> all supported
2013/11/20 Victor Stinner :
> It looks like dict, set and frozenset representation (repr(...)) now
> depends on the platform (probably 32 bit vs 64 bit), even if
> PYTHONHASHSEED is set. I don't know if it's an issue or not.
In Python 3.3, repr(set("abcd")) with PYTH
2013/11/21 Charles-François Natali :
> I'm happy to officially accept PEP 454 aka tracemalloc.
> The API has substantially improved over the past weeks, and is now
> both easy to use and suitable as a fundation for high-level tools for
> memory-profiling.
>
> Thanks to Victor for his work!
Thanks
2013/11/21 Nick Coghlan :
> Huzzah! Thanks to you both for getting this ready for inclusion :)
I now hope that someone will use it :-)
By the way, collections.namedtuple has a private _source attribute.
This attributes uses something like 676.2 kB in the Python test suite,
it the 5th biggest use
Hum, I don't think that regex module will enter Python 3.4 before this
week-end, there is no PEP.
For the "Introspection information for builtins", I think the PEP 436
has been accepted. The code has been merged, but the PEP status is
still draft.
Victor
2013/11/22 barry.warsaw :
> http://hg.pyt
2013/11/22 Antoine Pitrou :
> I've pushed pathlib to the repository. I'm hopeful there won't be
> new buildbot failures because of it, but still, there may be some
> platform-specific issues I'm unaware of.
A PEP wouldn't be successful if it doesn't break any buildbot. PEP 451
was successful, as y
Hi,
2013/11/21 Charles-François Natali :
> I'm happy to officially accept PEP 454 aka tracemalloc.
> The API has substantially improved over the past weeks, and is now
> both easy to use and suitable as a fundation for high-level tools for
> memory-profiling.
I pushed the implementation of he PEP
2013/11/25 Jim Jewett :
> Why are these functions (get_traces and get_object_traceback) private?
_get_object_traceback() is wrapped to get a nice Python object:
http://hg.python.org/cpython/file/6ec6facb69ca/Lib/tracemalloc.py#l208
_get_traces() is private, it is used internally by take_snapshot(
2013/11/27 guido.van.rossum :
> http://hg.python.org/cpython/rev/80e0040d910c
> changeset: 87617:80e0040d910c
> user:Guido van Rossum
> date:Wed Nov 27 14:12:48 2013 -0800
> summary:
> asyncio: Change write buffer use to avoid O(N**2). Make write()/sendto()
> accept bytearray/
Hi,
I'm trying to write an example of usage of the new
tracemalloc.get_object_traceback() function. Last month I proposed to
use it to give the traceback where a file/socket was allocated on
ResourceWarning:
https://mail.python.org/pipermail/python-dev/2013-October/129923.html
I found a worki
ython/rev/b231e0c3fd26
>> changeset: 87692:b231e0c3fd26
>> branch: 3.3
>> parent: 87690:7d3297f127ae
>> user:Victor Stinner
>> date:Mon Dec 02 12:16:46 2013 +0100
>> summary:
>> Issue #19728: Fix sys.getfilesystemencoding() d
Hi,
Packagers provide an important help and I would like to thank all
packagers! For CPython, we don't have the habit of listing
"third-party" contributors, but only direct contributors. For example,
Django helped a lot for the popularity of the Python language, but we
don't list them in Misc/ACKS
Hi,
The PEP 454 (tracemalloc module) has been implemented in Python 3.4
beta 1. Previously, I also wrote a pyfailmalloc project to test how
Python behaves on memory allocation failures. I found various bugs
using this tool.
I propose to add an optional memory limit feature to the
tracemallocmodul
Hi,
2013/12/9 Serhiy Storchaka :
> But tracemalloc doesn't count memory allocated besides Python allocators
> (e.g. memory for executable, static variables and stack, memory allocated by
> extensions and C lib, unallocated but not returned to OS dynamical memory).
> When you want investigate how y
2013/12/15 Antoine Pitrou :
> Shouldn't we have a special "%T" shortcut instead of trying to
> harmonize all the occurrences of `"%.400s", Py_TYPE(self)->tp_name` ?
Oh, I like this proposition! The following pattern is very common in Python:
"... %.400s ...", Py_TYPE(self)->tp_name
Victor
__
2013/12/18 Antoine Pitrou :
> You only need to call PyEval_InitThreads() once in the main Python
> thread.
This is not well documented. For your information, PyGILState_Ensure()
now calls PyEval_InitThreads() in Python 3.4, see:
http://bugs.python.org/issue19576
Victor
___
Hi,
2014/1/3 Serhiy Storchaka :
>> -if (!PyArg_ParseTuple(arg, "kl:_acquire_restore", &count, &owner))
>> +if (!PyArg_ParseTuple(args, "(kl):_acquire_restore", &count, &owner))
>> return NULL;
>
> Please don't use "(...)" in PyArg_ParseTuple, it is dangerous (see issue6083
> [1])
2014/1/3 Victor Stinner :
> 2014/1/3 Serhiy Storchaka :
>>> -if (!PyArg_ParseTuple(arg, "kl:_acquire_restore", &count, &owner))
>>> +if (!PyArg_ParseTuple(args, "(kl):_acquire_restore", &count, &owner))
>>> retu
2014/1/3 Zachary Ware :
> The above-quoted parts of this changeset caused several compiler
> warnings due to unused variables. On 32-bit Windows:
> (...)
> I believe this should fix it, but I'll leave it up to you to confirm
> that, Victor :)
Oh, I didn't notice these warnings. I fixed them, than
integer numbers?
* Signed number? ``%+i`` and ``%-i``
HTML version of the PEP:
http://www.python.org/dev/peps/pep-0460/
Inline copy:
PEP: 460
Title: Add bytes % args and bytes.format(args) to Python 3.5
Version: $Revision$
Last-Modified: $Date$
Author: Victor Stinner
Status: Draft
Type: Standa
2014/1/7 Paul Moore :
> Will the relevant projects actually support only 2.X and 3.4/5+? If
> they expect to or have to support 3.2 or 3.3, then this change isn't
> actually going to help them much. If they will only support versions
> of Python 3 containing this change, then it may well be worth
>
2014/1/7 Stefan Behnel :
> Victor Stinner, 06.01.2014 14:24:
>> ``struct.pack()`` is incomplete. For example, a number cannot be
>> formatted as decimal and it does not support padding bytes string.
>
> Then what about extending the struct module in a way that makes it cover
Hi,
2014/1/8 Mark Shannon :
> I'm opposed to adding methods to bytes for this, as I think it goes against
> the reason for the separation of str and bytes in the first place.
Well, sometimes practicability beats purity. Many developers
complained that Python 3 is too string. The motivation of the
Hi,
2014/1/8 M.-A. Lemburg :
> I'd simply copy over the Python 2 PyString code and start working
> from there.
It's not possible to reuse directly all Python 2 code because some
helpers have been modified to work on Unicode. The PEP 460 adds also
more work to other implementations of Python.
IMO
2014/1/8 Ethan Furman :
>> Therefore you shouldn't accept integers. It does not make sense to
>> format 4 as b'4'.
>
> Agreed. I would have that it would result in b'\x04'.
The PEP proposes b'%c' % 4 => b'\x04.
Antoine gave me a good argument against supporting b'%s' % int: how
would int subclas
Hi,
> Python 3 forces you to think about abstract concepts like encodings when all
> you want is to open that .txt file on the drive and extract some phone
> numbers and merge in some email addresses.
You can open a text file using ascii + surrogateescape, or just open
the file in binary.
Vic
2014/1/9 Kristján Valur Jónsson :
> This definition is funny, because according to Wikipedia, it is a "superset"
> of 8869-1 ( latin1)
Bytes 0x80..0x9f are unassigned in ISO/CEI 8859-1... but are assigned
in (IANA's) ISO-8859-1.
Python implements the latter, ISO-8859-1.
Wikipedia says "This enc
2014/1/10 Juraj Sukop :
> In the case of PDF, the embedding of an image into PDF looks like:
>
> 10 0 obj
> << /Type /XObject
> /Width 100
> /Height 100
> /Alternates 15 0 R
> /Length 2167
> >>
> stream
> ...binary image data...
> ends
Hi,
I'm in favor of adding support of formatting integer and floatting
point numbers in the PEP 460: %d, %u, %o, %x, %f with padding and
precision (%10d, %010d, %1.5f) and sign (%-i, %+i) but without
alternate format ("{:#x}"). %s would also accept int and float for
convenience.
int and float sub
2014/1/11 Ethan Furman :
>>> b'x=%s' % 10 is well defined, it's pure bytes.
>>
>> It is well-defined? Then please explain me what the general case of
>>b'%s' % x
>> is supposed to call:
>
> This is the key question, isn't it?
Python 2 and Python 3 are very different here.
In Python 2, the "s"
Hi,
2014/1/11 Antoine Pitrou :
>> b'x=%s' % 10 is well defined, it's pure bytes.
>
> It is well-defined? Then please explain me what the general case of
> b'%s' % x
> is supposed to call:
>
> - does it call x.__bytes__? int.__bytes__ doesn't exist
> - does it call bytes(x)? bytes(10) gives
> b
Hi,
I'm working for eNovance on the asyncio module, the goal is to use it
in the huge OpenStack project (2.5 millions line of code) which
currently uses eventlet. I'm trying to fix remaining issues in the
asyncio module before Python 3.4 final.
The asyncio project is very active but discussions a
2014-01-27 Antoine Pitrou :
> On Mon, 27 Jan 2014 10:45:37 +0100
> Victor Stinner wrote:
>>
>> - Tulip #111: StreamReader.readexactly() now raises an
>> IncompleteReadError if the
>> end of stream is reached before we received enough bytes, instead of
>> re
2014-01-27 Gustavo Carneiro :
>> > Why not simply EOFError?
>>
>> IncompleteReadError has two additionnal attributes:
>>
>> - partial: "incomplete" received bytes
>> - expected: total number of expected bytes (n parameter of readexactly)
>>
>> I prefer to use a different exception to ensure that th
2014-01-27 Serhiy Storchaka :
> 27.01.14 12:55, Victor Stinner написав(ла):
>
>> IncompleteReadError has two additionnal attributes:
>>
>> - partial: "incomplete" received bytes
>> - expected: total number of expected bytes (n parameter o
Hi,
I'm surprised: marshal.dumps() doesn't raise an error if you pass an
invalid version. In fact, Python 3.3 only supports versions 0, 1 and
2. If you pass 3, it will use the version 2. (Same apply for version
99.)
Python 3.4 has two new versions: 3 and 4. The version 3 "shares common
object ref
2014-01-28 "Martin v. Löwis" :
> Debugging reveals that it is actually the many integer objects which
> trigger the sharing code. So a much simplified example of Victor's
> benchmarking code can use
>
> data = [0]*1000
>
> The difference between version 2 and version 3 here is that v2 marshals
Link to the thread on python-tulip:
https://groups.google.com/forum/#!topic/python-tulip/2snxuJY_Lx0
Victor
2014-01-29 Guido van Rossum :
> If you're interested, please see us on the python-tulip mailing list at
> Google Groups.
>
> --
> --Guido van Rossum (python.org/~guido)
>
>
Latest asyncio update: it has a new asyncio.subprocess submodule which
provides a high-level API to control subprocesses, similar to
subprocess.Popen but using asyncio event loop (and so is
asynchronous).
It solves the following old and tricky issue:
http://bugs.python.org/issue12187
"subprocess.w
Hi,
I modified the Python documentaton (asyncio module) 6 days ago, and my
changes are not online yet:
http://docs.python.org/dev/library/asyncio-eventloop.html#running-subprocesses
Is it a problem with the server generating the documentation?
By the way, would it be possible to regenerate the d
2014-02-03 Phil Thompson :
> For example, a string created with a maxchar of 255 (ie. a Latin-1 string)
> must contain at least one character in the range 128-255 otherwise you get
> an assertion failure.
Yes, it's the specification of the PEP 393.
> As it stands, when converting Latin-1 strings
2014-02-03 Phil Thompson :
> Are you saying that code will fail if a particular Latin-1 string just
> happens not to contains any character greater than 127?
PyUnicode_FromKindAndData(PyUnicode_1BYTE_KIND, latin1_str, length)
accepts latin1 and ASCII strings. It computes the maximum code point
and
2014-02-03 Benjamin Peterson :
>> Is it a problem with the server generating the documentation?
>
> Hopefully fixed now.
The documentation is still outdated. For example, I don't see the new
subprocess page in
http://docs.python.org/dev/library/asyncio.html
> It was twice a day before, I've now s
2014-02-03 Benjamin Peterson :
>> The documentation is still outdated. For example, I don't see the new
>> subprocess page in
>> http://docs.python.org/dev/library/asyncio.html
>
> Finally fixed.
Thanks.
Victor
___
Python-Dev mailing list
Python-Dev@pyt
2014-02-04 Larry Hastings :
> Why couldn't these tools use inspect.Signature?
inspect.Signature was added in Python 3.3. Python 2 is still widely
used, and some Linux distro only provide Python 3.2.
By the way, help(dict.fromkeys) looks to use __doc__, not the
signature, because the prototype is
2014-02-09 1:00 GMT+01:00 MRAB :
> Some spelling mistakes:
Please, try to write a patch or it will be hard to merge fixes.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https:/
Hi,
It would be nice to give also the link to the whole changelog in your
emails and on the website:
http://docs.python.org/3.4/whatsnew/changelog.html
Congrats for your RC1 release :-) It's always hard to make developers
stop addings "new minor" changes before the final version :-)
Victor
2014
Hi,
2014-02-12 17:30 GMT+01:00 Bob Hanson :
> [32-bit Windows XP-SP2]
>
> Python 3.4.0rc1's MSI installer won't install on my machine.
I justed tested Python 3.4.0rc1 MSI installer on Windows XP SP3
(32-bit): Python was installed successfully.
Victor
_
2014-02-12 18:10 GMT+01:00 Bob Hanson :
> Does this mean that Python no longer supports XP-SP2?
I don't know what it means. I don't have access to Windows XP SP2 to test.
By the way, why not upgrading to SP3? :-)
I read that you installed the beta2 before. You should maybe make sure
that Python
Hi,
The PEP 436 is still a draft and not mentionned in Python 3.4
changelog. The PEP proposes to add a DSL, not to modify all modules
implemented in C. I think that it should be marked as Final and
mentionned in the changelog.
http://www.python.org/dev/peps/pep-0436/
2014-02-16 19:31 GMT+01:00 La
2014-02-17 0:25 GMT+01:00 Larry Hastings :
> You might think that anything you check in to the "default" branch in Python
> trunk will go into 3.4.0 rc2, and after that ships, checkins would go into
> 3.4.0 final. Ho ho ho! That's not true! Instead, anything checked in to
> "default" between my
Hi,
2014-02-18 6:19 GMT+01:00 Zachary Ware :
> On Mon, Feb 17, 2014 at 6:36 PM, victor.stinner
> wrote:
>> http://hg.python.org/cpython/rev/79ccf36b0fd0
>> changeset: 89239:79ccf36b0fd0
>> user:Victor Stinner
>> date:Tue Feb 18 01:35:40 2014 +0100
2014-02-19 0:46 GMT+01:00 Larry Hastings :
> Is there *any* reason to make this branch public before 3.4.0 final?
I'm a little bit worried by the fact that buildbots will not test it.
Cherry-picking many patches is complex. It's safe if you have a very
short list of changes.
Would it be insane to
2014-02-17 0:25 GMT+01:00 Larry Hastings :
> You might think that anything you check in to the "default" branch in Python
> trunk will go into 3.4.0 rc2, and after that ships, checkins would go into
> 3.4.0 final. Ho ho ho! That's not true! Instead, anything checked in to
> "default" between my
Hi,
Thanks Larry for being our release manager. How can we help you?
Sorry for giving you too much work with asyncio changes :-)
Python 3.4 is the largest release in term of new features since Python
3. To give you an overview of new features, 8 new modules were added
between Python 2.7 and 3.3.
Hi,
2014-02-21 4:15 GMT+01:00 Chris Angelico :
> PEP: 463
> Title: Exception-catching expressions
Nice PEP. Good luck, it's really hard to modify the language. Be
prepared to get many alternatives, criticisms, and suggestions. Good
luck to handle them :-) Here is mine.
I like the simple case "e
Hi,
First, this is a warning in reST syntax:
System Message: WARNING/2 (pep-0461.txt, line 53)
> This area of programming is characterized by a mixture of binary data and
> ASCII compatible segments of text (aka ASCII-encoded text). Bringing back a
> restricted %-interpolation for ``bytes`` and
>
>
>>>
>> (You forgot "/U" representation (it's an antislah, but I don't
>> see the key on my Mac keyboard?).)
>>
>
> Hard to forget what you don't know. ;) Will ascii() ever emit an
> antislash representation?
Try ascii(chr(0x1f)).
What is the use case of this *new* formatter? H
2014-02-24 3:45 GMT+01:00 Nick Coghlan :
> Would leaving %a out destroy the utility of the PEP?
Usually, debug code is not even commited. So writing b'var=%s' %
ascii(var).encode() is not hard.
Or maybe: b'var=%s' % repr(var).encode('ascii', 'backslashreplace')
which is the same but longer :-)
V
2014-02-24 22:08 GMT+01:00 Jim J. Jewett :
>>> Will ascii() ever emit an antislash representation?
Sorry, it's chr(0x10):
>>> print(ascii(chr(0x10)))
'\U0010'
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/
Hi,
2014-02-25 8:53 GMT+01:00 Nick Coghlan :
> I've checked these, and noted the relevant hg.python.org links on the
> tracker issue at http://bugs.python.org/issue20246
Would it be possible to have a table with all known Python security
vulnerabilities and the Python versions which are fixed? Bo
Hi,
2014-02-25 8:39 GMT+01:00 Christian Heimes :
> this looks pretty serious -- and it caught me off guard, too. :(
> https://www.trustedsec.com/february-2014/python-remote-code-execution-socket-recvfrom_into/
I don't think that the issue is critical.
Extract of the article "Diving into SocketSe
Hi,
2014-02-27 11:22 GMT+01:00 Kristján Valur Jónsson :
> Now, Larry Hastings pointed out that we support C89 which doesn’t support
> Inlines. Rather than suggesting here that we update that compatibility
> requirement,
In practice, recent versions of GCC and Clang are used. On Windows,
it's Vis
Hi,
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version? I'm asking for a typo in tracemalloc documentation:
http://bugs.python.org/issue20814
http://hg.python.org/cpython/rev/a9058b772807
Victor
2014-03-03 13:13 GMT+01:00 Larry Hastings :
> I would like to know if the cherry-picking rule still applies for
> Python 3.4 final? Can I open an issue if I want to see a changeset in
> the final version?
>
> Sadly, yes.
Ok, I created:
http://bugs.python.org/issue20843
Why do you say "sadly"? It'
>
>
>> Will this impact on the decision http://bugs.python.org/issue20846 ?
>
This issue has been closed as wontfix. It has no patch and must be reported
to pip, not python.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.or
Hi,
2014-03-03 22:38 GMT+01:00 Nick Coghlan :
> Related question - have you decided yet whether or not to do an rc3?
I take a look at current release blocker issues for Python 3.4. I saw
bugfixes (ex: upgrade SQLite from 3.8.3 to 3.8.3.1) but also fixes for
regressions between Python 3.4rc2 and P
Hi,
Python 3 now stores the traceback object in Exception.__traceback__
and exceptions can be chained through Exception.__context__. It's
convinient but it introduced tricky reference cycles if the exception
object is used out of the except block.
Refrences: Exception.__traceback__ -> traceback -
2014-03-06 14:42 GMT+01:00 Antoine Pitrou :
> Le 05/03/2014 23:53, Nick Coghlan a écrit :
>>
>>
>> __traceback__ wouldn't change [...]
>
>
> Uh, really? If you want to suppress all reference cycles, you *have* to
> remove __traceback__.
>
> The problem is to make computation of the traceback summar
Hi,
2014-03-06 16:19 GMT+01:00 Victor Stinner :
> By the way, here is my test script to try to create a lightweight
> traceback object without references to locals:
> https://bitbucket.org/haypo/misc/src/tip/python/suppress_locals.py
>
> It works if there is no chained exception
2014-03-07 6:25 GMT+01:00 Nick Coghlan :
>> Uh, really? If you want to suppress all reference cycles, you *have* to
>> remove __traceback__.
>>
>> The problem is to make computation of the traceback summary lightweight
>> enough that it doesn't degrade performance in the common case where you
>> do
> Could you clarify what the problem actually is?
Please see:
http://bugs.python.org/file33238/never_deleted.py
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.pyth
2014-03-08 1:14 GMT+01:00 Jim Jewett :
>>> Could you clarify what the problem actually is?
>
>> Please see:
>> http://bugs.python.org/file33238/never_deleted.py
>
> I would not expect it to be cleared at least until go runs ... and reading
> the ticket, it sounds like it is cleared then.
Attached
2014-03-08 12:45 GMT+01:00 Antoine Pitrou :
>> Attached script: never_deleted2.py, it's almost the same but it
>> explains better the problem. The script creates MyObject and Future
>> objects which are never deleted. Calling gc.collect() does *not* break
>> the reference cycle (between the future,
2014-03-08 14:33 GMT+01:00 Antoine Pitrou :
> Ok, it's actually quite trivial. The whole chain is kept alive by the
> "fut" global variable. If you arrange for it to be disposed of:
>
> fut = asyncio.Future()
> asyncio.Task(func(fut))
> del fut
> [etc.]
>
> then the problem disappears: as s
Hi,
I tested Python 3.4rc3 installer on Windows:
- all menu entries work (doc, doc server, help, IDLE, command line, etc.)
- pip is installed, yeah!
- my tracemalloc module works on Windows too ;-)
- The uninstaller fully removes C:\Python34
The major Windows installer issues are fixed in the RC
2014-03-08 16:30 GMT+01:00 Maciej Fijalkowski :
> How about fixing cyclic gc to deal with __del__ instead? That sounds
> like an awful change to the semantics.
Hum? That's the purpose of the PEP 442 which is implemented in Python 3.4.
As I wrote, it's not enough to fix all issues.
Usually, I see
2014-03-10 13:11 GMT+01:00 Maciej Fijalkowski :
> It was agreed long time ago that the immediate finalization is an
> implementation specific detail and it's not guaranteed. You should not
> rely on __del__s being called timely one way or another. Why would you
> require this for the program to wor
Hi,
Last 5 years, I spend significant time to port a lot of Python 2 code
on Python 3. First, using the 2to3 tool + extra manual patches. Sorry,
it was not usable in practice. The conversion was very slow, it didn't
fix doctests nor all other minor "details". "Fixing Python 2 code" was
no always p
2014-03-10 16:25 GMT+01:00 Stefan Richthofer :
> I don't see the point in this discussion.
> As far as I know, the major version is INTENDED to
> indicate backward-incompatible changes.
This is not a strict rule. I would like to follow Linux 3 which didn't
break the API between Linux 2 and Linux 3
>> I suggest to wait less than 8 years
>> for Python 4.
>
> Why? What's special about 8 years?
It's the time between Python 2.0 and 3.0.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubsc
Hi,
Thanks David! I added a summary of security improvements:
http://docs.python.org/dev/whatsnew/3.4.html#summary-release-highlights
Can someone please review it? Don't hesitate to modify the text
directly. Check also if the summary is complete.
Victor
2014-03-11 3:05 GMT+01:00 R. David Murray
2014-03-11 13:28 GMT+01:00 Nick Coghlan :
> I was thinking of adding a new "Migrating from Python 2" section at
> the end of the porting guide, noting the changed recommendations in
> the migration guide (i.e. people that read it a while ago should read
> it again), as well as the restoration of th
Hi,
2014-03-12 18:09 GMT+01:00 Guido van Rossum :
> I want to reject this PEP. (...)
> this was a well-written and well-researched PEP, and I think you've done a
> great job moderating the discussion, collecting objections, reviewing
> alternatives, and everything else that is required to turn a h
2014-03-13 11:49 GMT+01:00 Christian Heimes :
> * All stdlib modules now support server cert verification including
> hostname matching and CRL.
>
> * http://bugs.python.org/issue16499 isolated mode is a security
> improvement, too.
Ok, I added these two items.
Antoine wrote:
> CRL? really? I don
Hi,
To prepare my conference on tracemalloc for Pycon Montréal next month,
I wrote a GUI to analyze tracemalloc snapshots: "tracemallocqt".
https://bitbucket.org/haypo/tracemallocqt
It looks like that:
http://www.haypocalc.com/tmp/tracemallocqt_python34.png
I'm looking for testers and feedba
>
>
> I'm especially curious about tracemalloc, since I know Victor found
> something he wanted to change (add?) to the API just recently.
>
>
I hope that the PEP process found all major design issues. I will try to
avoid as much as posssible to break the backward compatibility. As you
wrote, I may
Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only
accept security fixes, right?
Victor
Le 17 mars 2014 07:48, "Larry Hastings" a écrit :
>
>
> The "3.4" branch is now checked in. It contains all the 3.4 releases
> since 3.4.0rc1. Its current state is effectively 3.4.1.
Hi,
I modified the Misc/NEWS file:
* I moved 3.3 sections to Misc/HISTORY: items were already present,
but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
* I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be
present in the 3.4 branch (changeset cb161cd94e6e)
Is tha
Hi,
I modified Python 3.5 to use the "surrogateescape" error handler (PEP
383) for stdin and stdout when the LC_CTYPE locale is POSIX ("C"
locale):
http://bugs.python.org/issue19977
New behaviour:
---
$ mkdir z
$ touch z/abcé
$ LC_CTYPE=C ./python -c 'import os; print(os.listdir("z")[0])'
abcé
--
Hi,
2014-03-18 7:19 GMT+01:00 Georg Brandl :
> Am 17.03.2014 22:36, schrieb Victor Stinner:
>> I modified the Misc/NEWS file: (...) Is that correct?
>
> The changes not merged in 3.4.0 will all be in 3.5.0; please reinstate the
> NEWS entries under the 3.5 heading.
Oh ok, I
2014-03-18 7:22 GMT+01:00 Georg Brandl :
> Am 18.03.2014 01:27, schrieb victor.stinner:
>> http://hg.python.org/cpython/rev/daa6bf71170f
>> changeset: 89835:daa6bf71170f
>> user: Victor Stinner
>> date:Tue Mar 18 00:53:32 2014 +0100
>> summary:
2014-03-18 9:08 GMT+01:00 Nick Coghlan :
> On 18 Mar 2014 11:56, "Victor Stinner" wrote:
>>
>> Hi,
>>
>> I modified Python 3.5 to use the "surrogateescape" error handler (PEP
>> 383) for stdin and stdout when the LC_CTYPE locale is POSIX
2014-03-18 10:48 GMT+01:00 Nick Coghlan :
> Well, the concern has always been the risk of silently generating bad
> data if there is a mismatch between the OS encoding and the stream
> encodings.
Data can be loaded from OS functions, from files and from stdin. These
3 sources may use various diffe
2014-03-18 11:02 GMT+01:00 Atsuo Ishimoto :
> FYI: Guido was opposed to change error handler of stdin and stdout years ago.
>
> http://bugs.python.org/issue2630#msg65493
This issue proposes to use "backslashreplace" error handler for
stdout. This error handler is very different to "surrogateescape
Hi,
2014-03-22 22:11 GMT+01:00 Nick Coghlan :
> In particular, the exception will apply to:
>
> * the ``ssl`` module
> * the ``hashlib`` module
> * the ``hmac`` module
> * the ``sha`` module (Python 2 only)
> * the components of other networking modules that make use of these modules
> * the compo
Hi,
2014-03-23 11:17 GMT+01:00 :
> Quoting Victor Stinner :
>> The drawback is that applications would be benefit immediatly from
>> this work, they should be modified to use the new module. But usually,
>> developers who care of security are able to do these modification
701 - 800 of 3215 matches
Mail list logo
