On Thu, Apr 26, 2012 at 9:29 PM, Larry Hastings wrote:
> My one bit of bike-shedding: I don't think it's desirable that this object
> be iterable. Therefore I suggest you don't use struct sequence.
Good point. Noted.
-eric
___
Python-Dev mailing list
Hi,
On 26/04/2012 22.10, Vinay Sajip wrote:
Following recent changes in html.parser, the Python 3 port of Django I'm working
on has started failing while parsing HTML.
The reason appears to be that Django uses some module-level data in html.parser,
for example tagfind, which is a regular expres
On 04/25/2012 10:31 PM, Eric Snow wrote:
The patch adds a struct sequence that holds ("name" => "CPython",
"version" => sys.version_info). If later needs dictate more fields,
we can cross that bridge then.
My one bit of bike-shedding: I don't think it's desirable that this
object be iterabl
On Fri, Apr 27, 2012 at 7:30 AM, Christian Tismer wrote:
> No big deal and easy to work around, I just would like to understand why.
I don't like it either and want to change it, but I'm also not going
to mess with it until the importlib bootstrapping is fully integrated
and stable.
For the mome
On Fri, Apr 27, 2012 at 5:21 AM, Guido van Rossum wrote:
> Traditionally we've been really lax about this stuff. We should strive
> to improve and clarify the exact boundaries of our APIs better.
Yeah, I must admit in my own projects these days I habitually mark all
module level and class level n
Howdy,
I have a small problem/observation with imports.
I have several packages to import, which works all fine, as long
as the packages are imported from directories found on the installed
site-packages, via .pth etc.
The only problem is the automatically prepended empty string in sys.path.
De
On Thu, Apr 26, 2012 at 12:10 PM, Vinay Sajip wrote:
> Following recent changes in html.parser, the Python 3 port of Django I'm
> working
> on has started failing while parsing HTML.
>
> The reason appears to be that Django uses some module-level data in
> html.parser,
> for example tagfind, whi
On 26.04.2012 21:10, Vinay Sajip wrote:
> Following recent changes in html.parser, the Python 3 port of Django I'm
> working
> on has started failing while parsing HTML.
>
> The reason appears to be that Django uses some module-level data in
> html.parser,
> for example tagfind, which is a regul
Following recent changes in html.parser, the Python 3 port of Django I'm working
on has started failing while parsing HTML.
The reason appears to be that Django uses some module-level data in html.parser,
for example tagfind, which is a regular expression pattern. This has changed
recently (Ezio c
Regarding Eric's hint: It seems that this agreement needs to be signed
and mailed. Can I sign/scan and email it to somebody?
Yes, see
http://www.python.org/psf/contrib/
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
Hello Mark,
> A URL for the code repository (with an open-source license),
> so code can be reviewed.
> It is hard to review and update a giant patch.
OK, I took Nick's advice to heart and created a fork from the official
cpython mirror on bitbucket. You can view the code patched in
(branch: inc
On Thu, Apr 26, 2012 at 8:31 AM, Barry Warsaw wrote:
> On Apr 25, 2012, at 11:31 PM, Eric Snow wrote:
>>Are there any objections? Considering the positive reaction and the
>>scope of the addition, does this need a PEP?
>
> It's somewhat of a corner case, but I think a PEP couldn't hurt. The
> ra
On Thu, 26 Apr 2012 17:07:46 +0200, Stefano Taschini wrote:
> May I suggest that http://bugs.python.org/issue8767 be reopened, to make
> things clear?
Done.
--David
PS: we prefer no top-posting on this list. It makes it far easier
to retain just enough context to make a message stand on its ow
Understood.
May I suggest that http://bugs.python.org/issue8767 be reopened, to make
things clear?
Stefano
On 26 April 2012 16:01, wrote:
> I'm looking into issue 1065986 [1], and in order to submit a patch I need
>> to know whether I have to take into account the eventuality that cpyhon
2012/4/26 jesus.cea :
> http://hg.python.org/cpython/rev/86dc014cdd74
> changeset: 76570:86dc014cdd74
> user: Jesus Cea
> date: Thu Apr 26 16:39:35 2012 +0200
> summary:
> Close #10142: Support for SEEK_HOLE/SEEK_DATA
>
> files:
> Doc/library/io.rst | 5 +
> Doc/libra
On Apr 25, 2012, at 11:31 PM, Eric Snow wrote:
>The proposal of adding sys.implementation has come up a couple times
>over the last few years. [1][2] While the reaction has been
>overwhelmingly positive, nothing has come of it. I've created a
>tracker issue and a patch:
>
>http://bugs.python
I'm looking into issue 1065986 [1], and in order to submit a patch I need
to know whether I have to take into account the eventuality that cpyhon 2.7
be built without unicode support.
It's intended (at least, it is *my* intention) that Python 2.7 can be built
without Unicode support, and it's a
> -Original Message-
> From: "Martin v. Löwis" [mailto:mar...@v.loewis.de]
>
> This is easy in a debug build, using sys.getobjects(). In a release build,
> you can
> use pympler:
>
> start = pympler.muppy.get_size(pympler.muppy.get_objects())
> run_complicated_tests()
> end = pympler.m
Thanks.
Meanwhile, I blogged about tuning the dict implementation.
Preliminary testing seems to indicate that tuning it to conserve memory saves
us 2Mb of wasted slots on the login screen. No small thing on a PS3 system.
http://blog.ccpgames.com/kristjan/2012/04/25/optimizing-the-dict/
I wonder i
Hello every one,
I'm looking into issue 1065986 [1], and in order to submit a patch I need
to know whether I have to take into account the eventuality that cpyhon 2.7
be built without unicode support.
As far as I can see it is no longer possible to configure cpython 2.7 with
--disable-unicode as
20 matches
Mail list logo
