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
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
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
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 _/_/ _/_/_/_/_/_/
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
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
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
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
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 _/_/
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.
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
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
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
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
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
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
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
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
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
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
-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 -
-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 _/_/ _/_/_/_/_/_/
-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
-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.
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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.:
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
-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
',
97).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things
proposed it at some point
+1
+1 too.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
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
...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things are not so
.
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
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
-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
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
://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
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
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
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
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
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
.
What do you think?
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
fingers...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
fingers...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
) 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
-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
a VirtualMachine with the
required resources myself. Crossing fingers...
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
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
-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
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
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
-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
-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
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
-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
wear because breaking the build? :).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
. 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
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
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
). What do you think?.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
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
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
, 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
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
-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
-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
-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
pressure.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
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
;-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things
;-).
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/
. _/_/ _/_/_/_/ _/_/ _/_/
Things
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
-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
)) nature of cmp, instead of
O(n) of key.
- --
Jesus Cea Avion _/_/ _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/
jabber / xmpp:j...@jabber.org
.
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
-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
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
1 - 100 of 231 matches
Mail list logo
