Nick Coghlan wrote:
> Is there a specific reason for not fully initialising the builtin types?
> Or should we be calling PyType_Ready on each of them from _PyBuiltin_Init?
I need to correct this slightly: some builtin types *are* initialised
properly by _Py_ReadyTypes.
So the question is actually
I have now set up buildbot slaves for 2.6 and 3.0,
and turned off the 2.5 ones.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
> Do you think we can get 3.0.1 out on December 24th?
I won't have physical access to my build machine from December 24th to
January 3rd.
> Or should we wait
> until after Christmas and get it out, say on the 29th? Do we need an rc?
If you want to get it quickly, it should happen on December 23
I have a program that creates a huge (45GB) defaultdict. (The keys
are short strings, the values are short lists of pairs (string, int).)
Nothing but possibly the strings and ints is shared.
The program takes around 10 minutes to run, but longer than 20 minutes
to exit (I gave up at that point).
On Fri, Dec 19, 2008 at 19:59, Benjamin Peterson
wrote:
> On Fri, Dec 19, 2008 at 12:55 PM, Tarek Ziadé wrote:
>> Hello
>>
>> I would like to request a commit access to work specifically on
>> distutils maintenance.
>
> +1
>
> We are currently without an active distutils maintainer, and many
> st
Antoine Pitrou pitrou.net> writes:
>
> Note the "binary". And indeed:
[...]
And I realize I should have thought a bit before giving that "proof".
Sorry!
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
Fror truly unbuffered text output you'd have to make changes to the
io.TextIOWrapper class to flush after each write() call. That's an API
change -- the constructor currently has a line_buffering option but no
option for completely unbuffered mode. It would also require some
changes to io.open() wh
Nick Coghlan gmail.com> writes:
>
> There are some memoryview issues [1] I'd like to have fixed for 3.0.1 -
> the 29th would be a much easier date to hit. A quick review pass through
> the other 3.0 highs and criticals might also be worthwhile.
What about #1717 "Get rid of more refercenes to __c
> Well, ``python -h`` still lists it.
Precisely, it says:
-u : unbuffered binary stdout and stderr; also PYTHONUNBUFFERED=x
see man page for details on internal buffering relating to '-u'
Note the "binary". And indeed:
./python -u
Python 3.1a0 (py3k:67839M, Dec 18 2008, 17:56:54)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 19, 2008, at 5:42 PM, Nick Coghlan wrote:
Barry Warsaw wrote:
I'd like to get Python 3.0.1 out before the end of the year. There
are
no showstoppers, but I haven't yet looked at the deferred blockers or
the buildbots.
Do you think we can
Barry Warsaw wrote:
> I'd like to get Python 3.0.1 out before the end of the year. There are
> no showstoppers, but I haven't yet looked at the deferred blockers or
> the buildbots.
>
> Do you think we can get 3.0.1 out on December 24th? Or should we wait
> until after Christmas and get it out,
On Dec 19, 2008 2:20pm, Fabio Zadrozny wrote:
You're right, thanks (guess I'll use that option then).
Now, is it a bug that Python 3.0 doesn't run unbuffered when
specifying -u or PYTHONUNBUFFERED, or was this support dropped?
Well, ``python -h`` still lists it. That means either the out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to get Python 3.0.1 out before the end of the year. There
are no showstoppers, but I haven't yet looked at the deferred blockers
or the buildbots.
Do you think we can get 3.0.1 out on December 24th? Or should we wait
until after Chr
You're right, thanks (guess I'll use that option then).
Now, is it a bug that Python 3.0 doesn't run unbuffered when
specifying -u or PYTHONUNBUFFERED, or was this support dropped?
Thanks,
Fabio
On Fri, Dec 19, 2008 at 8:03 PM, Brett Cannon wrote:
> On Fri, Dec 19, 2008 at 13:43, Fabio Zadrozn
Brett Cannon wrote:
> Notice how the exception specifies test I/O cannot be unbuffered. This
> restriction does not apply to bytes I/O. Simply open it as 'wb'
> instead of 'w' and it works.
s/test/text/ :)
(For anyone else that is like me and skipped over the exception detail
on first reading, th
Some strangeness was recently reported for the range() type in Py3k
where instances are unhashable until an attribute is retrieved from the
range type itself, and then they become hashable. [1]
While there is definitely an associated bug in the range implementation
(it doesn't block inheritance of
On Fri, Dec 19, 2008 at 13:43, Fabio Zadrozny wrote:
> Hi,
>
> I'm currently having problems to get the output of Python 3.0 into the
> Eclipse console (integrating it into Pydev).
>
> The problem appears to be that stdout and stderr are not running
> unbuffered (even passing -u or trying to set P
Hi,
I'm currently having problems to get the output of Python 3.0 into the
Eclipse console (integrating it into Pydev).
The problem appears to be that stdout and stderr are not running
unbuffered (even passing -u or trying to set PYTHONUNBUFFERED), and
the content only appears to me when a flush(
> I got a "Problem Report for Python" pop-up. Skip to "///" for
> "Problem Details". Interestingly, the test completed with the
> following report:
Thanks for the report. I have tested that with 2.5.2, which fails
in the same way. So this is not a regression, and I have not attempted
to fix it.
Ok, in this case I move that we remove this try/except and see where it leads
us.
If we see problems during teardown, we should deal with them in a more targeted
manner.
Kristján
-Original Message-
From: Nick Coghlan [mailto:ncogh...@gmail.com]
Sent: 19. desember 2008 13:51
To: Kristjá
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.6 and 2.5.3 (final).
2.5.3 is the last bug fix release of Python 2.5. Future 2.5.x releases
will only include security fixes. According to the release notes, about
80 bugs and patches
On Fri, Dec 19, 2008 at 12:55 PM, Tarek Ziadé wrote:
> Hello
>
> I would like to request a commit access to work specifically on
> distutils maintenance.
+1
We are currently without an active distutils maintainer, and many
stale distutil tickets are in need of attention I'm sure Tarek could
prov
Hello
I would like to request a commit access to work specifically on
distutils maintenance.
Regards
Tarek
--
Tarek Ziadé | Association AfPy | www.afpy.org
Blog FR | http://programmation-python.org
Blog EN | http://tarekziade.wordpress.com/
___
Python
ACTIVITY SUMMARY (12/12/08 - 12/19/08)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2266 open (+37) / 14258 closed (+20) / 16524 total (+57)
Open issues with patches: 762
Average
> Is there some reason no set tp_hash for rangeobject to
> PyObject_HashNotImplemented ?
http://bugs.python.org/issue4701
- Hagen
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://
On Fri, Dec 19, 2008 at 12:20 PM, Dmitry Vasiliev wrote:
> Hello!
>
> I think it's a strange behavior:
>
> Python 3.1a0 (py3k:67851, Dec 19 2008, 16:50:32)
> [GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
hash(range(10))
Christian Heimes wrote:
Dmitry Vasiliev schrieb:
Hello!
I think it's a strange behavior:
Python 3.1a0 (py3k:67851, Dec 19 2008, 16:50:32)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
hash(range(10))
Traceback (most recen
Dmitry Vasiliev schrieb:
> Hello!
>
> I think it's a strange behavior:
>
> Python 3.1a0 (py3k:67851, Dec 19 2008, 16:50:32)
> [GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
hash(range(10))
> Traceback (most recent call l
Hello!
I think it's a strange behavior:
Python 3.1a0 (py3k:67851, Dec 19 2008, 16:50:32)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> hash(range(10))
Traceback (most recent call last):
File "", line 1, in
TypeError: u
Kristján Valur Jónsson wrote:
> Ah, but that is not what the intent is to guard agains, according the
> comments. During exit, modules have been deleted and all sorts of
> things have gone away. It is therefore likely that code that executes
> during exit will encounter NameErrors (when a module is
> > try:
> > self.close()
> > except:
> > try:
> >if not sys.exiting(): raise
> > except:
> >pass
> >
> >
> > Or better yet, do as we have done often here, just catch the particular
> >
Hello,
Kristján Valur Jónsson wrote:
> Greetings!
>
> Yesterday, I committed revision r67843 to py3k.
>
> Re-enablign the windows CRT runtime checks showed me that close() was beeing
> called with an invalid file descriptor.
>
> Now, the problem was was in tokenizer.c, but the reason this wasn't ca
Greetings!
Yesterday, I committed revision r67843 to py3k.
Re-enablign the windows CRT runtime checks showed me that close() was beeing
called with an invalid file descriptor.
Now, the problem was was in tokenizer.c, but the reason this wasn't caught
earlier was,
1) Incorrect error checkin
33 matches
Mail list logo
