[Python-Dev] Riddle: Funny decorator chaining behaviour
Chatting in a Spanish python podcast about how convenient would be for
abstract classes to raise exceptions intermediately instead of at
instantiation time (how could you create an abstract class in that
case?), somebody produced this code:
import abc
class a(abc.ABC):
@classmethod
@property
@abc.abstractmethod
def x(cls):
print("Hello world")
class b(a):
def x(*args):
pass
(NOTHING happens, the abstract method/property is overriden)
class c(a):
pass
"HELLO WORLD" is printed, creating the class (not instanciating an
object of that type but creating the class itself), because the abstract
method/property is not overriden.
Note that the method is called at class creation time.
if you replace the body of "x" method with a "raise NotImplementedError"
you can produce that exception at import time, if some class remains
abstract.
This is an interesting interaction between decorators trying to be
clever supporting both regular and abstract methods/properties.
Trying to figure out how it worked took some time and python source code
diving. I think this is interesting enough to share.
I don't think this is a bug to solve, just some brain teasing. I let
other to decide what to do with this... collateral effect.
Let me know what do you think after trying to understand how it works.
--
Jesús Cea Avión _/_/ _/_/_/_/_/_/
j...@jcea.es - https://www.jcea.es/_/_/_/_/ _/_/_/_/ _/_/
Twitter: @jcea_/_/_/_/ _/_/_/_/_/
jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/
"My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
OpenPGP_signature
Description: OpenPGP digital signature
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/VJ5PWJNU325SVVIBTRPCEUYOERBKGNWA/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Request for review: issue 42815: new thread doesn't copy context of the parent thread
https://bugs.python.org/issue42815 https://github.com/python/cpython/pull/24074 I would love to have this in Python 3.10, but the interaction with "decimal" context has a risk I don't know how to evaluate, neither the impact of a new "context" parameter when launching a new thread. It could collide with a "frequently used" parameter name. I know that we are quite late in 3.10 window since rc1 is planned in a couple of days, but I think this enhancement is sensible. In fact, I discovered it after being annoyed myself with this issue (threads should have their own contexts) and studying the code to write a patch myself. In particular, "concurrent.futures" threads should have independent contexts, like asyncio futures have. That would allow, for instance, to have a "requests.Session" object per thread since that object is not thread-safe (my use case today) and reuse it in different futures that happens to run in the same thread. Since "contextvars" is "threading.local" correctly done, let's do it for real. If legacy code expects a thread to be able to modify parent context, just pass that context to the thread explicitly. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - https://www.jcea.es/_/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz OpenPGP_signature Description: OpenPGP digital signature ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/M67OMDBNFN5FLGLO7HZFJ6CUPK5Z4PJE/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] "threading.Lock().locked()" is not documented
https://docs.python.org/3.6/library/threading.html doesn't document "threading.Lock().locked()", and it is something quite useful. In fact, it is used in "threading.py" itself. For instance, lines 109, 985, 1289. Is there any reason to not document it?. (I didn't investigate other objects in the module). -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New security-annou...@python.org mailing list
On 21/09/17 17:30, Barry Warsaw wrote: > https://mail.python.org/mailman/listinfo/security-announce "No such list security-announce". > https://mail.python.org/mailman/listinfo/security-sig "No such list security-sig". -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] OpenIndiana and Solaris support
On 08/02/17 17:06, Jesus Cea wrote: > On 08/02/17 16:18, Jesus Cea wrote: >> I am trying to convince him to launch buildbot process tree with an >> "ulimit" to protect the machine. Lets see. >> >> Sorry. Thanks for your patience. > > I am launching now the buildbot with a limit of 1GB *PER PROCESS*. At > least, when the memory skyrockets it will die without impacting the rest > of the machine. Unless it does a fork-bomb... > > Backlog is huge. That will be useful to stress the buildbot and, > hopefuly, make it fails faster. Checking the mailing list archives, I am seen Openindiana buildbot memory issues since 2011, at least. <https://mail.python.org/pipermail//python-dev/2011-September/113532.html>. It was never triaged. I am getting mercurial errors because some incompatibility with current release <http://buildbot.python.org/all/builders/x86%20OpenIndiana%203.5/builds/79/steps/touch/logs/stdio>. Since we are moving to github in a couple of days, I will wait until that time to keep pursuing this. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] OpenIndiana and Solaris support
On 08/02/17 11:24, Victor Stinner wrote: > So I suggest to drop official Solaris support, but I don't propose to > remove the C code specific to Solaris. In practice, I suggest to > remove Solaris and OpenIndiana buildbots since they are broken for > months and are more annoying than useful. The main issue is that something wrong is going on with buildbot. From time to time, it eats gigabytes of RAM (last time, 64GB) and kills the machine. maybe once per week. This is not very welcomed by my host and his reaction is to shutdown the solaris "zone" because we don't "behave" and this is impacting production system. I am trying to convince him to launch buildbot process tree with an "ulimit" to protect the machine. Lets see. Sorry. Thanks for your patience. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] OpenIndiana and Solaris support
On 08/02/17 11:24, Victor Stinner wrote: > So I suggest to drop official Solaris support, but I don't propose to > remove the C code specific to Solaris. In practice, I suggest to > remove Solaris and OpenIndiana buildbots since they are broken for > months and are more annoying than useful. Give me a week to move this forward. Last hope. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] MemoryError and other bugs on AMD64 OpenIndiana 3.x
Sorry, I am currently traveling. Away from real computer until April 7th. On 28/03/15 10:48, Victor Stinner wrote: Hi, The buildbot AMD64 OpenIndiana 3.x is always red since at least 6 months. Almost always, tests fail because the buildbot has not enough memory. Well, it's fun to see how Python handles MemoryError (it's pretty good, there is no hard crash! my work on failmalloc was maybe useful ;-)), but it doesn't help to detect regressions. Would it be possible to enhance this buildbot? Those buildbots are hosted in OpenIndiana infraestructure. I take care of the Solaris Zone (similar to docker but better :-)) but I can't interact with the real machine. Sometimes changes in the real machine had impacted us and nobody realized until some time later, when nobody remembers what was changed or who did it. I have contacted the machine manager and he has said to me that 16GB were taken in the /tmp directory by buildbot user. He has deleted them and everything should be fine now. Lets see. Anyway if buildbot is leaving garbage behind we should take care of it. Doing a daily cron for manual cleaning up seems a bit hacky :). I would be interested, too, in getting an email when one of my buildbots is red for more than, lets say, 4 days in a row. An email per day would be fine. BTW, buildbot pages are painfully slow. The manager had to insist and be patient to see http://buildbot.python.org/all/waterfall?show=x86%20OpenIndiana%203.x, etc. How can that be improved?. I copy this email to the owner of buildbot. But I also sent it to python-dev because MemoryError is not the only error, please take care of our buildbots! Thanks for keeping me in the loop. I hope everything is going green for a while now :) -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Strange help(int.__lt__). Probably documentation bug
http://bugs.python.org/issue20530#msg231584 -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Strange help(int.__lt__). Probably documentation bug
On 27/11/14 13:42, Victor Stinner wrote: 2014-11-27 13:41 GMT+01:00 Victor Stinner victor.stin...@gmail.com: I am amused about the /) suffix in the signature. It happens to all magic methods. If I remember correctly, it means that the function does not accept keywords: I don't understand. Is that internal annotation for the clinic machinery?. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mUTF-7 support?
On 10/10/14 04:41, R. David Murray wrote: Specifically, it is about what we might better term mailbox *folders*...that is, not what you would normally think of as the 'mailbox name', which is usually understood to be the thing before the @ in the email address (and can't contain non-ASCII yet...we need RFC 6855 support for that, and I'm not sure *anybody* has that yet). In this context it is the names you give to folders on the IMAP server...starting (usually) with INBOX and adding from there. These names are used in IMAP commands (ex: the 'select' or 'create' commands), and IMAP uses mUTF-7 for those. In IMAP4, mail folders are called mailboxes. Yes, non universal notation sucks. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mUTF-7 support?
I think the consensus so far is that this is a good idea. I just opened http://bugs.python.org/issue22598. Thanks for your feedback. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Sad status of Python 3.x buildbots
On 03/09/14 02:37, Antoine Pitrou wrote: I'm not sure that's an answer to the problem. What we need is not more machines, but dedicated buildbot maintainers. I would love to get an email if my buildbots are consistently RED for a few hours. In the past Antoine, Victor and others pinged me about issues in my buildbots (OpenIndiana). I feel shame and I think it is not very productive either. If red state in the buildbots were really trustable, the committer of that changelog should be bugged too. Since we have quite a few false positives, that would be probably annoying and no productive. Decreasing false positives should be a priority. In my case another issue is that my buildbots are hosted as a Solaris ZONE inside a OpenIndiana development machine I don't manage. Their own usage varies and can impact buildbots resource limits like memory, swap space, etc. Thanks for your patience and for notifying me issues when you suffer them. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Sad status of Python 3.x buildbots
On 10/10/14 17:56, Chris Angelico wrote: Could I write a little monitor at my end that asks every hour if my buildbots can be seen? AFAIK maintainers already get an email if the buildbot vanishes long enough. I am more interested in getting an email when my buildbot is consistently red because somebody committed something it doesn't like two months ago... -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Sad status of Python 3.x buildbots
On 10/10/14 17:45, Jesus Cea wrote: Thanks for your patience and for notifying me issues when you suffer them. Another issue is changes that actually breaks buildbots and I don't actually know where to start debugging. For instance, currently: http://buildbot.python.org/all/builders/x86%20OpenIndiana%202.7/builds/2541/steps/test/logs/stdio == FAIL: test_init (test.test_readline.TestReadline) -- Traceback (most recent call last): File /export/home/buildbot/32bits/2.7.cea-indiana-x86/build/Lib/test/test_readline.py, line 52, in test_init self.assertEqual(stdout, b'') AssertionError: '\x1b[?1034h' != '' No idea what to do now, beside forcing bisection builds and blaming somebody else :). -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] mUTF-7 support?
I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python, in the codecs module. As an european with a language with 27 different letters (instead of english 26), tildes, opening question marks, etc., I find it very inconvenient. This encoding is used basically only in IMAP4, I know. But IMAP4 is an important protocol and all projects related to it needs mUTF-7 support if they care about non-english alphabets. Everybody has already an implementation, waste of effort. We already support quite amusing encodings in https://docs.python.org/3.5/library/codecs.html#standard-encodings. What do you think?. Could be considered for Python 3.5?. I volunteer for the job, of course. PS: Do you think a Python implementation would be good enough?. I don't think this need to be C-fast. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mUTF-7 support?
On 10/10/14 01:08, Victor Stinner wrote: When you say IMAP4, do you mean any IMAP4 server? Do you have a list of server vendors known to use the encoding mUTF-7? All of them. IMAP4 protocol **REQUIRES** mUTF-7. UTF-8 is optional in IMAP4, and even UTF-8 capable servers have to support clients without that ability. Check 5.1. Mailbox Naming in IMAP4 RFC: http://tools.ietf.org/html/rfc3501. Anyway, open an issue ;-) I would like to gauge interest/resistance to the idea from my fellows first. How is mUTF-7 different than UTF-7? (Why yet another encoding while standard UTF encodings exist???) As explained in section 5.1.3. Mailbox International Naming Convention: The purpose of these modifications is to correct the following problems with UTF-7: 1) UTF-7 uses the + character for shifting; this conflicts with the common use of + in mailbox names, in particular USENET newsgroup names. 2) UTF-7's encoding is BASE64 which uses the / character; this conflicts with the use of / as a popular hierarchy delimiter. 3) UTF-7 prohibits the unencoded usage of \; this conflicts with the use of \ as a popular hierarchy delimiter. 4) UTF-7 prohibits the unencoded usage of ~; this conflicts with the use of ~ in some servers as a home directory indicator. 5) UTF-7 permits multiple alternate forms to represent the same string; in particular, printable US-ASCII characters can be represented in encoded form. Requests of new encodings: I am volunteering and can even do the mercurial PUSH myself :-p. That is an advantage over some of those new encoding requests :-pp. But then yes, I realize that this is a specialized tool (even if IMAP4 is probably the most popular mail access protocol in the world), we can accommodate every use-case and there are tons of mUTF-7 libraries out there already. So, I am asking :). -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mUTF-7 support?
On 10/10/14 02:00, Victor Stinner wrote: 2014-10-10 1:33 GMT+02:00 Jesus Cea j...@jcea.es: The purpose of these modifications is to correct the following problems with UTF-7: If you need performances, I would be interested to see if it would be possible to reuse the C codec for UTF-7 to share as much code as possible. I don't need performance, and implementations I am studying are already using UTF-7 as an intermediate step. Example: http://imapclient.freshfoo.com/browser/imapclient/imap_utf7.py What is the current behaviour of imaplib in Python 3.4 with non-ASCII characters in mailbox names? It breaks. Crash burn. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mUTF-7 support?
On 10/10/14 02:43, Victor Stinner wrote: 2014-10-10 2:34 GMT+02:00 Jesus Cea j...@jcea.es: What is the current behaviour of imaplib in Python 3.4 with non-ASCII characters in mailbox names? It breaks. Crash burn. Oh ok. So in short, imaplib doesn't work on Python 3: it's a bug and it must be fixed. I agree that a new codec is good idea and I will support it! Actually, it doesn't work in Python 2 either. It never supported international mailbox names. Should I dare to suggest to port this to 2.7, since 2.7 is special and will be supported for a long time?. Or maybe this is something like Yes, Python 2 is broken, the real deal is Python 3? :). -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.3): Closes #20872: dbm/gdbm/ndbm close methods are not documented
On 25/06/14 20:35, Ned Deily wrote: The 3.3 branch is open only to security fixes. Please don't backport other patches to there. https://docs.python.org/devguide/devcycle.html#summary Ned, I am aware. It is a doc-only fix, like fixing a typo or correcting an incorrect statement. It that is against policy, let me know. That said, looks like 3.3 documentation is not sphinxed anymore to the webpage, so that actually makes the point high and clear. I have a browser tab open to check a 3.3 doc fix and it is not showing. Thanks for the heads up. Sorry for the inconvenience. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] sys.intern should work on bytes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sys.intern(b'12121212') Traceback (most recent call last): File stdin, line 1, in module TypeError: must be str, not bytes I wonder why. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjwvPJlgi5GaxT1NAQIINQP/ZmEyPBSapa52yZRhQf8QSVSBm5tXpWrC k9MbcvsK/5K6ArRogkulk1GSu1EJPPvuHMAXX8EenNFBXPvDRm0mOxrHkcYw5IKx Ml2ORENm+EEM/ziUJMRtY4aqD5Jp6pXSSl9UmP5OQMDJfuabSrVqs7X2409OOhUj BXeg9HvURxo= =78M+ -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] sys.intern should work on bytes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/09/13 14:04, Victor Stinner wrote: What would you be the use case of interned bytes objets? Performance and memory. Pickle sizes (my particular issue now). - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjxKPZlgi5GaxT1NAQJ6FwQAim2H+OGpRD75KplahNhnKIfm9AUqVnHg CaLakWhADdHBYlit+DxRQsxtv5C7gyhhqMryydyvx97z33VaI2p1RGOOcK/lWdNw ETcetqJo8UswS2PSthJ0e5snOUsIeVJRomhJ48n8sJfIadCxAk6ozdMR75pHP5Y3 lJoUuUgdcJU= =vbuK -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] sys.intern should work on bytes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/09/13 14:15, Antoine Pitrou wrote: From http://docs.python.org/3.3/library/sys.html#sys.intern sys.intern(string) Enter string in the table of “interned” strings and return the interned string [...] In Python 3 context, string means str. I read that, Antoine. In fact I read the manual, I thought it was a mistake carried over from 2.x documentation, I tried it just in case before reporting the documentation mistake, and I was surprised it was actually true :-). I know that intern is used for performance reasons internally to the interpreter. But I am thinking about memory usage optimizations. For instance, I have a pickle that is 14MB in size, when interning the strings on it (there are a lot of redundancy), the new size is only 3MB and it loads faster. I can do it because most data in the pickle are strings, I could NOT do it if I used bytes. I could do a manual intern for hashable objects by hand using an object:object dictionary (that would work for integers too), but I wonder if extending builtin sys.intern would be something to consider. Anyway, this pattern is easy enough: Instead of object = sys.intern(object) I could do interned = dict() ... object = interned.setdefault(object, object) - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjxOkZlgi5GaxT1NAQIOVgQAhN36yRAAQP1YWbDsXGSamgZnhEULTloB penRZYTYz/Ir/VM9l27GoXS7ThGrucAkkYZoJqXnUr2vyP0hq6rsfp+N5lzl61Nf mDJBCtAczzKNdYqQSgMQ+Ugk43KnbEFFX7SB9Y5IkYroWCeWq7+5y6KX3ZKBspXG lmXotLgpvW0= =/RNw -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] sys.intern should work on bytes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/09/13 15:31, Antoine Pitrou wrote: sys.intern is an internal interpreter optimization and should be orthogonal to pickling. If pickle can't detect already-seen bytes object, then you may file an improvement request on the bug tracker. Understood. Thanks for the clarification. Pickle manage correctly same object references, but not different objects but equivalent. That is the issue. But for most uses this is not a problem, and implementing this redundance removal looks like a performance cost that few users would benefice from, but everybody pays. Pickle is already slow enough now :). - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjxPbZlgi5GaxT1NAQIyYQQAplpwDnz2/0bNTF7KN7V0PQnXZQknEnvL 0VACm298Y386hs8bJQFlRlTOzfhguulaaEwdqLaBPkXMKA7LBaVRHM1v5o+Xb40X 7DwSKglkbt6HgX7/nDMX4qk9Kxb2ZEVz+XOozPta2NRoZmaz8y7Xyqc/+4+UTzHH XsNJ2H5yVEo= =GPtw -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] dict.setdefault(object, object) instead of sys.intern() (was Re: sys.intern should work on bytes)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/09/13 15:33, Benjamin Peterson wrote: Well, the pickler should memoize bytes objects if you have lots of the same one in a pickle... Only if they are the very same object. Not diferent bytes objects with the same value. Pickle doesn't do a==b but id(a)==id(b). Yes, I know that a==b would break mutable objects. It is just an example. I don't want to pursue that path. Performance of pickle is already appallingly slow. In my project, I will do the redundancy removal on my own way, as explained in ither message on this thread. Example: * Original pickle: 14416284 bytes * Pickle with interned strings: 3004880 bytes (quite an improvement, but this is particular to my case, I have a lot of string duplications here. The pickle also loads a bit faster) * Pickle including an extra dictionary of interned strings, created using the interned.setdefault(object,object) pattern: 5126587 bytes. Sniff. Could I do this more compactly?. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjxRwZlgi5GaxT1NAQKW8wP/dhVa/v3RZbOKvOtogpHGs5nZyjhtChwn lFK1Lr1wl/+6IgCjgu9axkrRM0LLRaBN91HW+e9AkAM9XSFBQp6qAAqjJpI/jLDp xRLW9fMRHpD21m1tG9zxziz4ACCLNNDnlsyY9l7oHHbMzaAX6Gbigyml3hEbj0uK G5hk4VhyKEY= =m/3T -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] sys.intern should work on bytes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/09/13 15:44, Antoine Pitrou wrote: Yes. The main difference is that sys.intern() will remove the interned strings when every external reference vanishes. It requires either weakref'ability (which both str and bytes lack) or special cooperation from the object destructor (which is why sys.intern() is restricted to str instead of working with arbitrary objects). Great comment. Thanks. Why str/bytes doesn't support weakrefs, beside memory use? - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUjxTqJlgi5GaxT1NAQIbvwP/fs7e5MJwF0pCa0NObTx0xN8CFQIX9/jt VkQ1Q7lPLSuRlZMC2B+0xfp9QoAsD6N3xqSXwG+T9uf7w6nZ9y3keI06kAdSn/Cz D8EyxoeuNk2aGq0VIzMO260mgs9Gr+3DtWAROcWCMG+8sr5uekJ/LAhI04/xMkqZ zr7aOy1xDgk= =hzGP -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 21:34, R. David Murray wrote: Note that I said that single signon *itself* was overrated. If you use the same token to authenticate to multiple sites (and here the 'token' is the email address) then your identities on those sites are ipso facto associated with each other. *If* that email address is also never leaked (never displayed, even to other signed on users, all communication with the site encrypted), then you only have to worry if the sites exchange information about their accounts, or if the government comes knocking on their doors Yes, I'm paranoid. That doesn't mean they aren't listening. Being paranoid is good. Fix for this is actually trivial: Use different emails for different personalities. If you are doing things you really NEED to hide, virtual machines and TOR is the way to go. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUi3lGZlgi5GaxT1NAQLykAQAi8WDuWmEAAX7bP1glDT8iLrMRpKlu+Vh WndX9ObB/os2D9RZkL7DZB01EDMRvfjGlWFm3gQV0CbM9smkgGkhJNLuxYzA2fpK PQlbO4KUKCoQG7qm413TA1g0xxOGzG2n9g2kJisFBCNu2Y2PXroUhm6p41CbTd89 ovwZLLUcPZU= =EQu4 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:18, Skip Montanaro wrote: I looked at this several years ago. As I recall, the problem at the time was that the Apple and Sun DTrace implementations were incompatible, or that the probes they had inserted into their own /usr/bin/python instances were incompatible. (Don't remember which off the top of my head.) Of course, the DTrace folks at Apple and Sun weren't really interested in holding hands... Right. They use two different set of probes because Python doesn't provide official probes :-). If I recall correctly, they were basically identical, with an extra parameter somewhere. I think my patch provides a superset. Anyway, I don't think neither of them support Python 3. Time to step in and liderate. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUinzmJlgi5GaxT1NAQLxwQP/cTq90CCfZhiUVLsutP0dQk4Br62kvCyn mmMV9E/ZPJEO3LYYQT+CSiIRnG5panqdZulMDAGBBvgIbJP/E8spuyoFZkspWtPM fk5n2etHq8JMZs36mbxnhw++W3/jlZ4osdVWZZKoKdwVBRFz2YvpLa24q+Y06gU/ 5YEXHuNDP/4= =YFm2 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Details of import lock in 3.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 With importlib and other recent changes, what are the current details of import lock?. That is, the lock/locks held when Python code does import, specially in the case of multithreading. Is that documented anywhere? Thanks! - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUinv7Jlgi5GaxT1NAQLX7QP/SBNuy869xSKRVNlWmAiDLpZOR9IHm77K fy+AG/aJDpk4BMcm+KNoHZyUtJJs2kndfz+OVTeU/mmlr+aXu/wA1yNB1HAjAwWO 4ZWyaN9WLrhv8xXomUlT8iqikc/9pEspgQbJAljUvMLVouixIdxga3IqtaT3FQZh wkV9v04G4OA= =P3PI -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As far as I know, Erlang, Ruby, PHP, Perl, etc., support Dtrace. Python is embarrasingly missing from this list. Some examples: http://crypt.codemancers.com/posts/2013-04-16-profile-ruby-apps-dtrace-part1/ http://www.phpdeveloper.org/news/18859 http://www.erlang.org/doc/apps/runtime_tools/DTRACE.html I have spend a very long time on a patch for Dtrace support in most platforms with dtrace available. Currently working under Solaris and derivatives, and MacOS X. Last time I checked, it would crash FreeBSD because bugs in the dtrace port, but that was a long time ago. I would like to push this to Python 3.4, and the window is going to be closed soon, so I think this is the time to ask for opinions and support here. Does Python-Dev have any opinion or interest in this project?. Should I push for it? Some (not current) details: http://bugs.python.org/issue13405 DTrace is amazing: http://dtrace.org/blogs/ PS: I can't release this code as a PyPI project, because it mess with the inner core of Python. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUinv55lgi5GaxT1NAQIK7gP8DeaWxNVwNFa5PnfZe00Aay5l1rWzgj8d CY0D3W+PAdPkBci9SYPmfv7ajXrQWo/ccANYIRaUdI/U9Zjq/od7eNemOFqyL7U6 BrQpAUMySI6tMlL+gYEfQ8O47SManvTqoyNvOFAz9mVJute8IxKsbCIK/jiRHDXz vWyG7YrYN1A= =4E7+ -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:08, Jesus Cea wrote: Does Python-Dev have any opinion or interest in this project?. Should I push for it? I have using this code for ages on my Solaris machines: Python 2.7.5 (dtrace-issue13405_2.7:f96ea83cd766, Aug 19 2013, 02:55:15) Python 3.3.2 (dtrace-issue13405_3.3:23dafaf73d29, Aug 19 2013, 05:52:34) Python 3.4.0a1+ (dtrace-issue13405:d7be45bb06a3, Aug 19 2013, 07:03:24) - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUin0uJlgi5GaxT1NAQJP/wQAmkxZ5UJk9L+wTZb94icd3vqUGdo+mgR6 CNs0/oyemd7fL2DSaHGycqDwVPqyqNVFE+aD/ziEmWOwmiFQebudX0Z7md4ZSF89 LU4ddBPMj1bI5E/EYtlqgZg4TqwbUP3XPy9IrCEeiiSKcIk2TJxYiZ12IlcFyXU+ ff3E+DyDkBY= =svJD -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:14, Guido van Rossum wrote: I've heard good things about DTRACE but never used it myself. Do I understand correctly that you have to build a separate Python executable with it turned on? It is a patch you apply on stock Python and you get a new configure option: --with-dtrace. If you compile Python with that flag, you get a python interpreter with dtrace probes on it. I noticed one odd thing in the patch: apparently the dtrace module only exists to have a flag that tells whether it is enabled. Can't that flag be added to the sys module? My plan is to (in the future) use that module to create new probes on the fly, like http://chrisa.github.io/blog/2011/12/04/libusdt-runtime-dtrace-providers/, and to export functions to communicate data to dtrace scripts, if running. That is, this module is currently a shell I plan to fill. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUiny4plgi5GaxT1NAQLngQP/eFoQ3rdPy12nmw8pPPO/+/RYjlhIi67+ T0n1xBJbxIvpFpIRufB+tkCfLWdb7YZKcf3Nb4V6pVsOPdbd9s6RcVWNA9Ds5mNx ISrO644CAIqRF5XgeeS5uhsODL1DrZTEfX0QBhGsU6lcqyOzSfRX2t9hRBMh3f5y 2dPMHNznJhs= =dV5g -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:41, Antoine Pitrou wrote: You should start by addressing review comments: http://bugs.python.org/issue13405#msg151751 Antoine, my first step now is to poke Python-DEV about this subject. If the consensus is DON'T I will probably maintain this patch by myself. I saw big BUTs with this work in the bug tracker, so I rather prefer to ask for actual interest before investing in iron out patch implementation details. If devs actually want it, then next step is to improve current work to make it acceptable in mainline. There are quite a few ugly corners I would love to file out, beside your (really valuable) feedback. That is how I see it. Right now, I agree with Charles-François: your patch is too intrusive. It is intrusive. Yes. I think it must be, by its own nature. Probably room for improvement and code transparency. But... are Python-DEVs interested in the project?. That is the point :) - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUin/Yplgi5GaxT1NAQI6tAP+MaGbSm8j3xPBjMui9tePg2engB+G/ckh TzVac8Gz5yhWhixOFLk3cXYySieB6ttjsAG1NZYKxIwyLSLrxcL8pTh4c8oHB8zu /wYfIdXt6leH6HECXJquPLxLM39Z6KIOTt2QgKYSWy6ZHGzVaaeTFvrMhW0N/5rp SCHSJQc7Vn4= =65h4 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:29, Charles-François Natali wrote: IMO, that's a large, intrusive patch, which distracts the reader from the main code and logic. Yes, the patch is intrusive. It must be, to get its goals. Could be improved, nevertheless. Help and suggestions welcome. I want to write a probe for the GIL, but I didn't because I know adding the cost of an extra single machine code branch would be anathema here :-) (lets do baby steps), but I would love to be able to watch with detail all interaction between the GIL, threads, and OS scheduling on my Solaris :). That is very valuable information to have, for instance, to guide future improvements of the GIL. How can you get that kind of information with any other tool? IMO it's not worth it (personally strace/gdb/valgrind are more than enough for me, and we''re about to gain memory tracing with Victor's tracemalloc). The main value of DTrace is systemwide observability. You can see something strange at kernel level and trace it to a particular line of code in a random Python script. There is no other tool that can do that. You have complete transversal observability of ALL the code running in your computer, kernel or usermode, clean reports with threads, etc. Valgrind doesn't work on Solaris and *BSD support is unclean. You can run a dtrace script in a long running python process if you need it, after launching it, at runtime, and when the dtrace script is done, the python program keeps running without any penalty. Just poking around, for instance. I do it constantly for, for instance, profiling covering both Python as any C code/libraries called from it. Maybe the biggest objection would be that most python-devs are running Linux, and you don't have dtrace support on linux unless you are running Oracle distribution. But world is larger than linux, and there are some efforts to port DTrace to Linux itself. DTrace is available on Solaris and derivatives, MacOS X and FreeBSD. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUin7CJlgi5GaxT1NAQKbfwP+PjOqf3pjlHHq78ggA8qyNkjPFXEoRVj9 9PKslZ7FiU+JWxzXY52k1GNspHhIox+PAcvdBL/gWU3rOiqjEm5fU8FX61Lh6FMj bB+QRyZLpLfmANrLX43sBvwDbG9gTuq8FVUvqmtSme615vX2ygITwNZysQ7xPoD/ jXbeOAF0LZU= =asEC -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Details of import lock in 3.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/13 17:43, Antoine Pitrou wrote: Quick summary here: http://docs.python.org/3/whatsnew/3.3.html#a-finer-grained-import-lock Otherwise, I'm afraid the source code has the most information, e.g.: http://hg.python.org/cpython/file/1d88d04aade2/Lib/importlib/_bootstrap.py#l124 Yes, I was depending of the global import lock in my code. I am evaluating impact under Python 3.3. Under Python 3.3, metafinder/loader MUST BE reentrant?. Can they count on the fact that they could be called concurrently by multiple threads but NOT for importing the SAME module?. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUin8mJlgi5GaxT1NAQKQugP+N0VI/BhqKvcaUicu7YMR09VhFweoAE6h c48ltOrhlWhrauYc9XYeoEPZ2ksl9/SDnMt83cE+qLunSBltkSbYv3j/0LXWyHwk ZGjzh5vQGTgCu3/2iCkFWq/tSAsgUfk8YfbwPQK82L1gs7LbC5vt2jWlRwNQs0nl 2Sr1Nlbf7og= =GL0o -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] DTRACE support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/13 20:33, Antoine Pitrou wrote:
On Fri, 06 Sep 2013 18:14:26 +0200 Jesus Cea j...@jcea.es wrote:
It is intrusive. Yes. I think it must be, by its own nature.
Probably room for improvement and code transparency. But... are
Python-DEVs interested in the project?. That is the point :)
As a concrete data point: - here are Dave's modifications to
ceval.c for systemtap:
http://bugs.python.org/review/14776/diff/5177/Python/ceval.c - here
are your modifications to ceval.c for dtrace:
http://bugs.python.org/review/13405/diff/6151/Python/ceval.c
Unfair, because that code is not doing the same thing.
Most of the extra complexity is there to deal with DTRACE ability to
provide meaningful stackframes, with Python code instead of CPython
evaluation loop. This is kind of magical.
Look at this:
[root@stargate-host /]# ps -lAf|grep -i correo
0 S correo 1371 1 0 40 20? 277063? Jul 29
? 90:43 /usr/local/bin/python /export/home/
0 S root 20397 20373 0 40 20? 1294? 05:18:16
pts/12 0:00 grep -i correo
[root@stargate-host /]# dtrace -n 'python1371:::function-entry
{jstack();}'
5 3164 PyEval_EvalFrameEx:function-entry
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x89a
[ /usr/local/lib/python2.7/logging/__init__.py:1332
(isEnabledFor) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /usr/local/lib/python2.7/logging/__init__.py:1202
(log) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x59ae
[ /home/correo/durus/connection.py:483 (shrink) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /home/correo/durus/connection.py:225 (shrink_cache) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /home/correo/durus/connection.py:303 (commit2) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /home/correo/durus/connection.py:261 (commit) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /export/home/correo/lmtp.py:191 (_monitor) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x59ae
[ /export/home/correo/lmtp.py:125 (process_vacation2) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x59ae
[ /export/home/correo/lmtp.py:138 (process_vacation) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`function_call+0x192
libpython2.7.so.1.0`PyObject_Call+0x5c
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x2b94
[ /usr/local/lib/python2.7/threading.py: ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`function_call+0xa4
libpython2.7.so.1.0`PyObject_Call+0x5c
libpython2.7.so.1.0`instancemethod_call+0xa1
libpython2.7.so.1.0`PyObject_Call+0x5c
libpython2.7.so.1.0`PyEval_CallObjectWithKeywords+0x58
libpython2.7.so.1.0`t_bootstrap+0x52
libc.so.1`_thr_setup+0x4e
libc.so.1`_lwp_start
^C
Lets say I want to know about what codepaths are hitting the OS sync
features, so I do this:
[root@stargate-host /]# dtrace -n
'syscall::fdsync:entry/pid==1371/{jstack();}'
dtrace: description 'syscall::fdsync:entry' matched 1 probe
CPU IDFUNCTION:NAME
3 58344 fdsync:entry
libc.so.1`__fdsync+0x15
libdb-6.0.so`__os_fsync+0x91
libdb-6.0.so`__log_flush_int+0x685
libdb-6.0.so`__log_flush+0x6a
libdb-6.0.so`__log_flush_pp+0x121
_pybsddb.so`DBEnv_log_flush+0x39
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6992
[
/export/home/correo/durus-berkeleydbstorage/berkeleydb_storage.py:918
(flush) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /export/home/correo/lmtp.py:1005 (lmtp2) ]
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x6231
[ /export/home/correo/lmtp.py:763 (lmtp) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`function_call+0x192
libpython2.7.so.1.0`PyObject_Call+0x5c
libpython2.7.so.1.0`PyEval_EvalFrameEx+0x2b94
[ /export/home/correo/lmtp.py:214
(_ignore_socket_errors) ]
libpython2.7.so.1.0`PyEval_EvalCodeEx+0x7b4
libpython2.7.so.1.0`function_call+0x192
libpython2.7.so.1.0`PyObject_Call+0x5c
libpython2.7.so.1.0
[Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just received an email from my OpenID provider, myOpenID, saying that they drop OpenID service next February. I wonder what other OpenID providers are used by other python-dev fellows. What are you using?. bugs.python.org admins could share some data? I agree than OpenID is (quite) dead, but I rather prefer OpenID to use user/pass. I have big hopes for Mozilla Persona, looking forward Python infrastructure support :). PS: I use http://www.jcea.es/; as my OpenID identity, and I delegate the actual service to myOpenID. I can switch delegation trivially. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUijAD5lgi5GaxT1NAQLH0wQAkKDORrAtfJFzzIHl3lHRp7GfxOzdqdNP uiuW65l/pas+p9+B0G6qR6EE2AAL7YPozcNF5AkmuGmxkpyn/JyUYKJcUWmUotpj V9Buz9jz3qpPuv7AlTnMbjBBQK4YTYenbdk2HgI41SVQHZHkU/+y4CL3Y1hWyJNo C8CCWfR0VlA= =YXIq -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/13 21:53, Ben Finney wrote: My own take is that most people choose convenience and expedience over security and freedom, hence Facebook and Twitter and Google have taken over the online identity game instead of a federated identity system. That is one of the Persona improvements: If your email provider is not supporting it, you can still use your email with persona (thru Mozilla servers). If you provider support OAUTH authentication (let say, Facebook, twitter, Google), You can use that identity to prove your identity to Mozilla, and Mozilla to prove your email ID to any Persona consumer. In the process, you get privacy (facebook doesn't know where are you using authentication, beside Mozilla). Being a Persona provider is easy, being a verifier is trivial. An interesting property of Persona is that if its popularity grows, it becomes decentralized automágically. Anyway, I was asking for alternative OpenID providers, not to open a debate about single sign on methods :). - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUikzWZlgi5GaxT1NAQJMbgP/enbARAwUiDXzJ9PkBmvlAi/OrhXrrXwE Vf1f6XHab+ERyJ6kj1V5yz6F0D0zxl6s7GL+abz7P0JEdGEGMfEJc+aK15HM2r3b LAm9k5ofe+ysdJx0HEd/V6/viqAeK7medb5Hh3xNwxbY6qRe4VkXbAvc0KQuo7eR 1Uf005ibUT8= =i0/D -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/13 22:36, Oleg Broytman wrote: There was no demise. Because there was no take-off. OpenID was never popular. I can remember a very limited set of major sites that allow login using OpenID: SourceForge, LiveJournal, BitBucket. The first two I remember a day where OpenID was the ONLY authentication method in StackOverflow. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUik1Iplgi5GaxT1NAQKHGQP/ayFi3hs5CWwlNCciFguNkUesQBfRaPFF TxHrloNM2Uo9wB2dt2oAVhAQnGSTw3lIYoRMzhk5+tfx4Bn16QVPiDXnbotO5xqn QkAH3ZE9q9/YTDDqPJPFXHP/7eoQwk9Ou4LrTJk97ofp0DM7JcfVm3W0Sys53wEQ ddwoNkrIk/s= =vFd+ -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/13 23:56, Oleg Broytman wrote: Well, I can only use services that are available, not those that are promised. If python.org grows support for Persona -- who will be my provider and for what price? I am not going to install and manage additional software on my servers -- I don't want to be my own provider, I have enough job already. If your email provider is not supporting Persona, the automatic fallback is Mozilla, a non-profit, free web, I care about your privacy, organization. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUik1Y5lgi5GaxT1NAQLKjwP9EXXmMTVORDPOCK5ByBfrwveL71nG/1IJ oTc0ZUjZPMp/JD2UBnibEUIhxJHtmAkTsuMTmNsSbzqx6F74n9zYokfMK4Y0iscC 2EpqDe7lcAzEjJXpIa93A/K8/fh3gaufWHAXND3Ynr7gMdlLkn9jRiXoVMHHX3Sm lEIX/47kzlI= =4+OP -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Offtopic: OpenID Providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/13 22:29, Oleg Broytman wrote: I have seen exactly 0 (zero) sites that support Persona. Can you point me? Python España (Python Spain) association is going to provide Persona Only login. Deployment in four weeks. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUik1uZlgi5GaxT1NAQIA3wP/eH0HA+gxa/9c1S679lmC7GVoBqahWyWS mmOnIg170MaozIxyjgLruReTKdnfhcFa/QxxWLpS7brGenOSA1UCXdOhRHRTpf5y JMtQ/f1pmS3sdjEIal2F6Fm1Dt1i6YFZr813j9hdzVHgcx96PuxTx5UVO3LpAAkf +edD8PBn3eM= =y1Ri -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Posting frequent spurious changes in bugtracker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This happens to me very frequently. I get the notification about new issues open in the bugtracker. If I see an interesting bug, I usually open a Firefox tab with it, to monitor it, decide if I will work on it in the future, whatever. When I have time to decide, I proceed. If I find the issue interesting but don't have the time to work on it, or somebody else is taking care of it, I just add myself to the nosy list, and close the tab. The problem with this is that even if I reload the tab, flags are usually stale and when I add myself to the nosy list, I revert flags to the old value. This happens frequently. Last time: http://bugs.python.org/issue16833#msg178917 I think tracker should keep a version hidden field, and refuse to act if the version on server is different that the just posted changes. Or something. Or am I doing something fundamentally wrong?. I reflesh 99% of the time, but could forget sometimes, and some other times I need a shift+reload to bypass browser cache. PS: Tracker tells me about conflicts ocasionally, but most of the time the stale flags are not noticed. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQCVAwUBUOXi2Zlgi5GaxT1NAQK6ewQAlCv0RKb3/y6tzdjggm4JqOjt0E9vYyZJ o0FIC+KBTrVtWrACiBOKCHPVsvJ1KB+6RzQ4FJdIyeOzG8Kv/E0HUNDufLGjr41C NCd4O8FN0tpHIfJkpC3PbkinyhZpviQL7YindAteb92sa+QFm8Rp+QCKBFRecMUX A7WLf+Gk8pE= =famI -END PGP SIGNATURE- ___ 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
[Python-Dev] push changesets hooks failing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I got this when pushing: jcea@ubuntu:~/hg/python/cpython$ hg push pushing to ssh://h...@hg.python.org/cpython/ searching for changes searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 4 changesets with 9 changes to 3 files remote: buildbot: change(s) sent successfully remote: sent email to roundup at rep...@bugs.python.org remote: notified python-check...@python.org of incoming changeset 0ffaf1079a7a remote: error: incoming.irker hook raised an exception: [Errno 111] Connection refused remote: notified python-check...@python.org of incoming changeset 3801ee5d5d73 remote: error: incoming.irker hook raised an exception: [Errno 111] Connection refused remote: notified python-check...@python.org of incoming changeset b6a9f8fd9443 remote: error: incoming.irker hook raised an exception: [Errno 111] Connection refused remote: notified python-check...@python.org of incoming changeset 3f7d5c235d82 remote: error: incoming.irker hook raised an exception: [Errno 111] Connection refused - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQCVAwUBUNsdf5lgi5GaxT1NAQKuzQP+IPef5nx00zKdUwL4LoLDds05Dl+WtrFu Vs+Nvm4haa1+NNJ1owodtA5Xp01pDhMrhv4dvFcfEdbF2zLi3h8Xo+9oO6sEGhqE cMJZJxRCa4RdC9zpFzw0jWS7Udn/j91veWqaR/HLPYeKWcaXqWOegI+f2aoCBbQ7 5cd8Ynqihxw= =xUEy -END PGP SIGNATURE- ___ 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
[Python-Dev] Bootstrap issue: select is compiled too late
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://buildbot.python.org/all/builders/x86%20OpenIndiana%202.7/builds/1287/steps/compile/logs/stdio The relevant part: ranlib libpython2.7.a gcc -o python \ Modules/python.o \ libpython2.7.a -lsocket -lnsl -ldl-lm Traceback (most recent call last): File ./setup.py, line 8, in module from platform import machine as platform_machine File /export/home/buildbot/32bits/2.7.cea-indiana-x86/build/Lib/platform.py, line 116, in module import sys,string,os,re,subprocess File /export/home/buildbot/32bits/2.7.cea-indiana-x86/build/Lib/subprocess.py, line 429, in module import select ImportError: No module named select My patch adds a select dependency, and select is not compiled yet at this stage. Any suggestion about how to solve this? Thanks!. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG2A/5lgi5GaxT1NAQL0KAQAgTFJc8owtoCAAAQGhhhTqGgrUuUegrM+ PCVZr/IVdnv+tNzAZWl84ng4ZQbfXBzU+6y5XIga0dpifqee9VOVNnLcHL4xv4fP EWV4jZ9AWN8fPiAbgAe6MGQp3NYlRWTDRoPZTz/zXLqHxzMYzr9LpAOURqXr2/eB VbYTRAhkGdM= =m3j8 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Bootstrap issue: select is compiled too late
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/12 14:34, Benjamin Peterson wrote: 2012/10/4 Jesus Cea j...@jcea.es: Any suggestion about how to solve this? Easy solutions include somehow removing the dependence on subprocess or moving the import of subprocess into the function that uses it. Moving the import into the function that needs it solves the issue. See http://hg.python.org/cpython/rev/d6d908dc11f2. Thanks for the suggestion, Benjamin. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG2MhJlgi5GaxT1NAQLiuAP+OkMW7wVO3rDvbpBGwes5hf6SfixrOyWu E/ZMcnhoJ3q8VCdpgIR0GKgzBobc4NuNFotakXe10JH6tQKJe/lnZfgzlJwvj5Pc G85anv08789oYrxzijmqcdrBJUrSoiqO1WEJBhELUFLjT9gtNnQ2RlEID81LMEzq Su3+VieZcBk= =flZu -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Proposed schedule for Python 3.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/12 17:27, Nick Coghlan wrote: I received a fair number of complaints from people that wanted to experiment with yield from, but couldn't, because the first alpha wasn't out yet and they weren't sufficiently interested to go to the effort of building their own copy of Python. In my job, we do alpha releases quite frequently. The promises for alpha is: a) no feature complete, b) the API, etc , can change before release, c) features included are useable. The point is to use them and experiment with them. We don't call them alphas, but engineering previews. And they expires after six months. Delivering useable alphas requires to do a minimal of release engineering, like disabling features half done, documenting known bugs, etc. So yes, it it a bit of extra work. In Python context, the idea of somebody using a alpha in production is scary, and I have a few bad experiences doing a make install of a alpha and when installing the final release keeping some alpha files around causing erratic behaviour until I did a \rm -r /usr/local/SOME and reinstall again. I think it happened to me with 2.6 :). There are some consequences here, like bytecode (pyc) changes, modules renaming or vanishing before the final release, etc. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG2P6Jlgi5GaxT1NAQJLBgP9GRnurLjdx2IIcrnbjGuRC0EoQF5ISh5p nVQldPRefb3c3MEpsVK0pmTDiPY0Nelepg8j8YMjZeri87AKHojMQ6Teu6NGvx/5 ZMRFsBve8YKfkqAr0ygVl8RlscOMXZsCq2iUHhc8I4L2Nqx7H7yoUDlMcak8JB4t VxYAhugWOmE= =/2aa -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Bootstrap issue: select is compiled too late
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/12 18:38, Nick Coghlan wrote: You can still technically deadlock, but you need a circular import *and* two different threads that start at different parts of the cycle. Is this true for 2.7 too, or only for recent 3.x? - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG4BkJlgi5GaxT1NAQJ3vgP9EDK6d3IKYV02cx/7JFNehK/+MvSdgIUp KXbf1hlvnMGsWnKgFFKZ4GC16+apyS5g0zXQU5qea/83l06/krcFaERSfZO++alY jgMJ4AFNBH8r6svoC9Y12WvutV4spzntVWal7kGYh7qTroFceI2sfxHK0PZrsgvn +qrCmBxspg0= =2KBh -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Tru64 support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/12 00:11, mar...@v.loewis.de wrote: We don't need to. It's perfectly fine if it breaks - we just can't actively remove code to support the platform. OTOH, if Tru64 was proposed for unsupport, we could disable support in 3.4, and remove support in 3.5. Perhaps that would be a good thing to do. In some other email in this thread you said that support was (partially) deprecated in 3.0, so removal in 3.4 would be justified. In any case, somebody have to take a decision and update PEP-11. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG4LKZlgi5GaxT1NAQKeCAQAg43Y6LgrYwJWP/TSDx4X9t+lSxE/47HF J0cEdFtEhT3hm08qFi3fKhR4p7K8gTVFRxNqVBu89dacjCPUrbbnLVI3tTJjvrst Joqx5RDZv1q3m/OwoFz+kIXEJFEtVNPY/geQlGGYkyoowc/FqFWl/ygpl8rTdjla NvFmdoBGFUY= =DIYs -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] what´s new 3.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/09/12 12:55, Kristján Valur Jónsson wrote: Hi there. Not having kept up, I realized I failed to contribute to the What's new thingie. Here's stuff I remember working on and putting in: 1. pickling support for built in iterators (#14288) 2. inter process socket duplication for windows (#14310) 3. Progress callback for gc module (#10576) 4. Faster locking on windows (#15038) DiSome of this should probably be mentioned in the What's new document, even if only in its online version. Please, update Doc/whatsnew/3.3.rst in 3.3 branch. The changes are automatically available in the online documentation after a while (a few hours). - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQCVAwUBUG5GZplgi5GaxT1NAQKhaQP/RKzxA44RN2VZeD9MTIK/tiS8ddg/uAWA 9YPYYwVoDQf/sF1S+W/zb/Vf3YjuoHsFFLGTzWIHkY6G8hiVGGfks91/3Ur7n/GO kE6CHQRpCzMYYnR2MvMjqlO99BD1++ex/+MKSiYFTUwsTIBVLSFicB5oG5WzWH/a cKl8n0DCv8w= =ULJD -END PGP SIGNATURE- ___ 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
[Python-Dev] HTTPS repositories failing when using selfsigned certs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My mercurial clone is https://hg.jcea.es/cpython-2011/, and today I
can't create a patch from it (in the bug tracker). No explanation in
the web interface, but checking the sourcecode of the resulting page,
I see a SSL certificate failure.
So, looks like bugs.python.org is now verifying repository certificates.
My certificate is selfsigned and, moreover, it is behind a SNI server,
so the certificate python.org is getting is a selfsigned jcea.es
certificate.
What can I do, beside buying a real cert?.
Do we have a certificate whitelist, like mercurial?. In my .hgrc, I use
[hostfingerprints]
# En realidad es www.jcea.es. hg.jcea.es esta tras SNI
hg.jcea.es = 54:7e:a7:36:56:c6:80:41:f8:fd:d6:c0:95:44:68:a9:93:58:ca:4c
PS: If I try to use the http version of my repository
(http://hg.jcea.es/cpython-2011), I get an error: ('invalid token',
97).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/
My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/
El amor es poner tu felicidad en la felicidad de otro - Leibniz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBUBipTplgi5GaxT1NAQKyjQP9F1rIKSlDIs8uHLrhIVmaOodRH3umYeyl
zhkiGm34+Cw6I22OQre3VoJ+9vrUF/Go/LpU+UpAH5adzgq4Xfef3Q8jRhclSZmU
ADvGpKhmlzDCahxsQoYXD7UHkc/BLkfNvx+q0wzfDUELbinLyITF4pp2/dLtoNtN
LFG9te1M55A=
=pgh1
-END PGP SIGNATURE-
___
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
Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 - default): MERGE: Better test for Issue #15402: Add a __sizeof__ method to struct.Struct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/07/12 18:27, Meador Inge wrote:
Doc/ACKS.txt is *only* for acknowledging documentation
contributions. Serhiy is already in Misc/ACKS. No need to add him
to Doc/ACKS.txt.
Oh, I missed that. Thanks for the head up.
As for the tests, I intentionally kept them the way that Serhiy
contributed them -- using = instead of . I kept them this way
because we also discussed in issue14596 the prospect of optimizing
the way repeat counts are handled. These tests would start failing
if (when) that optimization happens.
The problem is that if we do =, then an unpatched python
interpreter could pass the test too. So we are not actually testing
the feature.
If the repeat counters are going to be optimized, the obvious step
would be to upgrade the test to do something like BHHIL instead of
123B. I would wait until this feature is implemented to update the test.
What do you think?.
So, neither of these changes are really necessary. Although, it
wouldn't hurt to have *additional* tests using the relation.
diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt --- a/Doc/ACKS.txt +++
b/Doc/ACKS.txt @@ -205,6 +205,7 @@ * Anthony Starks * Greg Stein
* Peter Stoehr + * Serhiy Storchaka * Mark Summerfield * Reuben
Sumner * Kalle Svensson diff --git a/Lib/test/test_struct.py
b/Lib/test/test_struct.py --- a/Lib/test/test_struct.py +++
b/Lib/test/test_struct.py @@ -575,12 +575,12 @@ def
test_sizeof(self):
self.assertGreater(sys.getsizeof(struct.Struct('BHILfdspP')),
sys.getsizeof(struct.Struct('B'))) -
self.assertGreaterEqual(sys.getsizeof(struct.Struct('123B')), +
self.assertGreater(sys.getsizeof(struct.Struct('123B')),
sys.getsizeof(struct.Struct('B'))) -
self.assertGreaterEqual(sys.getsizeof(struct.Struct('B' * 123)),
+self.assertGreater(sys.getsizeof(struct.Struct('B' *
1234)), sys.getsizeof(struct.Struct('123B'))) -
self.assertGreaterEqual(sys.getsizeof(struct.Struct('123xB')), -
sys.getsizeof(struct.Struct('B'))) +
self.assertGreater(sys.getsizeof(struct.Struct('1234B')), +
sys.getsizeof(struct.Struct('123B')))
def test_main(): run_unittest(StructTest)
-- Repository URL: http://hg.python.org/cpython
___ Python-checkins
mailing list python-check...@python.org
http://mail.python.org/mailman/listinfo/python-checkins
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/
My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/
El amor es poner tu felicidad en la felicidad de otro - Leibniz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBUA1+Bplgi5GaxT1NAQJtSAQAkv5DyoQ1N1YdOH2QLHnFbOsvp/1aG0Vy
hHMlD6cu/L7Ub+gyWWo65v9Dp4sLahV+CYem1wL4Fzd2QyBNQdg+BNou9eqoDzGF
IJbY2HALwOwz1vgeBiamFOSvpyWya/hzXR9I7rkBqXdR9c2Njdl/ioZQNKETO05k
TRfd/BQas4k=
=TKFO
-END PGP SIGNATURE-
___
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
Re: [Python-Dev] Doc/ACKS and Misc/ACKS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/07/12 19:30, Eli Bendersky wrote: That said, we could probably merge Doc/ACKS and Misc/ACKS (*). There doesn't seem to be any strong argument for separating doc contributions from other contributions. (*) I think perhaps Éric already proposed it at some point +1 +1 too. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBUA2XtJlgi5GaxT1NAQKiXQQAnOmVaALBmcAbEK7vImQ03m6tdh86ZyU/ VyRuoHVgHxsOn83h2VG+94zjNutedIMK9rq1hEhhPApJcXnYwftMpgEwlyj7vLFA RUz8c02sKpoi/T8BGv2xVdW09yeMCUwzTDAuaS73NqscwcGplibaSPU5oKOjqetc NhS0JdGQcr8= =Ifpc -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 - default): MERGE: Better test for Issue #15402: Add a __sizeof__ method to struct.Struct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/07/12 20:19, Meador Inge wrote:
self.assertGreaterEqual(sys.getsizeof(struct.Struct('123B')),
[...]
and while they didn't fail without the patch I felt they were still
useful in documenting that there is nothing that guarantees
'sizeof(123B) sizeof(B)' 'sizeof(B * 123)
sizeof(123B)', or 'sizeof(123xB) sizeof(B)'.
No garantee, but I would find interesting that
sizeof(1234B)==sizeof(B).
If someday we implement some clever idea here (like the repeat counter
optimization discussed), we can simply change sizeof(123B) to
sizeof(12345B), or to sizeof(BHBHBHBH), etc.
It isn't that big of a deal. We can just leave the tests as you
changed them. In the future it would probably be better to hash
this stuff out in the tracker. The patch was out for review for
several days ...
I agree. I should have raised this issue in the tracker. The fact is
that I was checking the patch carefully today, when we collided
mid-air working in the same issue both of us :-). I disliked the
proposed tests at that time.
Thanks for raising the issue. I will try to be more careful.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/
My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/
El amor es poner tu felicidad en la felicidad de otro - Leibniz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBUA2ZiZlgi5GaxT1NAQKwLQP/RqrP5qbvUtZ9MCuyTaT45l8+7QzqlJrx
Nyh2t98jWVxiso0FDyT2vw839lX0CwssuKyNPFkXzKicNiX4mW0rC1uxNajCk0kG
aVHKL6aC+65iJhA7+9uOW1yfRFyhqQbUc3aRlvg7UJMj4YEfB82Okk/2Wu0hgyiU
4Ti5VvFuOZ8=
=G/WJ
-END PGP SIGNATURE-
___
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
[Python-Dev] Adding GNU conditional execution in the Makefile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Working in the DTRACE probes, I think I can simplify the build logic quite a bit using the GNU Makefile conditional execution: https://www.gnu.org/s/hello/manual/make/Conditional-Syntax.html. In concrete, I have object files that must be compiled and linked, or not, according to a configure test result. But currently I think we are not using these features. Maybe because we don't want to force the use of GMAKE, I don't know. If this is a policy, I would like to know. And if somebody has a suggestion to cope with this difficulty... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTuPrqZlgi5GaxT1NAQIRmQP/ebIcya/xg/lCTXPd6QyaBaFxrhL6jLiP osKeklCSH/aw6tt6v1lK7XgPf8HBEU11KGBmL4xJUsVcDExkNb3Mdu3bSW4Gb5ao Ep1PxvEWLxa/yVkKuvgdBpvdCoxibhNLfGgVTj08ZE18o9tGbhNKS6EN94uAQJT9 ZASlf8baOss= =5lr+ -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Long term development external named branches and periodic merges from python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/11/11 06:06, Nick Coghlan wrote: So, in this context, if the tracker create patch diff from BASE, it is not safe to merge changes from mainline to the branch, because if so create patch would include code not related to my work. No, Create Patch is smarter than that. What it does (or tries to do) is walk back through your branch history, trying to find the last point where you merged in a changeset that it recognises as coming from the main CPython repo. It then uses that revision of the CPython repo as the basis for the diff. Oh, that sounds quite the right way. Clever. So if you're just working on a feature branch, periodically pulling from hg.python.org/cpython and merging from default, then it should all work fine. So, my original question is answered as yes, you can merge in changes from mainline, and 'create patch' will work as it should. Good!!. Thanks!!!. Anybody knows the mercurial command used to implement create patch?. It's not a single command - it's a short script MvL wrote that uses the Mercurial API to traverse the branch history and find an appropriate revision to diff against. Publish out somewhere would be useful, I guess. This is a problem I have found in a few other projects. I can see even a modifier for hg diff for a future mercurial version :-). Could be implemented as a command line command using revsets?. Propose a new revset to mercurial devels? - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTtPze5lgi5GaxT1NAQIT9gP+N4urbw7TgCWTa7EFZ4rjj7/o9f3aBq4I kYBnVZGmh98YqjHL0MzHhhu2a+G6pC/Zksf9CyIinPol4DJR8zGhBDIxo6SNIja+ QsSyQ7DhBWkSwKZAKqBNSdBBH0fu/DpdmNv6fP0s04Ju6sllvHAbEN/oj9zWqxWM KjAMzrgPcSA= =zViH -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Long term development external named branches and periodic merges from python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/11/11 17:30, Éric Araujo wrote: That is what I want to do, but I need to know that it is safe to do so (from the Create Patch perspective). I don’t understand “safe”. Safe, in this context, means when clicking 'create patch' the created patch ONLY includes my code in the development branch, EVEN if the branch merged-in the original mainline branch several times. 6. What would be posted in the bug tracker when she does a new Create Patch?. Only her changes, her changes SINCE the merge, her changes plus merged changes or something else?. The diff would be equivalent to “hg diff -r base” and would contain all the changes she did to add the bug fix or feature. Merging only makes sure that the computed diff does not appear to touch unrelated files, IOW that it applies cleanly. (Barring bugs in Mercurial-Roundup integration, we have a few of these in the metatracker.) So you are saying that Create patch will ONLY get the differences in the development branch and not the changes brought in from the merge?. I don’t really understand how you understood what I said :( The merge brings in changes from default; when you diff your branch against default later, it will not show the changes brought by the merge, but it will apply cleanly on top of default. But I am not doing that diff, it is the tracker who is doing that diff. I agree that the following procedure would work. In fact it is the way I used to work, before publishing my repository and using create patch in the tracker: 1. Branch. 2. Develop in the branch. 3. Merge changes from mainline INTO the branch. 4. Jump to 2 as many times as needed. 5. When done: 5.1. Do a final merge from mainline to branch. 5.2. Do a DIFF from branch to mainline. After 5.2, the diff shows only the code I have patched in the branch. PERFECT. But I don't know if the tracker does that or not. Without the final merge, a diff between my branch and mainline tips will show my changes PLUS the undoing of any change in mainline that I didn't merge in my branch. Since create patch (in the tracker) doesn't compare against the tip of mainline (at least not in a trivial way), I guess it is comparing against the BASE of the branch. That is ok... as far as I don't merge changes from mainline to the branch. If so, when diffing the branch tip from the branch base it will show all changes in the branch, both my code and the code imported via merges. So, in this context, if the tracker create patch diff from BASE, it is not safe to merge changes from mainline to the branch, because if so create patch would include code not related to my work. I could try actually merging and clicking create patch but if the result is unpleasant my repository would be in a state not compatible with create patch tool in the tracker. I rather prefer to avoid that, if somebody knows the answer. If nobody can tell, experimentation would be the only option, although any experimental result would be suspicious because the hooks can be changes later or you are hitting any strange corner case. Another approach, that I am doing so far, is to avoid merging from mainline while developing in a branch, just in case. But I am hitting now a situation while there are changes in mainline that overlap my effort so I am quite forced to merge that code in, instead of dealing with a huge divergent code in a month. So, I have avoid to merge in the past and was happy, but I would need to merge now (changes from mainline) and I am unsure on what is going to happen with the create patch option in the tracker. Anybody knows the mercurial command used to implement create patch?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTtMMPplgi5GaxT1NAQKzhQP8DzAql1PAJkyEROsWl8CgPpW9ie8jNM1V +K5jLx/dCukzFXrZ2Ba1Tu5IFYFZxH7Wj4rg4sQ47zlKBi6gQELgtGV+bCYPAEt/ WQo7uGUCj+xLmBKXuQQlXrl1pNl9XhlufTNXIzW34o7SPKMEQy7N7uUxpxgwV8JX KoJoYAbiH88= =9lYm -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Merging 3.2 to 3.3 is messy because Misc/NEWS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/11 16:56, Éric Araujo wrote: Ezio and I chatted a bit about his on IRC and he may try to write a Python parser for Misc/NEWS in order to write a fully automated merge tool. Anything new in this front? :-) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTtBMi5lgi5GaxT1NAQLKsgP6At6qnzHknuTjq35mHfxVSOxJnMuZ8/vx 5ZXHcxCuPJud9GJz0+NEmDPImQAtRUZyV41ud9nQYIfhYE5rV4qBiK7KwMspg39o kclfRhMIPsQV3PkB4dDWy+gEkck+Q16pSzdtxbzKx7DpYk7lnFp/vsHQbNC5iqC9 pfmMny4L0s8= =NlDr -END PGP SIGNATURE- ___ 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
[Python-Dev] Long term development external named branches and periodic merges from python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a question and I would rather have an answer instead of actually trying and getting myself in a messy situation. Let say we have the following scenario: 1. A programer clones hg.python.org. 2. Programer creates a named branch and start to develop a new feature. 3. She adds her repositorynamed branch to the bugtracker. 4. From time to time, she posts updates in the tracker using the Create Patch button. So far so good. Now, the question: 5. Development of the new feature is taking a long time, and python canonical version keeps moving forward. The clone+branch and the original python version are diverging. Eventually there are changes in python that the programmer would like in her version, so she does a pull and then a merge for the original python branch to her named branch. 6. What would be posted in the bug tracker when she does a new Create Patch?. Only her changes, her changes SINCE the merge, her changes plus merged changes or something else?. What if the programmer cherrypick changesets from the original python branch?. Thanks! :-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTs50H5lgi5GaxT1NAQJsTAP6AsUsLo2REdxxyVvPBDQ51GjZermCXD08 jOqKkKY9cre4OHx/+uZHEvO8j7RJ5X3o2/0Yl4OeDSTBDY8/eWINc9cgtuNqrJdW W27fu1+UTIpgl1oLh06P23ufOEWPWh90gsV6eiVnFlj7r+b3HkP7PNdZCmqU2+UW 92Ac9B1JOvU= =goYv -END PGP SIGNATURE- ___ 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
[Python-Dev] 404 in (important) documentation in www.python.org and contributor agreement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trying to clear the licensing issues surrounding my DTrace work (http://bugs.python.org/issue13405) I am contacting Sun/Oracle guys. Checking documentation abut the contributor license agreement, I had encounter a wrong HTML link in http://www.python.org/about/help/ : * Python Patch Guidelines points to http://www.python.org/dev/patches/, that doesn't exist. Other links in that page seems OK. PS: The devguide doesn't say anything (AFAIK) about the contributor agreement. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTs7ayZlgi5GaxT1NAQLOfwQAoa1GFuQZKhbXD3FnmH3XUiylzTMBmXMh vB++AdDP8fcEBC/NYZ9j0DH+AGspXrPg4YVta09zJJ/1kHa2UxRVmtXM8centl3V Jkad+6lJw6YYjtXXgM4QExlzClsYNn1ByhYaRSiSa8g9dtsFq4YTlKzfeAXLPC50 DUju8DavMyo= =xOEe -END PGP SIGNATURE- ___ 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
[Python-Dev] webmas...@python.org address not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When mailing there, I get this error. Not sure where to report. Final-Recipient: rfc822; sdr...@sdrees.de Original-Recipient: rfc822;webmas...@python.org Action: failed Status: 5.1.1 Remote-MTA: dns; stefan.zinzdrees.de Diagnostic-Code: smtp; 550 5.1.1 sdr...@sdrees.de: Recipient address rejected: User unknown in local recipient table - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTs7fQZlgi5GaxT1NAQLxrQQAmph2w/KrLbwK34IVFKNKAn3P78uY19U1 yoUslB7J4u4IhqQHd5r/FD0v6q6W12t9H8UFNdKELc/zRnRWtE7wKI+3RAeBMAfe pTV6OY7kbGtUfDk9na8o6+oEQ7iZUWT1LbBtMpSusHBuif239RD3HMeaaJ6u/BFT TMmsu39qf2E= =ecRu -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Long term development external named branches and periodic merges from python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/11/11 18:08, Éric Araujo wrote: I have a question and I would rather have an answer instead of actually trying and getting myself in a messy situation. Clones are cheap, trying is cheap! cheap wink I would need to publish another repository online, and instruct the bug tracker to use it and create a patch, and play for the best or risk polluding the tracker. Maybe I would be hitting a corner case and be lucky this time, but not next time. Better to ask people that know better, I guess. 5. Development of the new feature is taking a long time, and python canonical version keeps moving forward. The clone+branch and the original python version are diverging. Eventually there are changes in python that the programmer would like in her version, so she does a pull and then a merge for the original python branch to her named branch. I do this all the time. I work on a fix- branch, and once a week for example I pull and merge the base branch. Sometimes there are no conflicts except Misc/NEWS, sometimes I have to adapt my code because of other people’s changes before I can commit the merge. That is good, because that means your patch is always able to be applied to the original branch tip, and that you changes work with current work in the mainline. That is what I want to do, but I need to know that it is safe to do so (from the Create Patch perspective). 6. What would be posted in the bug tracker when she does a new Create Patch?. Only her changes, her changes SINCE the merge, her changes plus merged changes or something else?. The diff would be equivalent to “hg diff -r base” and would contain all the changes she did to add the bug fix or feature. Merging only makes sure that the computed diff does not appear to touch unrelated files, IOW that it applies cleanly. (Barring bugs in Mercurial-Roundup integration, we have a few of these in the metatracker.) So you are saying that Create patch will ONLY get the differences in the development branch and not the changes brought in from the merge?. A hg diff -r base -as you indicate- should show all changes in the branch since creation, included the merges, if I understand it correctly. I don't want to include the merges, although I want their effect in my own work (like changing patch offset). That is, is that merge safe for Create Patch?. Your answer seems to indicate yes, but I rather prefer an explicit yes that an implicit yes :). Python Zen! :). PS: Sorry if I am being blunt. My (lack of) social skills are legendary. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTs7/1Jlgi5GaxT1NAQJUDAQAhQi5e3utsVdOveO/3r1EDr/9BUTpB8Tb DxIe12HEt+KT33CJR+HGTt9OBqNGmVb4Q3h8lj3YIi7WdIXjc3CQ3+dO1NF1jTZO 0rt5EbEU99RAkgqOT0r3ziKy6MSSWhTuZlQy6pvcivEJet0GANiNqbdw6xFBETeZ a5m85Q793iU= =1Kg3 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Merging 3.2 to 3.3 is messy because Misc/NEWS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/11 19:51, Terry Reedy wrote: If a bug is fixed in 3.2.latest, then it will not be new in 3.3.0, so perhaps it should not be added there. NEWS could just refer back to previous sections. Then 3.3.0 News would only be new features and the occasional ambiguous item not fixed before. I am confused. My usual usage case is this: 1. I fix something in 3.2. 2. I merge that fix into 3.3. Everything goes smooth except Misc/NEWS. 3. Recover the original 3.3 Misc/NEWS, and add manually what I added to the 3.2 Misc/NEWS. Mark the file as resolved and commit. I would like to avoid (3). A custom merge script is an option, but seems complicated and error prone. I have the feeling that structuring Misc/NEWS in the right way could solve it automatically. Something like adding patches to be up-ported/merged at the end of the section, 3.3 only patches be added at the beginning, so they don't conflict. A bit of discipline and, voila, automatic flawless merges! :-) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTrr87plgi5GaxT1NAQL5GgQAnKsWb4TM1oXXo4Dg84XFIHoKpxQQwRWq oKFIaddNOaZ3wp+ccR0G2aoi+LX2BrsEn3sBL7RXRXVFPludGDvonWcvHar/2DLw E52jDytiMd0gED5TkyqPdck3s6NhUCaZz1qfncI9jHkb2/rznXiBK0mLD+suRleu f+AQ6yoPD2o= =ruC4 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Merging 3.2 to 3.3 is messy because Misc/NEWS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/11/11 12:28, Nick Coghlan wrote: The 3.2.x maintenance release sections are not present in the 3.3 NEWS file - it jumps straight from 3.2 to 3.3a1. So bug fixes should be recorded in both places - the 3.3a1 notes record the deltas against 3.2.0, not against whatever the latest release of 3.2 happens to be when 3.3 is released. But fixes in 3.2.x should be incorporated to 3.3, and be in the Misc/NEWS. The general rule is that everything committed to 3.2 is merged to 3.3 (with very few exceptions, managed via dummy merges, like changing the version from 3.2.2 to 3.2.3) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTrr9oZlgi5GaxT1NAQIPUAP/YQJ4gG1ES0x2LiFN8Hinvk9snUqHJMjC GrgjTGeqAcFBt6vZxVC7UujKwync4BSVPtXX/Fogzj/P3yjN2hNRf/YoL5kHqIID W8HdY0n8ncfiy3ekgpa3i+8Ie4lnSw4OxnxEZMnGkKoH38HCPaRmH1yvcGQsy2yL ZgTwVOM/eUk= =bNy+ -END PGP SIGNATURE- ___ 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
[Python-Dev] Merging 3.2 to 3.3 is messy because Misc/NEWS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When merging from 3.2 to 3.3 Misc/NEWS always conflicts (lately). Instead of copypaste the test manually between versions, has anybody a better workflow?. Since any change applied to 3.2 should be applied to 3.3 too (except very few cases), Mercurial merge machinery should be able to merge both versions except when the changes are very near the version headers. I haven't checked, but I guess that the problem is that the different issues have been added in different positions in the file, so both branches are diverging, instead of only divert in the python versions referenced. If that is the case, could be acceptable to reorganize 3.3 version to ease future merges?. Would that solve it? Ideas?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTrlPl5lgi5GaxT1NAQKVggP/bn6vUhQlHjEYg+pFEInnVXYSudamPafP m6bgX6hKS/MtaixVJGlRnAwJ6UQ/nftjmVn80Yd7CsxnsyPApUZVgzkaLMLOhh++ H08gwxgoh1skciYmtyjsy4Vi4xi/4tehu2IVc73SVXkLVbnkc4z1c2Xmsu4TZ2ai r2ncgxRkHgw= =pCHL -END PGP SIGNATURE- ___ 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
[Python-Dev] Do we have interest in a clang buildbot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, pals. I am seeing a few commits related to clang (a C compiler, alternative to GCC), but we ¿only? have a buildbot using clang as the compiler. If there is interest, I would deploy 32 and 64 bits buildbots under my current OpenIndiana buildbot. What do you think? - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTnHhl5lgi5GaxT1NAQKlJgQApAwlZODoeG3G+HODkoSh6G5myqEXkS/0 YZM6wo+/uWb6ul50Kb9mWhucGhY1tc8wAxCDNsRcm8Vv/6sDLZOV0G++DIK0JXIw BA8TyF/5CI8c5K3wnrVkazTo/Io1kVYMGc1FekIoQFI3oRKdXs/A6h63XWwxDMNu PsGwVD4bizs= =lJ/r -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/09/11 09:18, Antoine Pitrou wrote: Ok, I've added -j4, let's how that works. It is not helping. it is taking tons of memory yet. Another option would be to have a single Python process and fork for each test. That would launch each test in a separate process without requiring a full python interpreter launching each time. Is this the way -j is implemented It uses subprocess actually, so fork() + exec() is used. Yes, does it but fork for each test or simply launch 4 processes, each doing 1/4 of the tests?. BTW, the (nice and helpful) OpenIndiana folks have told me a few hours ago that they would increase my swap limit to 16GB. I am now waiting for this change to be done. Good news :) 16GB of swap activated a few minutes ago. Thanks, Jon and Alastair :-) (OpenIndiana guys). Launching buildbots now and crossing fingers... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmotPplgi5GaxT1NAQKUzQP/Qm+lyCQeldL1XEkkq1EHY5C/hKvMDz9i qOV29iai/hkeqRWY2Fiu4vSfNTDAEil9eEIJQMGmUyYOMCrfOEoDCYzr+xTWfnNu EWzI6mEe8XWIUicGDAf/dbUEk11wtSrtXA09G0Q5oQWg0b6auQHYv5vhZITwDWSO h9rLBnZ0ZHI= =8Mpw -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/09/11 09:18, Antoine Pitrou wrote: Ok, I've added -j4, let's how that works. It is not helping. it is taking tons of memory yet. Another option would be to have a single Python process and fork for each test. That would launch each test in a separate process without requiring a full python interpreter launching each time. Is this the way -j is implemented It uses subprocess actually, so fork() + exec() is used. Yes, does it but fork for each test or simply launch 4 processes, each doing 1/4 of the tests?. BTW, the (nice and helpful) OpenIndiana folks have told me a few hours ago that they would increase my swap limit to 16GB. I am now waiting for this change to be done. Good news :) 16GB of swap activated a few minutes ago. Thanks, Jon and Alastair :-) (OpenIndiana guys). Launching buildbots now and crossing fingers... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmotSplgi5GaxT1NAQIHEwQAhcKKUerwx++/egmYRO86z5XmgiWh/chz j3xNcMau7L2pxqymEUwfQKihXrYS58ocTiRBEyHAl3vMOouRwgS8joT2eQugfjux Cy+Rglw+4yg99n+eGwF0z4QxbEljuBJFIrR/+BKeN0sBdT/n1/PZIkN/cWMLDk8t bw1FtxfSW6s= =F0er -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/09/11 19:04, Antoine Pitrou wrote: On 08/09/11 09:18, Antoine Pitrou wrote: Ok, I've added -j4, let's how that works. It is not helping. it is taking tons of memory yet. That's rather strange. Is it for every test or a few select ones? I can't reproduce after stopping the buildbots, delete all its data and restart them. Now I see quite a few python processes running, but memory usage is reasonable. Yes, does it but fork for each test or simply launch 4 processes, each doing 1/4 of the tests?. It forks for each test. So, the memory used should be quite low, then :-). I have committed a few patches in the last hours to get my buildbots green, back again. The memory used was 500MB, compared with 4GB before the -j. Could you reconfigure my buildbots to be able to run all the six (2.7, 3.2, 3.x, in 32 and 64 bits) instances at the same time, again?. I have enough resources now. I really sorry to waste your time... Thanks!. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmrTMZlgi5GaxT1NAQIIKgP+LE1NCfcCVIX+jau4QSJRAVvZan4rqqYn /tMLaz92/toP2S8FdHKbEPs6hBf6QGgnVxnHWcwTxxTWzfDL8xxGjFgJYh/hcqBi B2zfrp83PjW6hFMeL6E7707DI6YwZRCB+dJIiVejAIEMHVOVG6x12KRLFCWL+AOZ ElpXewoATXI= =fHkz -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/09/11 05:02, Jesus Cea wrote: I have committed a few patches in the last hours to get my buildbots green, back again. The memory used was 500MB, compared with 4GB before the -j. One of my patches solves a process leak in multiprocessing, when some tests failed. Doing make test leaked quite a few processes, but only in OpenIndiana, where those tests actually failed. That is solved now, both the leak and the test failure. Details: http://bugs.python.org/issue12948 http://bugs.python.org/issue12950 I think the buildbots toke care of this rogue processes after the timeout expires, anyway, but... Could you reconfigure my buildbots to be able to run all the six (2.7, 3.2, 3.x, in 32 and 64 bits) instances at the same time, again?. I have enough resources now. I really sorry to waste your time... Now, a buildbot run of 3.x compiled in 64bits takes around 500MB. I have seen a peak of around 4GB and a few of around 800MB, for a fraction of a second. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmrY6plgi5GaxT1NAQKvUgP/YlS7wneU5dsWoAmtqauC02gZUi1D4OpQ 7waM8G1q8OHXLbpV1jKmBb/32G+rDp1Tm/XCjlHpK1wJcmwWmdPGAbbQp1o5TduJ z+lbPnzWvMCRLJwZDtZAitn4/7VchoAcdTfIYCyBoK/JEUI1Oq0Mt5XeIgtD+FX9 IjwuWzXISqM= =ojrq -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 07:27, Nick Coghlan wrote: It may be the case that with the reduced memory limit, your machine may not be able to run concurrent slaves for 2.7, 3.2 and 3.x as I believe it does now. Antoine has changed the buildmaster configuration to only send me a build simultaneously. It doesn't solve the issue. I don't have enough resources even for a single build. I just send this email to the owner of the machine: XXX, I know you are very busy, but I would like to request formally the removal of the SWAP capping for my zone. After investigating the issue, I learn this: 1. Python make test launch a python process that can consume 300MB of RAM. 2. Under Solaris, a 300MB process doing a fork() will consume 600MB. That is, Solaris reserves this much memory just in case the processes modify their memory (to avoid out of memory condition simply because a process write to its own memory space). 3. So, if a 300MB is forked 10 times, it is going to virtually use 3GB. The real memory used is actually far less in the buildbot case, because the forked process doesn't modify their own memory so much (forked processes use Copy On Write). 4. So, the required memory to run the buildbots is actually modest compared with the virtual memory used. 5. A 4GB SWAP is not enough to run a single buildbot instance. I can have up to 6 instances, but 4GB is not enough for 1. Python-devs have modify the buildbot master for only sending me up to two build simultaneously, trying to help. It is not helping because 4GB of swap is not enough even for a single instance. 6. With an uncapped SWAP, the actual swapping would be quite low, because the swap is used to ensure memory reservation for the forked processes in the worst case (that the forked processes mess with their own copy of the 300MB address space, COW (Copy On Write)). In practice 4GB of RAM and uncapped SWAP would be enough, with no (or little) actual swapping. For this reasons I formally request a reconfiguration of my zone to uncap my SWAP usage. The proof is actually very simple: import time, os a=a*1024*1024*512 os.fork() # 2 processes os.fork() # 4 processes os.fork() # 16 processes time.sleep(10) Running the previous program does this to my swap: (Solaris 10 Update 9) [root@buffy /]# swap -s total: 684704k bytes allocated + 3732892k reserved = 4417596k used, 31829688k available After the programs die, I have this: [root@buffy /]# swap -s total: 156680k bytes allocated + 43284k reserved = 199964k used, 36118796k available In this machine, I have 4GB of RAM, 32GB of swap. So, this trivial test requires 4GB of RAM+SWAP even if it is actually using only ~512MB of RAM. Solaris is (rightly) playing safe being sure the program can actually play/modify its memory space. X, if you can't/don't want to modify my zone configuration, let me know, so I can think what to do next. If I have to talk to somebody else, please let me know. Sorry for bother your with these details. I really appreciate the effort you and your team are doing with OpenIndiana in general and supporting the Python buildbots under OI in particular. I hope we can solve this situation. Thanks for your time and effort. PS: I think that such memory+swap requirements are quite high, anyway, and I will pursuit it. But in the meantime I need the buildbot online, as it was a couple of weeks ago :-) Thanks!. So, the problem is that a) make test takes quite a bit of RAM and b) the buildbot forks some big processes, so the virtual memory needed is BIG. Linux is known for overcommiting memory. That is, playing fast and risky not actually reserving memory, hoping the process will not actually use it or it will do an exec inmediatelly, so this problem can be not apparent under Linux, but it is there. So I have two questions: 1. Can we reduce the memory footprint of the tests?. I can't understand why the python test process is taking so much memory. 2. Why buildbot is forking() big processes?. Can we do something to change this?. I will wait a few days for OpenIndiana team to reply. If the result is not satisfactory, I will try to setup a VirtualMachine with the required resources myself. Crossing fingers... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmdXr5lgi5GaxT1NAQKmRwP/dyg4qEs+oWt4r365D797+ItbHluuEVJ+ mWTZw5HVeDajrN7faGH6WuA/J+dJuBp2H4rB8WIM1U
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/09/11 14:32, Antoine Pitrou wrote: If -j is used, tests get run in a separate process each, so that approach might be an answer. Antoine, I think this would be the answer. Each test would be a bit slower, because I would launch a new python process per test, but I could run 16 tests in parallel (I have 16 CPUs and, actually, most tests are not CPU intensive). I sorry to bother you with these details and waste of time, but could you possibly change my buildbot configurarion to launch, let's say, 4 test processes in parallel, just for testing?. Another option would be to have a single Python process and fork for each test. That would launch each test in a separate process without requiring a full python interpreter launching each time. Is this the way -j is implemented, or is -j something external, like make -j?. BTW, the (nice and helpful) OpenIndiana folks have told me a few hours ago that they would increase my swap limit to 16GB. I am now waiting for this change to be done. I want my six builds in parallel (2.7, 3.2, 3.x, in 32 and 64 bits) back!. Sorry for wasting your time with these mundane details... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmgWgZlgi5GaxT1NAQI/eAP/anenlTjt7NxIzMLK+ME+f84zLurb8MS/ XiLRpVSNDn6TzKnqXtDLfOc6sua81h+ZlpHvuFNHOkK9u/PkmeUKidgoDvASj5Ti ITUmUxigX1j9ZbD1ITkn53msm1xfug3rw/8+Rh//4ONhhbmhSm8ChZ0iNwtntToG 5SwL3BL2iSI= =fCJe -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/11 20:14, Antoine Pitrou wrote: On Fri, 02 Sep 2011 19:53:37 +0200 Jesus Cea j...@jcea.es wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/11 17:57, Jesus Cea wrote: The build hangs or die with a out of memory error, eventually. A simple make test with python not compiled with pydebug and skipping all the optional tests (like zip64) is taking up to 300MB of RAM. Python 2.7 branch, current tip. Can you tell if it's something recent or it has always been like that? I can't tell. My host has restricted me recently to 4GB RAM max (no swap), and the buildbot is failing now, but I don't know if using so much memory is something recent or not. Previously I could use up to 32GB of RAM. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmWc3Zlgi5GaxT1NAQKhGgP/U8f/NEk2WeNdEngasEDFxX1xSEzJMddo qIv7XkGXc93LNdGpqaIzNgW2d5NX3i7es0U5NrDtJVa0BTDLorKFN+zV6RpInZUO eQR65ZYn6Ld1xioyrb74v5vZq7HXcONhyVPcmXufRHkzkZ+kTnybvyc60plZEN5n NyHJkl7gNcU= =iNH7 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 06:19, Nick Coghlan wrote: Is it possible your buildbot is set up to run the bigmem tests? IIRC, those would work correctly with 32 GB, but die a horrible death with only 4 GB available. How can I check that?. I am seen multiple python processes, quite a few, each taking around 300MB of RAM. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmWhPZlgi5GaxT1NAQLkFAP/YBJ5owdNdl2yiJMc8kVi4Ndjt5WK5aRa DY24wZvQP/wY1gOjWKGceTm5Mkhds1Y3qWnP4nW8l1nQNxj+xAdqc5SUQcBHQRVo 5xtC+gQQ1HqDUS4FhAn+IgvlXtnoT0cTfgRO2G7k0ti89KN79aCR+q52TSOy0VCW 1Spv9ilP1Rk= =Ffmz -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 06:46, Nick Coghlan wrote: The server actually looks it may be in a generally unhappy state, perhaps due to previous builds that failed without cleaning up after themselves properly. How many python processes do you see hanging around? Just now: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 4340 buildbot 366M 344M sleep10 0:11:23 0.0% python/2 10097 buildbot 366M 8096K sleep 250 0:00:00 0.0% python/1 10099 buildbot 366M 8100K sleep 250 0:00:00 0.0% python/1 10098 buildbot 366M 8108K sleep 260 0:00:00 0.0% python/1 27698 buildbot 251M 5244K sleep10 0:00:00 0.0% python/1 27697 buildbot 251M 11M sleep10 0:00:00 0.0% python/1 27695 buildbot 251M 5852K sleep10 0:00:00 0.0% python/1 27694 buildbot 251M 5844K sleep10 0:00:00 0.0% python/1 27696 buildbot 251M 5884K sleep10 0:00:00 0.0% python/1 27693 buildbot 251M 5964K sleep10 0:00:00 0.0% python/1 9893 buildbot 202M 198M sleep11 0:09:32 0.0% python/2 14538 buildbot 200M 4700K sleep11 0:00:00 0.0% python/1 25971 buildbot 194M 189M sleep 100 0:11:22 0.0% python/2 2616 buildbot 120M 114M sleep10 0:06:38 0.0% python/47 11204 buildbot 118M 5612K sleep10 0:00:00 0.0% python/2 ZONEIDNPROC SWAP RSS MEMORY TIME CPU ZONE 23 56 4073M 1632M40% 0:39:38 0.0% pythonbuildbot.uk.openindiana.org This particular build seems to have hang, usual result of running out of memory. Note the SWAP usage of 4073MB, when my limit seems to be 4096MB. The buildbot master process will kill this hang processes after the usual timeout. I have requested raising my memory limit to my host, with no effect so far. Anyway, eating 4GB of RAM seems quite overkill. Doing a make test manually I can see the python process doing the test to eat more than 200MB of RAM, but it only launch a python process, not a handful like the regular buildbot. I have verified that the memory use is atribuible to the buildbot, since if I kill the buildbot processes, my RAM+SWAP usage is negligible. Thanking for helping me with this. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmWorplgi5GaxT1NAQIb7QP/Y/Mr0RhhRTM1Rld7xKqNi77tcB0+p4CX EZ0fViNr/NF6NibKMzowi0pr42iZ3dXN4/yRQgNsvGhfzTrpi+J3Z1GCg5vnqox3 jOC+DQ5IrZylLV+zH46K9j2UJ+4hvU3PWBZcGAt6iB4EVK1h8mvBBW08VeDoN5Cj Nkqth694BcY= =KAwa -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 06:59, Jesus Cea wrote: Thanking for helping me with this. BTW, it is 7AM in Spain now. I am going bed. I will check this thread again tomorrow. Thanks for your time and effort. This is very frustrating, moreover because it was working very well (with 32GB of RAM... :-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmWpVZlgi5GaxT1NAQIz/wP5AYXGp6DYf0Fpl0tNHx8sLNJXR8XSQFjf YRoUvmo1Sh60eMU7yGsoyT2wvOTzU4rPgaWoFsaUELS/74rLMcmb567kKAJqpH7X 8BNmNSdRxYxMXixUrrwi25rYTEgz4ZenpV8tjkHR+wHhcCbBvKnDxcliJZkAxDAJ mzlhdQvdPgI= =9wQO -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 07:02, Jesus Cea wrote: On 06/09/11 06:59, Jesus Cea wrote: Thanking for helping me with this. BTW, it is 7AM in Spain now. I am going bed. I will check this thread again tomorrow. Thanks for your time and effort. This is very frustrating, moreover because it was working very well (with 32GB of RAM... :-). I just deleted all the build directories and restarted the buildbots. Forcing a build now. Bedtime. Good night. At this moment, I have 3 Python processes, of sizes 230, 160 and 130 MB. And growing. Sleeping... Z... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmWtWJlgi5GaxT1NAQJ0uAQAhmOiXf6lxZeqiRldZcYvYXxnBDw4wNKJ ulADNvqJY7dxFPvuUZ8gv9zQcBjs+xTcY3IkDL4ZlSvubMZeR0O7mQ09zvBKXezd PI6vIK59PPeY+Znfw29TCDB8x5As2wqLVh388eLlYyJFsuUiZfOr4KuCwRughDns cJ7XJ4lb2+c= =oRzC -END PGP SIGNATURE- ___ 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
[Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A single instance of buildbot in the OpenIndiana buildbot is eating 1.4GB of RAM and 3.8GB of SWAP and growing. The build hangs or die with a out of memory error, eventually. This is 100% reproducible. Everytime I force a build thru the buildbot control page, I see this: takes huge memory and dies with an out of memory or hangs. I am allocating 4GB to the buildbots. I think this is not normal. I am the only one seen such a memory usage?. I haven't changed anything in my buildbots for months... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmD81plgi5GaxT1NAQJIfQP+LvxG8jGDcfdsKB3omkM8fE/pA3q3yVQL qVtSPQomCNB3hhhctEXnSFmDDekOTroCTpU9lYp6c9ZLmSCEGJx7bVW/53hk9ZJv oMNwSHvQbrZy/eWuJAlSUqIl2oAmMP75RiDhL2eqBu/alhavK8oXCeDV7iG9EvZq 0RH9Weqr788= =3jyf -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/11 17:57, Jesus Cea wrote: The build hangs or die with a out of memory error, eventually. A simple make test with python not compiled with pydebug and skipping all the optional tests (like zip64) is taking up to 300MB of RAM. Python 2.7 branch, current tip. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTmEYIZlgi5GaxT1NAQK79gP/aRyMqgEE7uScYtrZzPqs0ZSpGnVM8sBi RbNEN3cB/s6Oe/UVIo4vinaDnXXYSOM5qtqghUl5Cnx+wiiK2cL8iIv/YzZbjT9s U8QELEkol8lpjAVPEO/rSylZ5kvsmdjkM2mU6NOwiLGw+mmbbgqpmdAU14p+sqSO 2xFJElgOHuM= =YA0J -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 - default): Correctly merging #9319 into 3.3?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If a patch in 3.2 is not applicable in 3.3, a null merge should be done. If not, next developer tring to merge will find some other unrelated code to merge, and she doesn't have the context knowledge to know what to do :-). In this case, I merged code that doesn't actually compile, breaking the build for 20 minutes :-). And yes, I fully realized that I should try to compile locally first. Dealing with this unexpected merge when merging my own patch was... unexpected, and the code seemed sensible enough. Do we have some hat-of-shame I should wear because breaking the build? :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCUAwUBTbTgpplgi5GaxT1NAQJqegP3QSVIf6yszZrFJEgKTaK4XXvHB965PdYN T9g8bx5IKXmiMjDBCatjuA2AAtwnL0Wd2Dw0tnGhRTqYHD2l+cMcFw/2JtV4L6sC c0fKm2o+V8gSW7KZwdvgNWiQlzE3lp2DiD/ng3gM3JlK/EKghIH8acDiJsHHrQtS 7T7iSLllOw== =+50u -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Drop OS/2 and VMS support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/04/11 22:48, Antoine Pitrou wrote: On Tue, 19 Apr 2011 15:20:13 -0400 Doug Hellmann doug.hellm...@gmail.com wrote: Victor, if you want to post the call for support to Python Insider, let me know off list and I will set you up with access. Doesn't it have more chances of succeeding if posted to comp.lang.python, simply? I think Python Insider point was to translate to general public relevant python-dev discussions. This is a perfect example. +1 to include deprecation warnings/errors in 3.3 and remove in 3.4, according to PEP11. A heads-up warning and request for help in Python Insider is the way to go, too. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTbTk0Jlgi5GaxT1NAQJyGAP8CnKuJyOh0pidU/Y4xlE4oSqQzwbVIqYA +Pd95c+oWDf8cRGkc8U/4APHOruyX1YYUpQL9WTlf3NzyoBv0f7JvzQRgc9eKDaj IGU79VhDKEShTB49saPTsUCpIcaQ8bUTeAjXLv67ga44WQ0toghez7dWVJ8iWh6+ R+w/4tK6aRM= =MBBZ -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Test Force Build on custom buildbots
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/03/11 18:27, Antoine Pitrou wrote: On Wed, 30 Mar 2011 18:11:53 +0200 Victor Stinner victor.stin...@haypocalc.com wrote: Le mercredi 30 mars 2011 à 17:59 +0200, Victor Stinner a écrit : I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues. Oh, I forgot something: there is an error on hg purge. [...] It's not an error, it falls back on another purging method when the purge extension is not enabled. I guess you are talking about http://mercurial.selenic.com/wiki/PurgeExtension. Do you want me to activate this extension in my buildbots? (OpenIndiana machine). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTbTpjZlgi5GaxT1NAQKVfwP9FwD50nnoIErTpigrG8W/7ds1kWQz3C02 4qwt7P5jQ9mbXImIbmh0TKNjJJg0zsp+QR/3cZZRkg67R0Walu9glbXlcp9mDeWZ qU3SuiRQ4vNq+lcXdEK0dXSXYxGMHaIgd+PYxaBaQzdDkG8Cgct/uYZO2157UuMd 45KKejJuUB8= =csNj -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Issue 11715: building Python from source on multiarch Debian/Ubuntu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/04/11 00:37, Nick Coghlan wrote: However, the combination of running on Ubuntu 11.04+ and need to build security patched version of old Python seems unlikely. Well, I, for one, have Python 2.3, 2.4, 2.5, 2.6, 2.7, 3.1 and 3.2 installed in my machine (Ubuntu 10.04) because I need to support code spanning such a range of python versions. I remember that compiling 2.3 or 2.4 was a bit painful. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTbTqSJlgi5GaxT1NAQJdBwP/fVcqmac2gF/rPLYJvrwRKC7JqlmogRuQ h9Wp97Ihl430aeESjIuzLPCdfBxEWj14f6bP2GHOanncOXaNOLisA2Oktl5I92Dc Iw0lWPjWuEuDb1zkvALFB312Ecu0icBSCtScVRHHTeppC+ucpzuu/+eNXN+tCJ31 eWlNQcZR1qQ= =oQ1k -END PGP SIGNATURE- ___ 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
[Python-Dev] http://docs.python.org/py3k/ pointing to 2.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://docs.python.org/py3k/ takes you to 2.7, by default. Should we update it to point to 3.2?. If the point is to promote Python 3... I would point it to 3.2, with a big access to documentation to legacy 2.7 (beside the small left column link). What do you think?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTagtY5lgi5GaxT1NAQKCigP/YwAMrqyQglgJa85rXBQrFVdvHPcNASab Fw7PWTMdg7Hxof/cXn9gsdiR3fGqVrRv9G5V64hxi6WN5aVbXDyAMJzxsCEAtPfW PkRDvdZKsKD1xgxLKIZo1gUCY80Xqrts+kXRJKGtA/TeXzmqhhknHQyHW0oiYK3t jL9qRKGxVO0= =gFw7 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] I am now lost - committed, pulled, merged, what is collapse?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/03/11 19:59, Raymond Hettinger wrote: I think if we're going to require a complex workflow, then we're going to have to expect a lot of questions. And those questions shouldn't be brushed-off with go read the tutorial, we have no time for you or words to that effect. I think we are doing some antipatterns with our current approach, battling the tools instead of joining them. Would be nice to document a complete case workflow, from patch thinking to the final push, dealing with all the little details, collapsing outgoing commits, +1 head, merging real conflicts, linealizing history, moving the patch thru branches, etc. But the fact is that some of us are still experimenting. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYX64Jlgi5GaxT1NAQLaXwQAhtZyuIZ1wYXx7yS41+bzIpZHEMbj3uCN iA/OzE1cAY55/opNHqIu1OAONKD/Y4kAm6cU/Qs2prRL2OsMwml1zPsG2Aono2iN SIqAN1YS7fagOEcDeKmPo6LbHTBpq9wuv53LBiW7xM1/ut2e5ou9DMfpf5bK6xP6 bbR4ESTGzyU= =NNNV -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18/03/11 01:01, Larry Hastings wrote: In 2.7.1 PyCObject_FromVoidPtr() now calls PyErr_WarnPy3k(). This means it's been promoted to throwing DeprecationWarning! But that's also guarded with Py_Py3kWarningFlag so it's not active unless you ask for that too (as with -3 on the command-line, etc). I kind of remember doing this change myself. Since no 2.8 is planned, it seemed sensible to mark PyCObject as a py3k warning. PS: I am the maintainer of (externally developed lib) bsddb, but the 2.7.0 behaviour actually broke some other extensions out there (when used with warnings active). Details in the tracker, somewhere. I am offline now, can't use the browser. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYOiYplgi5GaxT1NAQLtRgQAjdB1yvFmqJLGqqzEaCK+ll5jx277b751 RGshITBFUkd+OLVErP9nEKUMsHvr/nl7BIjhZotKH31g6Hl0KiuGPHHkPNKYGs4y 5XsHaZ2a9/qkgt1wa12gLsHmxsrIICGKPzcPUQs6GVJGBuppGtDkc18iODOCd6eC kkDcc/sFHUI= =mXiX -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/03/11 03:14, Nick Coghlan wrote: What may actually be better for buildbot experimentation purposes is to allow us to request running a build-and-test cycle from branches in *any* of the repositories hosted on hg.python.org, rather than having to push experimental changes to the main line of development. (i.e. start moving towards more of a style of development where code doesn't land in the main repository until it has been vetted by the buildbots *first*). This is a good suggestion. I kind of remember that when working in SVN you could request a particular build from a particular branch. If that was true, we should consider something similar with mercurial. I am offline and can't check, thought. In fact I am thinking about being able to push a patch to the buildbots and, if the patch applies cleanly to the branch tip, actually apply it, build test. That would be amazing, security aside :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYQhWJlgi5GaxT1NAQJ23AP/dn2lqXgxeoYgsAZklkDR2hLqHJzYs8PT Y38sGpeUdDmJQ/k+vISUtlNsshLRDc7o88cL95wy1j10QNPSL43ehfz3+W6anAvB 6ELpvTePT/0rJzTcWQVgXSwAu50am4z9rcV7r2Q7EluLCKg3azXcARoCMFSZ/8Wp vMgbAGe3pwk= =5LvY -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 06:14, R. David Murray wrote: The fun part comes if there are changesets. At this point there are two options: go through each of the branches doing an up/merge/ci, and then pull/push. Or, what I actually do: hg log hg strip the changeset id of my first checkin Then I start from the top of the section above, but starting by reapplying my temp.patch. There's one other detail, though: because I'm using share, the checkouts lose their parent id when I do the strip. So in each checkout I also need to do 'hg debugsetparent branch' before doing the hg up. Clearly, this procedure is not for everyone Clearly not :). So you do a hg strip and start over again. The problem with this is that your patch will be applied on top of the incoming changeset, and your merge will merge that patch too, if the original pusher haven't done it yet. Tonight I was thinking about doing a merge inside the branch, to solve the +1 branch. Something like transforming: branch 3.2 -My patchincoming patch--- branch 3.x -- to +--+ | | | v branch 3.2 -My patchincoming patch---merge--- | V branch 3.x merge So I merge my patch to the other branches, preserving history and keeping only a single head in the 3.2 branch, that the other developer must merge to 3.x. The bad thing about this is that the new head (the merge) will be assigned to me, but the developer that must merge that head to 3.x is the other guy. The other committer could merge her changeset to 3.x and, if my merge between the two heads is not trivial, she must notice it and do a second merge. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYIAJplgi5GaxT1NAQJ+XAP+On4tEhylQ7gxtTsfnBNKVG4sLwR697cw GneD9Mi79cEGN5ANjkfflhUkd9kwrPgpkPjzLOXUHU1t7w5ozrWYkRpPHRM44rPA 7VL/Mm6/OMhYehnebwiCriEu6CcUBUFAQMC8BfOdaUb3EQsGFqhZkH9sHepOg+MQ ggSv5OGblic= =h7q8 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 13:35, Jesus Cea wrote: Tonight I was thinking about doing a merge inside the branch, to solve the +1 branch. Something like transforming: Another thing I was thinking about tonight was... dropping the +1 head banning. Embrace it. Embrace the mercurial way completely. Each developer is responsible of merging HIS heads. If somebody forgets, nothing wrong will happens. And no patch is left behind, because you can see unmerged patches with hg heads, and bug their owners. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYIBiplgi5GaxT1NAQLVhQP7Bidj3q+e3LqSWHFR3mcDON1HatygPniQ e1Y0bNdeUlk3V0sNG9LQcCNIsd475UrwOJOGTvbaLOP4zaXUrNX9x9cIbhOsD9NA nF8rwDQGucTRHEC8TonG/rGwuOcnFR704ttHU6z0+P/+3lA7/xpl3KL7bK9L/3dS g3ZZ6LTN8Z8= =kfVk -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Solaris family and 64 bits compiling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/11/10 13:19, Jesus Cea wrote: Would be acceptable to change something like: add_library_path(/usr/local/lib) to something similar to: if (platform.uname()==SunOS) and (platform.architecture()[0]==64bits) : add_library_path(/usr/local/lib/64) else : add_library_path(/usr/local/lib) python-dev would consider that change OK?. Resurrecting an old thread. I think that, under SunOS and 64 bits, python should install the lib directory under /usr/local/lib/64, following the convention in the platform. In fact, under OpenIndiana 147, I see this: - -bash-4.0$ type python python is /usr/bin/python - -bash-4.0$ ldd /usr/bin/python libpython2.6.so.1.0 = /usr/lib/libpython2.6.so.1.0 libc.so.1 = /usr/lib/libc.so.1 libdl.so.1 =/lib/libdl.so.1 libm.so.2 = /lib/libm.so.2 - -bash-4.0$ file /usr/bin/python /usr/bin/python:ELF 32-bit LSB executable 80386 Version 1 [FPU], dynamically linked, not stripped, no debugging information available - -bash-4.0$ ls -lA /usr/lib/|grep python lrwxrwxrwx 1 root root 19 Oct 1 10:55 libpython2.6.so - libpython2.6.so.1.0 - -rwxr-xr-x 1 root bin 1788896 Oct 1 10:55 libpython2.6.so.1.0 lrwxrwxrwx 1 root root 22 Oct 1 10:55 libpython2.6_db.so - libpython2.6_db.so.1.0 - -rwxr-xr-x 1 root bin 10372 Oct 1 10:55 libpython2.6_db.so.1.0 drwxr-xr-x 25 root bin 432 Oct 1 10:55 python2.6 - -bash-4.0$ ls -lA /usr/lib/64/|grep python lrwxrwxrwx 1 root root 19 Oct 1 10:55 libpython2.6.so - libpython2.6.so.1.0 - -rwxr-xr-x 1 root bin 2217504 Oct 1 10:55 libpython2.6.so.1.0 lrwxrwxrwx 1 root root 22 Oct 1 10:55 libpython2.6_db.so - libpython2.6_db.so.1.0 - -rwxr-xr-x 1 root bin 13336 Oct 1 10:55 libpython2.6_db.so.1.0 - -bash-4.0$ file /usr/lib/64/libpython2.6.so.1.0 /usr/lib/64/libpython2.6.so.1.0:ELF 64-bit LSB dynamic lib AMD64 Version 1 [SSE2 SSE CMOV], dynamically linked, not stripped, no debugging information available - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYIGSJlgi5GaxT1NAQIrGAP/fBcLKIdFN+O8jNArCs01m30pQC5rNAhp hs1mTqlllpGkSQLDeQvcN/ctwFpR8a+mlC4yCFwYFB8CpB9TjilIKRn0RlerfOlw U0OuhezPTGc75NY95a+x8iZG4FQYytMkv7ClPmyDjG/g68CTS/zArRoKGRA7trZk +WbsLPK4lhg= =ScvG -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 14:10, Brian Curtin wrote: On Thu, Mar 17, 2011 at 07:41, Jesus Cea j...@jcea.es mailto:j...@jcea.es wrote: [..] Each developer is responsible of merging HIS heads. If somebody forgets, nothing wrong will happens. And no patch is left behind, because you can see unmerged patches with hg heads, and bug their owners. That just makes more work. 1. I, being new to hg, might not realize my error and just think I'm done. I move on with life. 2. Someone has to notice the additional head then contact me. 3. Now I have to go back and figure out not only what I did wrong, but what I have to do to correct it. But thinking that you are done is already a problem now, and everybody must deal with your unmerged head doing whatever trick to keep your head apart and don't merge it automatically. That is burdensome and error prone. I would guess that most people would merge your head themselves, just for convenience. And that would not be your plan if, for instance, your patch is being tested/half done/whatever. Allowing multiple heads, your patch is still there, but nobody suffers for it. If fact, if you don't care, your patch will sit out of the tip line and will be not actually integrated in the tip code. So you must merge it, but nobody has to pay any price just because you forgot :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYIMk5lgi5GaxT1NAQJPaAP/fJv2IKHQycxyfg4xkZaqQe/VbxrpfAeV l4Q6nQKYXKCFyTGrlh0Hx6Kb8lkdR+H1KOGWQ7tZVDITLvnK4YBYXj6Be4Uoddn8 H/zsJYAHz1rGKmkq1erY5+ejZpQ2BhUnPqz20yomACG/hUCXH+KI7kf5yqZ27fTx 5c/all+SNNg= =XNMs -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 14:45, R. David Murray wrote: Not if the cpython repo is in a fully merged stated. And if it isn't, I will wait until it is. (The update notifications on the IRC channel help with monitoring this.) That is repository serialization. The point of HG is to avoid that :-). Moreover, you are supposing that the original committer will merge soon. If you leave an unmerged changeset in 3.2, I would consider that to be leaving the repo in a weird state. I do agree. But there is nothing enforcing it (push hooks), except social pressure. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYJaTZlgi5GaxT1NAQJTmgP+IUCRioVAgSEjXtuufj3T6Vl1Q9XQCHej 4R+RTHeojTleWui3W013tS8cmQMa3Y8RSYh5G60kwhSZmdligRcDHWOzuTkemYol QEv5DDx5dAK/n6XoRA4VWFkVWlw9ZQ8TiiQtvd8h5xiCSxFVTq9NB/LHCQTNzQrW et/jGUvlkOI= =oTMp -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 16:04, Guido van Rossum wrote: I don't want to be alarmist and I don't want to start another moratorium, but I do think that we need to be aware of people coming in sideways into Python 3 and missing the nice deprecations. So let's be conservative with deprecations in the Python 3 line for now. I can see the motivation for this. I would suggest to keep deprecating things in 3.x, BUT keeping the deprecated stuff around (maybe reimplementing them using the new stuff) until we decide is safe to axe it, instead of the regular 3.x deprecates, 3.(x+1) cleans up. In this way we can keep the improvements, while not leaving people just migrating from 2.7 behind. The problem will be to decide when to do the cleanup... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYJcQplgi5GaxT1NAQIeawQAgC3kpmS8RoYoeRn6BRFKTOSEKc6edafY NVKDZ+NAZzTeYqJcr0symc+9A+5J92fJQq2n6tz1/K2yAzS/m1dudAXK7YIb1Ldc EwX8JB2osvCgGM5PFefhGOLZ0VrrlWnHQTEviU5GilGNHzCcbEgNj/3BPnEyCNyv QPmlcyeN+eQ= =xidU -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] hooks: Add roundup integration hook.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/03/11 22:16, Georg Brandl wrote: But in any case, by popular demand fix is now removed, and only close and its variants actually closes the issue -- since there is not much chance that you can write close #12345 without actually meaning to close the issue :) Sorry to bother you. What would be the exact wording?. What variants means?. Yesterday I committed a changeset with a commit message of Close issue #8600: test_gdb failures because innocuous warnings, and it didn't automatically close the issue :). Sorry for being so picky ;-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYDJ2plgi5GaxT1NAQJ7WQQAl0gM0F4GPdY0O3K2qH4/GJc8fqDx6pRJ rz4DwVbYRZes3JCwWNCYvK7tJ3B2c39RLi6f4yL5xVP2MDdYT3fu4uBUaSky4a7x jevns2KraRJVxQbkqwn0agV6CyDhKoffOzHKDg20k1Q+R0/JX3cwrQGDB9QtJuMR xkIgbhZloF4= =syPU -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] public visibility of python-dev decisions before it's too late
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/03/11 22:16, Georg Brandl wrote: But in any case, by popular demand fix is now removed, and only close and its variants actually closes the issue -- since there is not much chance that you can write close #12345 without actually meaning to close the issue :) Sorry to bother you. What would be the exact wording?. What variants means?. Yesterday I committed a changeset with a commit message of Close issue #8600: test_gdb failures because innocuous warnings, and it didn't automatically close the issue :). Sorry for being so picky ;-). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYDMNZlgi5GaxT1NAQL3bAP/aey6/n0Hx59PsOW0t6v0+eOBcWGZ4r6R 20pvuYa2GJ4GUd6rTcOmIXBdwyfLe9K2r+2hYkSbn4Xg2RrAltXnPEhFuSOKRYfD /v5S4YuwGa3QL7uiKe5qUn7u91KJzLb3vlAqq0TCzJxwLvZq5YeTB1iSXOZ3NoM8 xx/+mHpcUHI= =eDnU -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] public visibility of python-dev decisions before it's too late
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/03/11 16:01, Lennart Regebro wrote: Python 2.6's API wasn't removed in 2.7. It remains available. But not in 3.2. And the new API appeared in 2.7. That is a deprecation period of seven and a half months. I strongly opposed CObject deprecation in 2.7, as you can see in http://bugs.python.org/issue9675 and mailing list archives. In (external module) pybsddb http://www.jcea.es/programacion/pybsddb.htm I support Python 2.3, 2.4, 2.5, 2.6, 2.7, 3.1, 3.2 and 3.x. Having to deal with CObject/Capsule was an undesired pain, but the actual support has been painless. What problems are you finding trying to support both CObject and Capsule?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYDNvplgi5GaxT1NAQIZ+gP8Dtv1EBIUTYYujlY/QcjmmyY+rdXwgZq6 tSJnHsonvaBkG34yY+YM/jw54wA0GFRApvHNtXo6r1AS0Gwei6+Ypb5iGGxdsWmB SdaZhhcEfmaP1u+5Jaq9P3Nco9LfhgxC3ahT/M8uYsGzpC6U4zgh3yjIY08Y1MAp h5cRmF2L6CI= =8MSH -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] public visibility of python-dev decisions before it's too late (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/11 22:50, Guido van Rossum wrote: I propose we try to find an embedded blogger who participates in python-dev but is focused on making regular blog posts about the interesting tidbits. There's no requirement to be complete (which I think always weighed the python-dev-summaries task down). Ditto for python-ideas -- it would be nice if it was the same person but doesn't have to be. This might be an opportunity for increasing diversity. +1. I would love to see this. Too bad I don't have the time myself to keep up with python-dev python-ideas... Forwarding the request to python-es mailing list. Crossing fingers. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYDSJZlgi5GaxT1NAQIEvwP+MWHZbY+xMhl27K7hC2fPH7QJsz55H0Xb 7FIWSApqdJXL5Uzu+VbGN4IKK7GBCGHXS8t/vTOXcePeqZRnTGIgxVth8NnxcK3M O9+VJIyGaqMghb0BEgSaaryfiZNfbI0mKwAouzgzQsvP2uyX/kzCHQCnxdDsNTWo mxLbKVicaRw= =aA2c -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Python3 regret about deleting list.sort(cmp=...)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/03/11 13:14, Paul Moore wrote: None of my real code is affected either way, but it seems to me that the removal of the comparison function option was (sadly) a case of purity being allowed to beat practicality. Luckily, adding it back wouldn't be a backward compatibility issue :-) Whether it's worth doing, I'll leave to those who would be doing the work to judge... I would +1 to reintroducing cmp. Mapping my mental cmp to a key is something I must think about everyday. When I have a 200 element list, I don't mind about the O(nlog(n)) nature of cmp, instead of O(n) of key. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYDhJJlgi5GaxT1NAQKcXQP+IX5bSb3aSNsfzu/vjNY41CNI/1CJ+r3q vxPbi7ut1ZvXVyiMo2b+jVC1rxNVitf0pQXyQ4skv9Tiq3+L8eYbOts7hbmDB7Aw sNPWYuvjLmTrX2lsgdQyjbiVK0lHJjzYn8+pvKqy7Tt47+sNiL/07FmM6CHj2fiU N/vspNCa6rs= =Zc90 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Useful page in the Hg book
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 02:39, Nick Coghlan wrote: On Wed, Mar 16, 2011 at 7:09 PM, Nick Coghlan ncogh...@gmail.com wrote: As I'm sure there will be plenty of erring as we get used to Hg: http://hgbook.red-bean.com/read/finding-and-fixing-mistakes.html For simple cases of attempting to push a single commit that gets rejected by the server, hg rollback/hg pull/hg commit/hg push/ may provide a cleaner history than doing a dummy merge. Having tried this, I advise against anyone else trying it. I seem to have got my local repo into a state where it thinks I have already merged something from 3.2 to default when I really haven't. The good thing about dummy merges is that you do the merge in your local clone, and if you don't like it you can do a revert or a rollback. That way, it is risk free and you can experiment locally before pushing. Since rebase is in HG core these days, I am getting comfy with hg pull - --rebase. But I find rewriting history too scary when merging between branches and complicated changeset graphs. I want to be able to drop a bad conflict merging and try again, in a safe way. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYGBMJlgi5GaxT1NAQIl2wQAllNQiQfjHygDDoGEGm+9wUAxtaGLvSkB na/MmFTgXSXn4og7K5JVmTesc1KXHJjF+a3Kb2oDu9A3IRbjipEIc4qWpnwTlPBW skmAMXhwLR+Y9y+nXo2ry9R71SvIa7u1RGihrPWBnnIHzlgWKPwr93BPdYygSb4g uQJ4QGIVudU= =LSJh -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 00:20, Antoine Pitrou wrote: That's not my experience. Often, when the resolution on other branches is deferred, it means the committer has actually forgotten about it. I agree with this impression. Personally when I have a pending branch, I keep a firefox tab open in the issue, as a reminder. It bugs me a lot. And that is the point. Most of the time, I push all the changesets for all branches in a single operation. The (mainly) only time I could push a single branch is if I want to try the patch in the buildbots first, before applying to all relevant branches. And I try to avoid it, because I know some other people are going to have issues when doing their own merges trying not to merge my changeset themselves, specially newbies (the +1 head thing). I agree that half the changesets are merges now. But that is an artifact of our commit culture (create a patch, commit inmediatelly). Another approach would be to spend some time writing patches, committing locally and doing a giant merge push at the end of the week :-). (DIGRESS: If buildbots could download test a remote arbitrary HG repository, it would be a big improvement for this, and a galaxy-size security hazard :-p... Although now any pusher can break-in any buildbot machine simply pushing some ugly test code, of modified configure script. Uhm... Maybe a wiki about how to set up a chroot buildslave would be something to think about... Any info about this?) The good thing about merging so frequently is that mergin is easy, painless and every committer must go thru it for her own patches, instead of putting that responsability on somebody else. hg log can be a bit unusual for us, but pretty moot. we are getting used to it, yet. No forgeting up-porting changesets is a massive improvement with the late svnmerge practice (nobody cared about automatic merging, but merging by hand anyway, cherrypicking revisions). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYGG55lgi5GaxT1NAQLEDwP+L3AsqeXMpgEOKJFW6gqs0ahjbqF61Ao5 zThKWqXQoAyDm+21bT8aJR3Ogrix+dI37PrTRa6B8L+S2tDh3PdG984tOUOsGUvp KNa+GSNai1OotfLUebBhCvGlPAapQnWK9xoELYjO8Lo7YTkfWspXGv5e3exIQQJp AmunpKy1I3U= =gS+8 -END PGP SIGNATURE- ___ 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
Re: [Python-Dev] Hg: inter-branch workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/11 04:41, R. David Murray wrote: Dealing with a null merge when someone else has committed between the time I started the merge dance (I always pull just before I start that) and the time I push is not that hard either. It pretty much amounts to having to do an additional set of merges. (In my case I do a strip and restart my merge dance, but I'm not sure I should recommend that since altering history is considered dangerous :). Could you possibly describe your current approach, marking it with a huge NOT SAFE; AT YOUR OWN RISK banner?. I wonders how other people manage this. I too do a pull before doing the merge, but I don't push each merge separatelly but I do the all the merges locally and then do an unique push. Than can take some time, moreover if I run the complete testsuite in all changed branches. Resolving a +1 head here is tricky, if I *WANT* the other developer to manage her own merging by herself. As it should. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTYGJ65lgi5GaxT1NAQII3wP/fiHkDs5xFP9hK/3tWxFSrovdSoOOTzKT py7J2P1Ys1nQAw9ylfDiq6oFPGuc22pSqBrO2MgLlGs1a5i9XBSDhA6yCvRW6i4C CoPMmVXigEeZXpEBGpYWtjSO7pIvPQxPCjMH6zlHWwD+jg6RhqBQrz/yacKQdNzw 7auugDVYyD0= =uAdh -END PGP SIGNATURE- ___ 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
