On 11/23/2010 1:44 AM, Georg Brandl wrote:
Am 23.11.2010 07:13, schrieb Terry Reedy:
On 11/23/2010 1:01 AM, terry.reedy wrote:
Author: terry.reedy
Date: Tue Nov 23 07:01:31 2010
New Revision: 86702
Log:
Issue 9222 Fix filetypes for open dialog
Sorry, forgot to add this before clicking [go]
> But if we say the Python can be compiled as 64 bits under Solaris, would
> be nice if that was actually true. Now that we have a buildbot (under
> OpenIndiana) to test, it is doable.
But it is true, and always has been true. The lib/64 issue did not
prevent one building Python on Solaris/SPARC64
On 11/23/2010 1:16 AM, Senthil Kumaran wrote:
Hi Terry,
On Tue, Nov 23, 2010 at 2:07 PM, terry.reedy wrote:
Author: terry.reedy
Date: Tue Nov 23 07:07:04 2010
New Revision: 86703
Log:
Issue 9222 Fix filetypes for open dialog
Modified:
python/branches/release31-maint/Lib/idlelib/IOBindin
Am 23.11.2010 07:13, schrieb Terry Reedy:
>
>
> On 11/23/2010 1:01 AM, terry.reedy wrote:
>> Author: terry.reedy
>> Date: Tue Nov 23 07:01:31 2010
>> New Revision: 86702
>>
>> Log:
> Issue 9222 Fix filetypes for open dialog
>
> Sorry, forgot to add this before clicking [go] or whatever the butto
Hi Terry,
On Tue, Nov 23, 2010 at 2:07 PM, terry.reedy wrote:
> Author: terry.reedy
> Date: Tue Nov 23 07:07:04 2010
> New Revision: 86703
>
> Log:
> Issue 9222 Fix filetypes for open dialog
>
> Modified:
> python/branches/release31-maint/Lib/idlelib/IOBinding.py
You should be using svnmerge.
On 11/23/2010 1:01 AM, terry.reedy wrote:
Author: terry.reedy
Date: Tue Nov 23 07:01:31 2010
New Revision: 86702
Log:
Issue 9222 Fix filetypes for open dialog
Sorry, forgot to add this before clicking [go] or whatever the button
is. Is there any way to revise a revision ;-?
Modified:
On Mon, Nov 22, 2010 at 11:13 PM, Hirokazu Yamamoto <
ocean-c...@m2.ccsnet.ne.jp> wrote:
> Hello. Does this affect python? Thank you.
>
> http://www.openssl.org/news/secadv_20101116.txt
>
No.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail
Hello. Does this affect python? Thank you.
http://www.openssl.org/news/secadv_20101116.txt
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-d
2010/11/22 Łukasz Langa :
> Wiadomość napisana przez Benjamin Peterson w dniu 2010-11-23, o godz. 00:47:
>
> No test?
>
>
> The tests were there already, raising ResourceWarnings. After this change,
> they stopped doing that. You may say: now they pass for the first time :)
It looks like you added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 01:05, "Martin v. Löwis" wrote:
> I just point out that none of the binaries in /usr/bin is a 64-bit
> binary; this includes the Sun-provided /usr/sfw/bin/python
True. This is for simplicity reasons (provide only one binary valid for
32 an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 01:05, "Martin v. Löwis" wrote:
> No offense taken. If you really want to know the historical background:
> this was the very first build slave (before I actually announced it to
> python-dev), and I haven't changed much from the initial se
Wiadomość napisana przez Michael Foord w dniu 2010-11-22, o godz. 23:01:
> On 22/11/2010 21:08, Guido van Rossum wrote:
>> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>>> The problem with that is it means developers who switch to Python 3.2
>>> or whatever are suddenly going to have the
On 11/22/2010 11:46 PM, Anurag Chourasia wrote:
I have a problem in starting my Python(Django) App using Apache and Mod_Wsgi
I'm pretty sure you're asking on the wrong list. This one is for
discussing development of python-the-language :-)
You'd better head over to the django-user mailingl
Wiadomość napisana przez Benjamin Peterson w dniu 2010-11-23, o godz. 00:47:
> No test?
>
The tests were there already, raising ResourceWarnings. After this change, they
stopped doing that. You may say: now they pass for the first time :)
Best regards,
Łukasz
> 2010/11/22 lukasz.langa :
>> A
Am 23.11.2010 00:48, schrieb Jesus Cea:
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
The canonical way is to use platform.architecture().
> And any macro useable for conditional compilation in C?.
You need to be mor
On Mon, Nov 22, 2010 at 17:48, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
>
import platform
platform.architecture()
On Tue, 23 Nov 2010 00:48:06 +0100
Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
sys.maxsize
> And any macro useable for conditional compilation i
Am 23.11.2010 00:41, schrieb Jesus Cea:
> On 22/11/10 23:05, "Martin v. Löwis" wrote:
>>> PS: Martin, is there any reason to restrict the solaris 10 buildslaves
>>> to 32 bits, beside the said problems?.
>
>> I don't see that as a restriction. I have to make a choice, and there
>> are sooo many ch
On 11/22/2010 5:46 PM, Anurag Chourasia wrote:
[Mon Nov 22 09:45:43 2010] [error] [client 108.10.0.191] mod_wsgi
(pid=1273874): Target WSGI script '/u01/home/apli/wm/app/gdd/pyserver/
apache/django.wsgi' cannot be loaded as Python module.
All other error stem probably from this.
Please guide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think this is probably trivial, but is there any foolproof way to
detect 64 bit builds in python, beside "sys.maxint"?.
And any macro useable for conditional compilation in C?.
Checking Solaris 10 header files, I see macros like "_LP64". Portabilit
No test?
2010/11/22 lukasz.langa :
> Author: lukasz.langa
> Date: Tue Nov 23 00:31:26 2010
> New Revision: 86699
>
> Log:
> Issue #9846: ZipExtFile provides no mechanism for closing the underlying file
> object
>
>
>
> Modified:
> python/branches/py3k/Lib/zipfile.py
>
> Modified: python/branche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 23:05, "Martin v. Löwis" wrote:
>> PS: Martin, is there any reason to restrict the solaris 10 buildslaves
>> to 32 bits, beside the said problems?.
>
> I don't see that as a restriction. I have to make a choice, and there
> are sooo many c
Am 22.11.2010 23:51, schrieb Éric Araujo:
> Hi,
>
> I think this bug is related: http://bugs.python.org/issue1294959
> “Problems with /usr/lib64 builds.”
Perhaps more closely related:
http://bugs.python.org/issue847812
http://bugs.python.org/issue1733484
http://bugs.python.org/issue1676121
http:
On Mon, Nov 22, 2010 at 16:54, Glenn Linderman wrote:
> I suppose it is possible that some environment variables are used by Python
> directly (but I can't seem to find a documented list of them) although I
> would expect that usage to be optional, with fall-back defaults when they
> don't exist.
Hi,
I think this bug is related: http://bugs.python.org/issue1294959
“Problems with /usr/lib64 builds.”
Regards
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/ma
All,
I have a problem in starting my Python(Django) App using Apache and Mod_Wsgi
I am using Django 1.2.3 and Python 2.6.6 running on Apache 2.2.17 with
Mod_Wsgi 3.3
When I try to access the app from Web Browser, I am getting these
errors.
[Mon Nov 22 09:45:25 2010] [notice] Apache/2.2.17 (Unix
On Mon, Nov 22, 2010 at 13:08, Guido van Rossum wrote:
> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>> The problem with that is it means developers who switch to Python 3.2
>> or whatever are suddenly going to have their tests fail until they
>> update their code to turn the warnings o
In article <4ceae129.2060...@jcea.es>, Jesus Cea wrote:
> On 22/11/10 20:42, "Martin v. Löwis" wrote:
> > Before enabling anything on a build slave, a patch needs to be
> > contributed to make it work in the first place.
>
> I actually agree. I am not sure yet, but I am thinking that adding a
> "
> I actually agree. I am not sure yet, but I am thinking that adding a
> "--build-64" parameter to "configure" could be an option under Solaris.
> Most OSs (let say, Linux) force you to choose 32/64 bits at install
> time
Actually, that's not at all the case. Most systems these days support
32-bit
On 22/11/2010 21:08, Guido van Rossum wrote:
On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
The problem with that is it means developers who switch to Python 3.2
or whatever are suddenly going to have their tests fail until they
update their code to turn the warnings off.
That sounds li
On 11/22/2010 8:33 AM, Guido van Rossum wrote:
On Sun, Nov 21, 2010 at 9:40 PM, Glenn Linderman wrote:
In reviewing my notes from my experimentations with CGIHTTPServer
(Python2.6) and then http.server (Python 3.2a4), I note one behavior I
haven't reported as a bug, nor do I know where to start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 20:42, "Martin v. Löwis" wrote:
> Before enabling anything on a build slave, a patch needs to be
> contributed to make it work in the first place.
I actually agree. I am not sure yet, but I am thinking that adding a
"--build-64" parameter
On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
> The problem with that is it means developers who switch to Python 3.2
> or whatever are suddenly going to have their tests fail until they
> update their code to turn the warnings off.
That sounds like a feature to me... :-)
--
--Guido van
On Mon, 22 Nov 2010 12:37:59 -0500, Alexander Belopolsky
wrote:
> On Mon, Nov 22, 2010 at 12:30 PM, R. David Murray
> wrote:
> ..
> > For reference, a grep in py3k/Doc reveals that there are currently exactly
> > 23 lines mentioning UCS2 or UCS4 in the docs.
>
> Did you grep for USC-2 and USC-
> Solaris overcomes most of the issue having separate library searchpath
> in 32 and 64 bits (via the "crle" command). But in some cases python try
> to find some library in "/usr/local/lib", and my point is that it should
> search TOO inside "/usr/local/lib/64".
I don't think this will work. If t
On Nov 10, 2010, at 04:27 PM, Barry Warsaw wrote:
>I finally found a chance to address all the outstanding technical issues
>mentioned in bug 9807:
>
>http://bugs.python.org/issue9807
>
>I've uploaded a new patch which contains the rest of the changes I'm
>proposing. I think we still need con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 20:12, Brett Cannon wrote:
> Are you asking about buildbots only or as a general policy? If you are
> asking about the buildbots then I definitely think we should use 64
> bits. If you are asking about policy I would say it should be an
> o
On Mon, Nov 22, 2010 at 10:58, Ezio Melotti wrote:
> On 22/11/2010 19.45, Michael Foord wrote:
>>
>> On 22/11/2010 17:35, Łukasz Langa wrote:
>>>
>>> Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
>>>
>>> +1
>>>
On Mon, Nov 22, 2010 at 10:34, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A Solaris installation contains ALWAYS 32 and 64 bits libraries. So in
> any Solaris you can run 32/64 bits programs, and compile in 32 and 64 bits.
>
> For this, libraries are stores in "/usr/lib
On Mon, Nov 22, 2010 at 12:41 PM, Terry Reedy wrote:
..
> What Python does might be called USC-2+ or UCS-2e (xtended).
>
Wow! I am not the only one who can't get the order of letters right
in these acronyms. (I am usually consistent within one sentence,
though.) :-)
I-can't-spell-three-letter-
On 22/11/2010 19.45, Michael Foord wrote:
On 22/11/2010 17:35, Łukasz Langa wrote:
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently
we have a horde
Raymond Hettinger wrote:
> Any explanation we give users needs to let them know two things:
> * that we cover the entire range of unicode not just BMP
> * that sometimes len(chr(i)) is one and sometimes two
>
> The term UCS-2 is a complete communications failure
> in that regard. If someone looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A Solaris installation contains ALWAYS 32 and 64 bits libraries. So in
any Solaris you can run 32/64 bits programs, and compile in 32 and 64 bits.
For this, libraries are stores in "/usr/lib", for instance, for 32 bits,
while the same 64 bits librarie
On Nov 22, 2010, at 9:41 AM, Terry Reedy wrote:
> On 11/22/2010 5:48 AM, Stephen J. Turnbull wrote:
>
>> I disagree. I do see a problem with "UCS-2", because it fails to tell
>> us that Python implements a large number of features that make it easy
>> to do a very good job of working with non-B
On Nov 22, 2010, at 2:48 AM, Stephen J. Turnbull wrote:
> Raymond Hettinger writes:
>
>> Neither UTF-16 nor UCS-2 is exactly correct anyway.
>
> From a standards lawyer point of view, UCS-2 is exactly correct,
You're twisting yourself into definitional knots.
Any explanation we give users nee
On 22/11/2010 17:35, Łukasz Langa wrote:
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently
we have a horde of ResourceWarnings, zipfile mostly). I wou
On 11/22/2010 5:48 AM, Stephen J. Turnbull wrote:
I disagree. I do see a problem with "UCS-2", because it fails to tell
us that Python implements a large number of features that make it easy
to do a very good job of working with non-BMP data in 16-bit builds of
Yes. As I read the standard, UC
On Mon, Nov 22, 2010 at 12:30 PM, R. David Murray wrote:
..
> For reference, a grep in py3k/Doc reveals that there are currently exactly
> 23 lines mentioning UCS2 or UCS4 in the docs.
Did you grep for USC-2 and USC-4 as well? I have to admit that my
aversion to these terms is mostly due to the
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently we
have a horde of ResourceWarnings, zipfile mostly). I would even be +1 on
making warnings errors f
On Mon, 22 Nov 2010 12:00:14 -0500, Alexander Belopolsky
wrote:
> I recently updated chr() and ord() documentation and used
> "narrow/wide" terms. I thought USC2/4 proponents objected to that on
> the basis that these terms are imprecise.
For reference, a grep in py3k/Doc reveals that there a
I would like to re-enable by default warnings for regrtest and/or unittest.
The reasons are:
1) these tools are used mainly by developers and they (should) care
about warnings;
2) developers won't have to remember that warning are silenced and
how to enable them manually;
3) developers wo
On 04:24 pm, solip...@pitrou.net wrote:
On Mon, 22 Nov 2010 17:08:36 +0100
Hrvoje Niksic wrote:
On 11/22/2010 04:37 PM, Antoine Pitrou wrote:
> +1. The problem with int constants is that the int gets printed,
not
> the name, when you dump them for debugging purposes :)
Well, it's trivial to
On Mon, Nov 22, 2010 at 11:13 AM, Nick Coghlan wrote:
..
>> Do you think these articles are helpful for someone learning how to
>> use chr() and ord() in Python for the first time?
>
> No, that's what the documentation of chr() and ord() is for. For that
> use case, it doesn't matter *what* the te
On 22/11/2010 16:24, Antoine Pitrou wrote:
On Mon, 22 Nov 2010 17:08:36 +0100
Hrvoje Niksic wrote:
On 11/22/2010 04:37 PM, Antoine Pitrou wrote:
+1. The problem with int constants is that the int gets printed, not
the name, when you dump them for debugging purposes :)
Well, it's trivial to s
On Sun, Nov 21, 2010 at 9:40 PM, Glenn Linderman wrote:
> In reviewing my notes from my experimentations with CGIHTTPServer
> (Python2.6) and then http.server (Python 3.2a4), I note one behavior I
> haven't reported as a bug, nor do I know where to start to figure it out,
> other than experimental
On Mon, 22 Nov 2010 17:08:36 +0100
Hrvoje Niksic wrote:
> On 11/22/2010 04:37 PM, Antoine Pitrou wrote:
> > +1. The problem with int constants is that the int gets printed, not
> > the name, when you dump them for debugging purposes :)
>
> Well, it's trivial to subclass int to something with a n
On Tue, Nov 23, 2010 at 2:03 AM, Alexander Belopolsky
wrote:
> On Mon, Nov 22, 2010 at 10:37 AM, Nick Coghlan wrote:
> ..
>> *(The first Google hit for "ucs2" is the UTF-16/UCS-2 article on
>> Wikipedia, the first hit for "ucs4" is the UTF-32/UCS-4 article)
>>
>
> Do you think these articles are
On 11/22/2010 04:37 PM, Antoine Pitrou wrote:
+1. The problem with int constants is that the int gets printed, not
the name, when you dump them for debugging purposes :)
Well, it's trivial to subclass int to something with a nicer __repr__.
PyGTK uses that technique for wrapping C enums:
>>
On Mon, Nov 22, 2010 at 10:37 AM, Nick Coghlan wrote:
..
> *(The first Google hit for "ucs2" is the UTF-16/UCS-2 article on
> Wikipedia, the first hit for "ucs4" is the UTF-32/UCS-4 article)
>
Do you think these articles are helpful for someone learning how to
use chr() and ord() in Python for th
On Tue, Nov 23, 2010 at 1:19 AM, Michael Foord
wrote:
> On 22/11/2010 15:14, Nick Coghlan wrote:
>> On Mon, Nov 22, 2010 at 10:54 AM, Éric Araujo wrote:
+ Possible states are:
+ GEN_CREATED: Waiting to start execution.
+ GEN_RUNNING: Currently being executed by the int
On Mon, 22 Nov 2010 15:19:04 +
Michael Foord wrote:
> On 22/11/2010 15:14, Nick Coghlan wrote:
> > On Mon, Nov 22, 2010 at 10:54 AM, Éric Araujo wrote:
> >>> +.. function:: getgeneratorstate(generator)
> >>> +
> >>> +Get current state of a generator-iterator.
> >>> +
> >>> +Possible
On Mon, Nov 22, 2010 at 10:47 PM, M.-A. Lemburg wrote:
> Please also note that we have used the terms UCS-2 and UCS-4 in Python2
> for 9+ years now and users are just starting to learn the difference
> and get acquainted with the fact that Python uses these two forms.
>
> Confronting them with "na
On 22/11/2010 15:14, Nick Coghlan wrote:
On Mon, Nov 22, 2010 at 10:54 AM, Éric Araujo wrote:
+.. function:: getgeneratorstate(generator)
+
+Get current state of a generator-iterator.
+
+Possible states are:
+ GEN_CREATED: Waiting to start execution.
+ GEN_RUNNING: Currently b
On Mon, Nov 22, 2010 at 10:54 AM, Éric Araujo wrote:
>> +.. function:: getgeneratorstate(generator)
>> +
>> + Get current state of a generator-iterator.
>> +
>> + Possible states are:
>> + GEN_CREATED: Waiting to start execution.
>> + GEN_RUNNING: Currently being executed by the in
Why don't ya'll just call them "--unichar-width=16/32". That describes
precisely what the options do, and doesn't invite any quibbling over
definitions.
James
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/py
Martin,
it is really irrelevant whether the standards have decided
to no longer use the terms UCS-2 and UCS-4 in their latest
standard documents.
The definitions still stand (just like Unicode 2.0 is still a valid
standard, even if it's ten years old):
* UCS-2 is defined as "Universal Character
Am 22.11.2010 11:48, schrieb Stephen J. Turnbull:
> Raymond Hettinger writes:
>
> > Neither UTF-16 nor UCS-2 is exactly correct anyway.
>
>>From a standards lawyer point of view, UCS-2 is exactly correct, as
> far as I can tell upon rereading ISO 10646-1, especially Annexes H
> ("retransmitting
Am 22.11.2010 11:47, schrieb Stephen J. Turnbull:
> "Martin v. Löwis" writes:
>
> > More interestingly (and to the subject) is chr: how did you arrive
> > at C9 banning Python3's definition of chr? This chr function puts
> > the code sequence into well-formed UTF-16; that's the whole point of
>
Raymond Hettinger writes:
> Neither UTF-16 nor UCS-2 is exactly correct anyway.
>From a standards lawyer point of view, UCS-2 is exactly correct, as
far as I can tell upon rereading ISO 10646-1, especially Annexes H
("retransmitting devices") and Q ("UTF-16"). Annex Q makes it clear
that UTF-16
"Martin v. Löwis" writes:
> More interestingly (and to the subject) is chr: how did you arrive
> at C9 banning Python3's definition of chr? This chr function puts
> the code sequence into well-formed UTF-16; that's the whole point of
> UTF-16.
No, it doesn't, in the specific case of surrogate
> Unicode 5.0, Chapter 3, verse C9:
>
> When a process generates a code unit sequence which purports to be
> in a Unicode character encoding form, it shall not emit ill-formed
> code sequences.
> > > A Unicode-conforming Python implementation would error at the
> > > chr() call, or
71 matches
Mail list logo
