[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 @prope

[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

[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

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

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 launchin

Re: [Python-Dev] OpenIndiana and Solaris support

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 th

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 m

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

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 h

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 : >> 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

[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 _/_/

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/b

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

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 ab

Re: [Python-Dev] mUTF-7 support?

I think the consensus so far is that this is a good idea. I just opened . Thanks for your feedback. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea

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 y

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 : >>> 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 do

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 : >> 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

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 clien

[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.

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

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 coope

[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=

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.

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 contex

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

[Python-Dev] sys.intern should work on bytes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 """ sys.intern(b'12121212') Traceback (most recent call last): File "", line 1, in TypeError: must be str, not bytes """ I wonder why. - -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/

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 > a

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 wrote: >> >> It is intrusive. Yes. I think it must be, by its own nature. >> Probably room for improvement and code transparency. But.

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/1

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 s

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

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

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,

[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

[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: <

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/

Re: [Python-Dev] Offtopic: OpenID Providers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/13 20:45, Eli Bendersky wrote: > PS: I use "http://www.jcea.es/"; as my OpenID identity, and I > delegate the actual service to "myOpenID". I can switch delegation > trivially. > > http://bugs.python.org/?@action=openid_login&provider=Google

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ó

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

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

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 sys

[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 d

[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 t

[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

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

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

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 Ce

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 ef

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 : >> Any suggestion about how to solve this? > > Easy solutions include somehow removing the dependence on > subprocess or moving the import of subprocess into the fu

[Python-Dev] Bootstrap issue: "select" is compiled "too late"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The relevant part: """ ranlib libpython2.7.a gcc -o python \ Modules/python.o \ libpython2.7.a -l

[Python-Dev] HTTPS repositories failing when using selfsigned certs

repository (<http://hg.jcea.es/cpython-2011>), I get an error: "('invalid token', 97)". - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es -

Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 -> default): MERGE: Better test for Issue #15402: Add a __sizeof__ method to struct.Struct

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 fac

Re: [Python-Dev] Doc/ACKS and Misc/ACKS

>> (*) I think perhaps Éric already proposed it at some point >> > > +1 +1 too. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _

Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 -> default): MERGE: Better test for Issue #15402: Add a __sizeof__ method to struct.Struct

sertGreater(sys.getsizeof(struct.Struct('1234B')), + >> sys.getsizeof(struct.Struct('123B'))) >> >> def test_main(): run_unittest(StructTest) >> >> -- Repository URL: http://hg.python.org/cpython >> >>

[Python-Dev] Adding GNU conditional execution in the Makefile?

cope with this difficulty... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/

Re: [Python-Dev] Long term development external named branches and periodic merges from python

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?

Re: [Python-Dev] Long term development external named branches and periodic merges from python

nch, 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 me

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

Re: [Python-Dev] Long term development external named branches and periodic merges from python

ed 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",

[Python-Dev] webmas...@python.org address not working

Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table """ - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/

[Python-Dev] 404 in (important) documentation in www.python.org and contributor agreement

://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. -

[Python-Dev] Long term development external named branches and periodic merges from python

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?. T

Re: [Python-Dev] Merging 3.2 to 3.3 is messy because "Misc/NEWS"

d 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/ _/_/_/_/ _/_/_/

Re: [Python-Dev] Merging 3.2 to 3.3 is messy because "Misc/NEWS"

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/ _/_/_/_/ _/_/

[Python-Dev] Merging 3.2 to 3.3 is messy because "Misc/NEWS"

tead 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 -

[Python-Dev] Do we have interest in a clang buildbot?

. What do you think? - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org

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

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

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 _/_/ _

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

B of swap activated a few minutes ago. Thanks, Jon and Alastair :-) (OpenIndiana guys). Launching buildbots now and crossing fingers... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

B of swap activated a few minutes ago. Thanks, Jon and Alastair :-) (OpenIndiana guys). Launching buildbots now and crossing fingers... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

ack!. Sorry for wasting your time with these mundane details... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ .

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

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 s

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 a

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 work

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

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

Re: [Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

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...@j

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 wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 02/09/11 17:57, Jesus Cea wrote: >>> The build hangs or di

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

[Python-Dev] Multigigabyte memory usage in the OpenIndiana Buildbot

e 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.

Re: [Python-Dev] Issue 11715: building Python from source on multiarch Debian/Ubuntu

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...@jc

Re: [Python-Dev] Test "Force Build" on custom buildbots

t;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.

Re: [Python-Dev] Drop OS/2 and VMS support?

rors 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

Re: [Python-Dev] [Python-checkins] cpython (merge 3.2 -> default): Correctly merging #9319 into 3.3?

at-of-shame I should wear because breaking the build? :). - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber /

[Python-Dev] http://docs.python.org/py3k/ pointing to 2.7

olumn link). What do you think?. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@

[Python-Dev] Proposal for Python 3.3: dependence injection

be "socket-like", but how much "socket-like" in the API sense?. Do you need to implement "getpeername()" for injecting in smtplib?. If you agree that this is a nice idea, what other libs do you think that could benefice of being "injected", beside "socke

Re: [Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost - committed, pulled, merged, what is "collapse"?)

ature or bug you're trying to land might be > enough. Would be amazing if the test system could detect which files were changed and only do the tests that cover them. Not a 100% safety net, provided by the full test suite, but not a bad star

Re: [Python-Dev] Workflow proposal

or a buildbot cycle. Also, you have to deal with whatever problem you have during the merge yourself (for instance, the API changed and the merge is not trivial), when this work should be done by the original committer. - -- Jesus Cea Avion _/_/ _/_/_/_/_/

Re: [Python-Dev] Python 3.3 release schedule posted

like a year ago. Somebody else said he was planning a PEP... not done yet, I guess. Digging the archive: <http://mail.python.org/pipermail/python-dev/2010-April/099237.html> - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - h

Re: [Python-Dev] Workflow proposal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/03/11 18:38, Jesus Cea wrote: > Most of our problems are related to trying to keep a lineal history, and > races with pull-patch-commit-push cycle. I propose the following workflow. The points of my proposal are: 1. The hg.pyth

Re: [Python-Dev] Hg: inter-branch workflow

ce, "hg log --follow-first". We could have a trivial "push hook" to enforce that the current tip be the "left/first" parent for any merge. - -- Jesus Cea Avion _/_/

[Python-Dev] Workflow proposal

t, this sandbox could add your patch automatically to the assigned issue (bugs.python.org). We already have "cloned in the server" repositories, but I am not sure how to delete them, how to push them to the buildbots (is it efficient?, of the buildbots must pull the comple

Re: [Python-Dev] I am now lost - committed, pulled, merged, what is "collapse"?

ith 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 _/_/

Re: [Python-Dev] Hg: inter-branch workflow

ots 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/ _/_/_/_/

Re: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective

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/ _/_/

Re: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective

afe 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 _/_/ _/_

Re: [Python-Dev] Hg: inter-branch workflow

it (push hooks), except social pressure. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/

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 <mailto:j...@jcea.es>> wrote: [..] > Each developer is responsible of merging HIS heads. If somebody > "forgets", nothing wrong w

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: > > "&quo

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

  1   2   3   >