On Wed, Dec 08, 2004 at 02:18:48PM -0800, Guido van Rossum wrote:
This is a PR issue that Python needs to fight -- any ideas?
I'm not good at PR so I will continue to try to make it faster. In
my copious free time I plan to:
* finish the AST compiler (no performance benefit but makes
On Tue, Mar 01, 2005 at 11:45:43PM +1000, Nick Coghlan wrote:
Interesting. In that case, my other suggestion was to have raising
NotImplementedError from a special method be the equivalent of returning
NotImplemented (which makes life much easier for a class like Decimal which
has an
On Sat, Apr 04, 1998 at 07:04:02AM +, Tim Peters wrote:
[Martin v. L?wis]
I can't see any harm by supporting this operation also if __str__ returns
a Unicode object.
It doesn't sound like a good idea to me, at least in part because it
would be darned messy to implement short of saying
On Mon, Mar 21, 2005 at 11:53:04AM -0500, Brett C. wrote:
But one of things I am not sure of is what the marshal_write_*() functions
in Python/Python-ast.c are used for. I assume they output to the marshal
format, but there is mention of a byte stream format and so I thought it
might be
On Wed, Apr 27, 2005 at 12:30:22AM -0700, Guido van Rossum wrote:
I've written a PEP about this topic. It's PEP 340: Anonymous Block
Statements (http://python.org/peps/pep-0340.html).
[Note: most of these comments are based on version 1.2 of the PEP]
It seems like what you are proposing is a
On Thu, Apr 28, 2005 at 05:47:18PM -0400, Jing Su wrote:
Is there work to change python into a direct-threaded or even JIT'ed
interpreter?
People have experimented with making the ceval loop use direct
threading. If I recall correctly, the resulting speedup was not
significant. I suspect the
On Thu, Apr 28, 2005 at 03:55:03PM -0700, Guido van Rossum wrote:
A variation on this with somewhat different semantics swaps the keywords:
in EXPR for VAR:
BLOCK
Looks weird to my eyes.
On a related note, I was thinking about the extra cleanup 'block'
provides. If the 'file'
On Sat, Jun 18, 2005 at 06:24:48PM -0400, Phillip J. Eby wrote:
So, I think I've got this sorted out, assuming that I'm not doing
something hideously insane by having 'has_finalizer()' always
check tp_del even for non-heap types, and defining a tp_del slot
for generators to call close() in.
: 1.2 $
Last-Modified: $Date: 2005/08/06 04:05:48 $
Author: Neil Schemenauer [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Content-Type: text/plain
Created: 02-Aug-2005
Post-History: 06-Aug-2005
Python-Version: 2.5
Abstract
This PEP proposes the introduction of a new built-in function
On Sat, Aug 06, 2005 at 06:56:39PM -0700, Guido van Rossum wrote:
My first response to the PEP, however, is that instead of a new
built-in function, I'd rather relax the requirement that str() return
an 8-bit string
Do you have any thoughts on what the C API would be? It seems to me
that
On Sat, Aug 06, 2005 at 06:56:39PM -0700, Guido van Rossum wrote:
My first response to the PEP, however, is that instead of a new
built-in function, I'd rather relax the requirement that str() return
an 8-bit string -- after all, int() is allowed to return a long, so
why couldn't str() be
I've been getting:
ssh: connect to host cvs.sourceforge.net port 22: Connection refused
for the past few hours. Their Site News doesn't say anything
about downtime.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
On Sat, Aug 13, 2005 at 02:27:22PM -0700, Guido van Rossum wrote:
What do people think of using this for Python?
I think it deserves consideration. One idea would be to have a
Bazaar-NG repository that tracks the CVS SF repository. I haven't
tried it yet but there is a tool called Tailor[1]
On Sat, Aug 13, 2005 at 06:00:37PM -0500, [EMAIL PROTECTED] wrote:
Based on the message Guido forwarded, I installed bazaar-ng. From Mark's
note it seems they convert cvs repositories to bzr repositories, but I
didn't see any mention in the bzr docs of any sort of cvs2bzr tool.
Haven't tried
On Sun, Aug 14, 2005 at 06:16:11PM +0200, Martin v. Löwis wrote:
It depends on what a bit is. Waiting a month would be fine; waiting
two years might be pointless.
It looks like the process of converting a CVS repository to
Bazaar-NG does not yet work well (to be kind). The path
CVS-SVN-bzr
On Sat, Aug 13, 2005 at 06:03:46PM -0600, Neil Schemenauer wrote:
Haven't tried it but should work:
http://darcs.net/DarcsWiki/Tailor
After applying the attached patch, this command seemed to work for
converting the initial revision:
~/src/cvsync/tailor.py --source-kind cvs --target
On Tue, Aug 16, 2005 at 08:31:20PM +0200, Martin v. Löwis wrote:
I would agree. However, there still is the debate of hosting the
repository elsehwere. Some people (Anthony, Guido, Tim) would prefer
to pay for it, instead of hosting it on svn.python.org.
Another option would be to pay someone
On Wed, Aug 17, 2005 at 06:37:11PM +0200, Reinhold Birkenfeld wrote:
As I can see, this is not going to happen before Py3k, as it is completely
breaking backwards compatibility. As such, a PEP would be unnecessary.
We could add sys.id for 2.5 and remove __builtin__.id a some later
time (e.g.
applications and
report any incompatibilities.
PEP: 349
Title: Allow str() to return unicode strings
Version: $Revision: 1.3 $
Last-Modified: $Date: 2005/08/22 21:12:08 $
Author: Neil Schemenauer [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Content-Type: text/plain
Created: 02-Aug-2005
Post
On Tue, Aug 23, 2005 at 10:46:36AM +0200, Wolfgang Lipp wrote:
one point i don't seem to understand right now is why it says in the
function definition::
if type(s) is str or type(s) is unicode:
...
instead of using ``isinstance()``.
I don't think isinstance() would be
On Tue, Aug 23, 2005 at 11:43:02AM -0400, Phillip J. Eby wrote:
At 09:21 AM 8/23/2005 -0600, Neil Schemenauer wrote:
then of course, one could change ``unicode.__str__()`` to return
``self``, itself, which should work. but then, why so complicated?
I think that may be the right fix
On Tue, Aug 23, 2005 at 05:45:27PM +0200, Wolfgang Lipp wrote:
i have to revise my last posting -- exporting the new ``str``
pure-python implementation breaks -- of course! -- as soon
as ``isinstance(x,str)`` [sic] is used
Right. I tried to come up with a pure Python version so people
could
On Thu, Aug 25, 2005 at 11:58:48AM -0400, Raymond Hettinger wrote:
Deprecation is only warranted if the interim substitute works --
AFAICT, there is no other way to broadly catch exceptions not
derived from Exception.
This seems to get to the heart of the problem. I'm no fan of bare
excepts
On Wed, Aug 24, 2005 at 09:11:18PM +0200, Dieter Maurer wrote:
Neil Schemenauer [EMAIL PROTECTED] writes on Mon, 22 Aug 2005 15:31:42
-0600:
The code was fixed by changing
the line header = str(header) to:
if isinstance(header, unicode):
header
On Fri, Aug 26, 2005 at 06:21:58PM +0200, Alain Poirier wrote:
For example, I often use this class to help me in functional programming :
_marker = ()
[...]
You should not use an immutable object here (e.g. the empty tuple is
shared). My preferred idiom is:
_marker = object()
Cheers,
Nick Coghlan [EMAIL PROTECTED] wrote:
If we kill the branch for now, then anyone that wants to bring up the idea
again can write a PEP first
I still have some (very) small hope that it can be finished. If we
don't get it done soon then I fear that it will never happen. I had
hoped that a SoC
On Thu, Oct 13, 2005 at 05:08:41PM -0500, [EMAIL PROTECTED] wrote:
test_trace segfaults consistently, even when run alone.
That's a bug in frame_setlineno(), IMO. It's failing to detect an
invalid jump because the lnotab generated by the new compiler is
slightly different (DUP_TOP opcode
On Fri, Oct 14, 2005 at 01:03:28AM -0400, Raymond Hettinger wrote:
Do the AST branch generate a syntax error for:
foo(a = i for i in range(10))
No. It generates the same broken code as the current compiler.
Neil
___
Python-Dev mailing list
Anthony Baxter [EMAIL PROTECTED] wrote:
Could someone involved give a short email laying out what concrete (no
pun intended) advantages this new compiler gives us?
One advantage is that it decreases the coupling between the parser
and the backend of the compiler. For example, it should be
Simon Burton [EMAIL PROTECTED] wrote:
Is there a python interface ?
Not yet.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Fredrik Lundh [EMAIL PROTECTED] wrote:
Thomas Lee wrote:
Even if it meant we had just one function call - one, safe function call
that deallocated all the memory allocated within a function - that we
had to put before each and every return, that's better than what we
have.
alloca?
Perhaps
Tim Peters [EMAIL PROTECTED] wrote:
We should note that hotshot didn't intend to reduce total time
overhead. What it's aiming at here is to be less disruptive (than
profile.py) to the code being profiled _while_ that code is running.
A statistical profiler (e.g.
On Tue, Dec 06, 2005 at 11:20:46AM +0100, Weber, Gregoire wrote:
We're seriously evaluating Python for use in embedded realtime systems
and need some informations about Pythons garbage collector.
What we're interested mostly in the runtime behaviour of the GC. The
main question is:
Does
Armin Rigo [EMAIL PROTECTED] wrote:
On Mon, Dec 12, 2005 at 10:23:27PM +0100, Fredrik Lundh wrote:
$(AST_H) $(AST_C): $(AST_ASDL) $(ASDLGEN_FILES)
-$(PYTHON) $(ASDLGEN) $(AST_ASDL)
The same just-ignore-it behavior can bite if the script genuinely fails
after you just made a typo in
Armin Rigo [EMAIL PROTECTED] wrote:
Of course, speaking of a rewrite, PyPy does the right thing in
these two areas. Won't happen to CPython, though. There are too
much backward-compatibility issues with the PyTypeObject
structure; I think we're doomed with patching the bugs as they
show up.
Martin v. Löwis [EMAIL PROTECTED] wrote:
One challenge is that PyObject_GC_Del doesn't know how large the memory
block is that is being released. So it is difficult to find out how
much memory is being released in the collection.
Another idea would be to add accounting to the PyMem_*
Scott David Daniels [EMAIL PROTECTED] wrote:
Or, perhaps:
class _Quitter(str):
def __call__(self): raise SystemExit
quit = _Quitter('The quit command. Type quit() to exit')
exit = _Quitter('The exit command. Type exit() to exit')
FWIW, I like this kind of solution
Ian Bicking [EMAIL PROTECTED] wrote:
OTOH, str(path) will break unicode filenames. And unicode()
breaks anything that simply desires to pass data through without
effecting its encoding.
That general problem was the motivation for PEP 349. Originally I
suggested adding a new built-in.
Guido van Rossum [EMAIL PROTECTED] wrote:
PEP 349 - str() may return unicode. Where is this?
Does that mean you didn't find and read the PEP or was it written so
badly that it answered none of your questions? The PEP is on
python.org with all the rest. I set the status to Deferred
because it
Guido van Rossum [EMAIL PROTECTED] wrote:
In py3k, when the str object is eliminated, then what do you have?
Perhaps
- bytes(\x80), you get an error, encoding is required. There is no
such thing as default encoding anymore, as there's no str object.
- bytes(\x80, encoding=latin-1), you get a
On Tue, Feb 14, 2006 at 03:13:37PM -0800, Guido van Rossum wrote:
Also, bytes objects are (in my mind anyway) mutable. We have no other
literal notation for mutable objects. What would the following code
print?
for i in range(2):
b = babc
print b
b[0] = ord(A)
Would the
Guido van Rossum [EMAIL PROTECTED] wrote:
Anyway, we need a new PEP author who can take the current
discussion and turn it into a coherent PEP.
I'm not sure that I have time to be the official champion. Right
now I'm spending some time to collect all the ideas presented in the
email messages
I'm in the process of summarizing the dicussion on the bytes object
and an idea just occured to me. Imagine that I want to write code
that deals with strings and I want to be maximally compatible with
P3k. It would be nice if I could add:
from __future__ import unicode_strings
and have
On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
from __future__ import unicode_strings
Didn't we have a command-line option to do this? I believe it was
removed because nobody could see the point. (Or
: The bytes object
Version: $Revision$
Last-Modified: $Date$
Author: Neil Schemenauer [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Content-Type: text/plain
Created: 15-Feb-2006
Python-Version: 2.5
Post-History:
Abstract
This PEP outlines the introduction of a raw bytes sequence
On Thu, Feb 16, 2006 at 12:47:22PM -0800, Guido van Rossum wrote:
BTW, for folks who want to experiment, it's quite simple to create a
working bytes implementation by inheriting from array.array. Here's a
quick draft (which only takes str instance arguments):
Here's a more complete prototype.
Michael Hoffman [EMAIL PROTECTED] wrote:
Am I the only one who finds the use of self on a classmethod to be
incredibly confusing? Can we please follow PEP 8 and use cls
instead?
Sorry, using self was an oversight. It should be cls, IMO.
Neil
___
Oleg Broytmann [EMAIL PROTECTED] wrote:
What are disadvantages of a direct .len() instead of .__len__()?
I can think of a few arguments against getting rid of double
underscores in general. First, special methods are a little like
keywords in that it would be nice to introduce new ones from
Talin [EMAIL PROTECTED] wrote:
However, I would like to be able to reply to posts in such a way as to
have them appear in the appropriate place in the thread hierarchy.
The message should have a References header that contains the
Message-Id of the message that you are responding to.
Does
I occasionally need dictionaries or sets that use object identity
rather than __hash__ to store items. Would it be appropriate to add
these to the collections module?
Neil
___
Python-Dev mailing list
Python-Dev@python.org
Barry Warsaw [EMAIL PROTECTED] wrote:
There are two patches on SF to add a couple of features to the gc
module. Skip wrote one (which I reviewed) and I wrote the other.
Neither is earth shattering, but they're helpful when debugging gc
issues.
I have no major objections to either patch. The
Guido van Rossum [EMAIL PROTECTED] wrote:
Bad idea, as several pointed out -- quit() should return a 0 exit
to the shell.
I like the idea of making quit callable. One small concern I have
is that people will use it in scripts to exit (rather than one of
the other existing ways to exit). OTOH,
I think it would be a good idea to follow the Plone project and try
to encourage new developers by offering assistance to get them up
and running. AFAIK, we've done that for the other bug days but it
might help to publish the fact that no prior Python development
experience is necessary.
Neil
Guido van Rossum [EMAIL PROTECTED] wrote:
Not even True and False.
I don't see why everything that doesn't make sense to be shadowed
ought to become a keyword. That way lies madness.
Have you considered whether P3K will disallow names from being
shadowed in such as way as to prevent the
Guido van Rossum [EMAIL PROTECTED] wrote:
This would require a bit __del__ already called on an object,
but don't we have a whole word of GC-related flags?
No.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
Greg Ewing [EMAIL PROTECTED] wrote:
Okay, so would it be possible for a generator that
needs finalisation to set up a weakref callback, suitably
rooted somewhere so that the callback is reachable,
that references enough stuff to clean up after the
generator, without referencing the generator
Ka-Ping Yee [EMAIL PROTECTED] wrote:
Most other languages that support lexical scoping (including Scheme,
JavaScript, Ruby, Perl, E, Java, Smalltalk) provide a uniform way
to read and write to scopes at all levels. This is done by letting
programmers specify the scope in which they want a
The bug was reported by Armin in SF #1333982:
the literal -2147483648 (i.e. the value of -sys.maxint-1) gives
a long in 2.5, but an int in = 2.4.
I have a fix but I wonder if it's the right thing to do. I suppose
returning a long has the chance of breaking someone code. Here's
the test
On Sun, Jul 09, 2006 at 03:02:06PM -0700, Neal Norwitz wrote:
Do we care about this (after your checkin and with my fix to make
32-63 bit values ints rather than longs):
# 64 bit box
minint = str(-sys.maxint - 1)
minint
'-9223372036854775808'
eval(minint)
-9223372036854775808
Neal Norwitz [EMAIL PROTECTED] wrote:
I don't know of any. I haven't heard of any issues with the fixes
that have been checked in.
It would be nice if someone could bytecompile Lib using
Tools/compiler/compile.py and then run the test suite. I'd do it
myself but can't spare the time at the
Neal Norwitz [EMAIL PROTECTED] wrote:
On 8/15/06, Neil Schemenauer [EMAIL PROTECTED] wrote:
It would be nice if someone could bytecompile Lib using
Tools/compiler/compile.py and then run the test suite.
Has this been done before?
Obviously not. :-)
# This code causes python to segfault
John J Lee [EMAIL PROTECTED] wrote:
The note (4) says that the result will be unicode, but it doesn't say how,
in this case, that comes about. This case is confusing because the docs
claim string formatting with %s converts ... using str(), and yet
str(a()) returns a bytestring. Does it
M.-A. Lemburg [EMAIL PROTECTED] wrote:
You can add a -1 from me to the list as well: I don't think that
dynamic lookups are common enough to warrant new syntax.
I agree. Also, I think the special syntax may make them too
inviting to new programmers, who haven't figured out that usually
there
Neal Norwitz [EMAIL PROTECTED] wrote:
The time schedules in PEP 361 (2.6 release schedule) and what Guido
has said for 3k (from what I remember) are roughly:
April 2007 - 3.0 PEPs and features accepted/decided
June 2007 - 3.0a1 - basic (most) features implemented
Any talk at PyCon
On Sun, Feb 25, 2007 at 05:37:08PM -0600, Guido van Rossum wrote:
Right. To be honest, I consider the str/unicode unification a much
bigger project than the new I/O library.
I was more concerned about IO because it would seem to require your
time for design work. The str/unicode work could be
A.M. Kuchling [EMAIL PROTECTED] wrote:
At PyCon, there was general agreement that exposing a read-only
Bazaar/Mercurial/git/whatever version of the repository wouldn't be
too much effort, and might make things easier for external people
developing patches. Thomas Wouters apparently has
Neil Schemenauer [EMAIL PROTECTED] wrote:
Using git-svn to track a SVN repository seems to work well. It
would be trivial to setup a cron job on one of the python.org
machines that would create a publicly accessible repository.
I guess Andrew was looking for specific instructions. Install
Martin v. Löwis [EMAIL PROTECTED] wrote:
Why isn't the mark-and-sweep mechanism used for all memory
management?
See above - it's not implementable, because the root objects get not
tracked.
To further elaborate, the main obstacle is with extension modules.
Most of them create roots and there
Guido van Rossum [EMAIL PROTECTED] wrote:
bytes is an alias for str (not even a subclass)
b is an alias for
One advantage of a subclass is that there could be a flag that warns
about combining bytes and unicode data. For example, bx + uy
would produce a warning. As someone who writes
Christian Heimes [EMAIL PROTECTED] wrote:
+1 on focusing on improving pymalloc to handle int and float
object allocations even better
I wonder if the int and float types could use a faster internal
pymalloc interface. I can't remember the details but I seem to
recall that pymalloc must jump
Nick Coghlan [EMAIL PROTECTED] wrote:
The problem is calls to Py_DECREF(self-attr) where some of the code
invoked by __del__ manages to find a way back around to reference
self-attr and gets access to a half-deleted object.
Don't you mean __del__ manages to find a way back around to self?
If
On Mon, Feb 18, 2008 at 05:48:57PM +0100, Amaury Forgeot d'Arc wrote:
For example, in exception.c, BaseException_init() starts with the instruction:
Py_DECREF(self-args);
this may call __del__ on self-args
Ah, I understand now. We are not talking about tp_dealloc methods
(the GC takes
I wrote:
Most Py_DECREF calls are probably okay but it's going to be hard
to find the ones that are not.
I suppose Py_DECREF is not the only source of trouble. Many calls
to the Python API can end up calling arbitrary user code (via
__getattr__, __getitem__, etc.). Whenever an object does
Guido van Rossum gu...@python.org wrote:
No. Trust me. It is not always possible to strengthen the
implementation. (At least not until we get rid of the replace all
globals with None upon module deletion rule.)
We should do that. Trying to do cleanup without globals sucks. I
updated Armin's
Guido van Rossum gu...@python.org wrote:
So how do you get destructors to run in that case? Or do you just not
run them? Then open files may not be closed and may not even see their
buffer flushed. I'm not happy about that.
Unfortantely I don't have an up-to-date understand of the issues
I've revised my instructions on using the experimental git mirror of
the Python SVN repository:
http://python.ca/nas/tmp/git-notes.txt
Stories of success or failure welcome.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
On Fri, Feb 27, 2009 at 08:36:08AM -0600, Brad Miller wrote:
when I get to the step git svn fetch I get the following error:
zsh-% git svn fetch
Permission denied (publickey).
Network connection closed unexpectedly: Connection closed unexpectedly at
/opt/local/bin/git-svn line 1385
Is
David Ripton drip...@ripton.net wrote:
I don't see any point to using Neil's complicated dual-remote git +
git-svn setup if you don't have commit access.
Good point. I will write another, hopefully simpler, set of
instructions for read-only access.
Neil
Chris McDonough chr...@plope.com wrote:
As far as I can tell, asyncore/asynchat is all undocumented
internals. Any use of asyncore in anger will use internals;
there never was any well-understood API to these modules.
What I would like to see is a module that provides a low-level API
for
gl...@divmod.com gl...@divmod.com wrote:
... which is exactly why I have volunteered to explain to someone how to
separate the core event-loop bits (suitable for inclusion in the
standard library) from the huge pile of protocol implementations which
are not necessarily useful.
Despite the
Barry Warsaw ba...@python.org wrote:
It would be really nice if say the Cheeseshop had a voting feature.
Use PEP 10 voting to get a rough estimate of a module's popularity
(download counts alone might not tell you everything). Then at least
you can get a rough idea of how generally
Guido van Rossum gu...@python.org wrote:
Does this need a pronouncement? Worrying about the speed of symlinks
seems silly
I agree. I wonder if a hard-link was used for legacy reasons. Some
very old versions of Unix didn't have symlinks. It looks like it
was introduced in BSD 4.2, released in
Greg Ewing [EMAIL PROTECTED] wrote:
Martin v. Löwis wrote:
Under my proposal, 10 middle collections must have passed,
PLUS the number of survivor objects from the middle generation
must exceed 10% of the number of objects in the oldest
generation.
What happens if the program enters a phase
Hi,
In case anyone is interested, I have git repositories for both the
trunk and the py3k branch of the Python source code. They are
up-to-date and so using them with git-svn would be much faster than
starting from scratch.
If anyone is interested, I will find a place to host them. They are
On Mon, Jul 14, 2008 at 09:31:47PM -0400, Barry Warsaw wrote:
Neil, we should try to host them on code.python.org.
I was hoping to get a sense of the interest. Oh well, if you build
it they might come. ;-) I've written draft instructions, temporarily
at http://python.ca/nas/tmp/git-notes.txt.
Benjamin Peterson [EMAIL PROTECTED] wrote:
Can we push branches?
The git-daemon is setup as read-only. If you have write access to
the SVN repository then you can push back changes using git-svn.
That's quite a nice way to work, IMHO and provides an easy path for
people who are used to
[back on the list]
On Thu, Jul 17, 2008 at 11:24:16PM -0700, Brett Cannon wrote:
Turned out to be a rebuild::
r65077 = 82d954e8c20c91562c4c660859d17756cba10992
r65082 = 1c75cce93c2ef2ec87e801888638cfdf5d2ff29a
r65085 = 3143c2fbe7315afd29496dc0cdac3122bed30536
Done rebuilding
On Fri, Jul 18, 2008 at 11:12:41AM -0700, Brett Cannon wrote:
git log git-svn..
And those two periods are significant for people who think they are
line noise. Damn is Git quirky.
I guess it would have been clearer if I had used git-svn..HEAD.
The .. is similar to SVN's : so I don't see
On Fri, Jul 18, 2008 at 11:57:21AM -0700, Brett Cannon wrote:
I figured this out. I just did ``git reset --hard``, did the proper
fetch;rebase dance, resolved the conflict, did ``git add`` and then
continued with the rebase. It all looks fine now.
Doing a fetch followed by a rebase is similar
On Fri, Jul 18, 2008 at 12:07:19PM -0700, Brett Cannon wrote:
I lied. Trying again complained about Mac/IDLE/Makefile.in which I
have not touched, nor is it listed as changed.
I think you are running into the fact that the git tree on
code.python.org is only updated every 30 minutes. Using the
Sigurd Torkel Meldgaard [EMAIL PROTECTED] wrote:
For a student project in a course on virtual machines, we are
evaluating the possibility to experiment with removing the GIL
from CPython
Hi,
It's great to hear of this kind of project. I think what you want
to do is difficult but possible.
Georg Brandl g.bra...@gmx.net wrote:
Am 22.07.2010 13:29, schrieb Antoine Pitrou:
Is it the reason why? With the new module creation API in 3.x, extension
modules should be able to handle deletion of their own internal
resources.
Yes, but as Martin noted at the summit, nobody since went
Georg Brandl g.bra...@gmx.net wrote:
The hard part is to know *when* to look. As you might have noticed, the
Python test suite does not run in ten seconds, especially on some of the
buildbots -- it can take 1-2 there to complete.
Based on this and other issues, I don't think it's practical to
Peter Ingebretson pinge...@yahoo.com wrote:
I am happy to write up a PEP for this feature. I'll start that
process now, though if anyone feels that this idea has no chance of
acceptance please let me know.
I think a feature that allows modules to be more reliability
reloaded could be
I have a specific, easy to implement proposal. I would like one
more version tag added to the Roundup tracker. My proposed name is
Python 2.7+ but I don't care what it is called.
It would be used to tag bug reports and patches that apply only to
the 2.x line and are considered not appropriate
Barry Warsaw ba...@python.org wrote:
On Jan 04, 2011, at 10:21 AM, Alex Gaynor wrote:
Ugh, I can't be the only one who finds these special cases to be a little
nasty?
Special cases aren't special enough to break the rules.
Yeah, I agree. Still it would be interesting to see what kind of
Greg Ewing greg.ew...@canterbury.ac.nz wrote:
So am I. It seems to result from the hisorical mess
of distinguishing between numeric and sequence operations
at the C level but not the Python level. I think CPython
should be moving in the direction of eliminating that
distinction, not expecting
Guido van Rossum gu...@python.org wrote:
What is rebase? Why does everyone want it and hate it at the same time?
It's the same thing that happens when you do a svn up with local
changes in your checkout. Logically, your patch gets modified so
that it applies on a different (newer) version of
Barry Warsaw ba...@python.org wrote:
I'm asking because I don't know hg and git well enough to answer the
question. In my own use of Bazaar over the last 4+ years, I've almost never
rebased or even been asked to.
Maybe it depends on what kind of changes you commit. I consider
future
As a user of the AST, I as well favor just changing the AST and the
version. IMHO, it is not intended to be stable between Python
releases (similar to bytecode).
Neil
___
Python-Dev mailing list
Python-Dev@python.org
1 - 100 of 229 matches
Mail list logo
