On Tue, 7 Mar 2023 at 16:53, Stephen Tucker wrote:
>
> Hi again,
>
> I tried xrange, but I got an error telling me that my integer was too big
> for a C long.
>
> Clearly, xrange in Py2 is not capable of dealing with Python (that is,
> possibly very long) integers.
That's because Py2 has two diff
Hi again,
I tried xrange, but I got an error telling me that my integer was too big
for a C long.
Clearly, xrange in Py2 is not capable of dealing with Python (that is,
possibly very long) integers.
I am raising this because,
(a) IF xrange in Py3 is a simple "port" from Py2, then it won't handl
On 2023-03-02, Stephen Tucker wrote:
> The range function in Python 2.7 (and yes, I know that it is now
> superseded), provokes a Memory Error when asked to deiliver a very long
> list of values.
>
> I assume that this is because the function produces a list which it then
> iterates through.
>
> 1
On Thu, 2 Mar 2023 at 22:27, Stephen Tucker wrote:
>
> Hi,
>
> The range function in Python 2.7 (and yes, I know that it is now
> superseded), provokes a Memory Error when asked to deiliver a very long
> list of values.
>
> I assume that this is because the function produces a list which it then
>
On 2023-03-02 at 11:25:49 +,
Stephen Tucker wrote:
> The range function in Python 2.7 (and yes, I know that it is now
> superseded), provokes a Memory Error when asked to deiliver a very long
> list of values.
>
> I assume that this is because the function produces a list which it then
> ite
Ethan Furman writes:
> On 2/16/21 12:09 PM, Kevin M. Wilson via Python-list wrote:
>
>> My employer has hundreds of scripts in 2.7, but I'm writing new
>> scripts in 3.9! I'm running into 'invalid syntax' errors.I have to
>> maintain the 'Legacy' stuff, and I need to mod the path et al., to
>> ex
The best would be to upgrade the scripts, did you try them with 2to3 ? It
should do most of the work, if not all.
https://docs.python.org/3/library/2to3.html
--
https://mail.python.org/mailman/listinfo/python-list
On 2021-02-17 14:09, Thomas Jollans wrote:
On 16/02/2021 22:16, Ethan Furman wrote:
Kevin, please reply to the list (preferably Reply-to-list, or
Reply-all), that way others can chime in with help.
On 2/16/21 12:55 PM, Kevin M. Wilson wrote:
Windows 7 OS, and typically run in conjunction with
On 16/02/2021 22:16, Ethan Furman wrote:
Kevin, please reply to the list (preferably Reply-to-list, or
Reply-all), that way others can chime in with help.
On 2/16/21 12:55 PM, Kevin M. Wilson wrote:
Windows 7 OS, and typically run in conjunction with testing SSD', as
for stand alone scripts.
On 2/16/21 4:16 PM, Ethan Furman wrote:
> Kevin, please reply to the list (preferably Reply-to-list, or
> Reply-all), that way others can chime in with help.
>
> On 2/16/21 12:55 PM, Kevin M. Wilson wrote:
>
>> Windows 7 OS, and typically run in conjunction with testing SSD', as
>> for stand alone
Kevin, please reply to the list (preferably Reply-to-list, or
Reply-all), that way others can chime in with help.
On 2/16/21 12:55 PM, Kevin M. Wilson wrote:
Windows 7 OS, and typically run in conjunction with testing SSD', as for
stand alone scripts.
Those require: python BogusFile.py. I too
On 2/16/21 12:09 PM, Kevin M. Wilson via Python-list wrote:
My employer has hundreds of scripts in 2.7, but I'm writing new scripts in 3.9!
I'm running into 'invalid syntax' errors.I have to maintain the 'Legacy' stuff,
and I need to mod the path et al., to execute 3.7 w/o doing damage to the
On 2018-07-17 10:22 AM, Peter Otten wrote:
> D'Arcy Cain wrote:
>
>> I just realized that my subject was backwards. It's 2.7 that can find
>> the libs and 3.6 than cannot. Just in case that makes a difference.
>
> Not for me, I believed the pasted shell session rather then the subject
> line.
D'Arcy Cain wrote:
> I just realized that my subject was backwards. It's 2.7 that can find
> the libs and 3.6 than cannot. Just in case that makes a difference.
Not for me, I believed the pasted shell session rather then the subject
line.
--
https://mail.python.org/mailman/listinfo/python-
I just realized that my subject was backwards. It's 2.7 that can find
the libs and 3.6 than cannot. Just in case that makes a difference.
--
D'Arcy J.M. Cain
Vybe Networks Inc.
http://www.VybeNetworks.com/
IM:da...@vex.net VoIP: sip:da...@vybenetworks.com
--
https://mail.python.org/mailman/lis
nt: Friday, May 5, 2017 10:07:33 AM
To: python-list@python.org
Cc: jeff saremi
Subject: Re: Python 2.7: no such module pip
On Fri, May 5, 2017 at 4:57 PM, jeff saremi wrote:
>
> There is no such option in the installation. Please take a look at the
> screenshot I enclosed.
Sorry, I overl
On 5/5/2017 1:03 PM, jeff saremi wrote:
forgot the attachment
This is a no-attachment list
--
https://mail.python.org/mailman/listinfo/python-list
Thanks very much Eryk. I will look into WinPython. And as for the PYTHONPATH i
came up with that. I will unset it.
From: eryk sun
Sent: Thursday, May 4, 2017 10:21:20 PM
To: python-list@python.org
Cc: jeff saremi
Subject: Re: Python 2.7 on Windows: Copy&P
forgot the attachment
From: jeff saremi
Sent: Friday, May 5, 2017 9:57:30 AM
To: eryk sun; python-list@python.org
Subject: Re: Python 2.7: no such module pip
Eryk
There is no such option in the installation. Please take a look at the
screenshot I enclosed. If
module named ensurepip
From: eryk sun
Sent: Friday, May 5, 2017 9:49:18 AM
To: python-list@python.org
Cc: jeff saremi
Subject: Re: Python 2.7: no such module pip
On Fri, May 5, 2017 at 4:30 PM, jeff saremi wrote:
> i checked the installation again. There is no option to
On Fri, May 5, 2017 at 4:57 PM, jeff saremi wrote:
>
> There is no such option in the installation. Please take a look at the
> screenshot I enclosed.
Sorry, I overlooked that you said you're installing
"python-2.7.amd64.msi" -- as in 2.7.0. Please download and install
2.7.13:
https://www.python
On Fri, May 5, 2017 at 4:30 PM, jeff saremi wrote:
> i checked the installation again. There is no option to select or deselect
> PIP. I installed with everything included. No pip module is present despite
> the fact that Python documentation says that PIP is a part of Python
> installation and do
.
From: eryk sun
Sent: Thursday, May 4, 2017 9:58:40 PM
To: python-list@python.org
Cc: jeff saremi
Subject: Re: Python 2.7: no such module pip
On Thu, May 4, 2017 at 8:24 PM, jeff saremi wrote:
> Did a fresh install of python-2.7.amd64.msi on windows 10.
>
> Th
On Thu, May 4, 2017 at 8:27 PM, jeff saremi wrote:
> I have scoured the net for any hints on this. We have some prod machines
> where we're not able to run MSI installations.
> Is it possible to copy Python2.7 from say c:\Python2.7 from one machine to
> another?
> What other steps do we need bey
On Thu, May 4, 2017 at 8:24 PM, jeff saremi wrote:
> Did a fresh install of python-2.7.amd64.msi on windows 10.
>
> The install finishes with success. Python runs. No pip when the following is
> run:
>
> C:\> python -m pip install elastalert
> C:\Python27\python.exe: No module named pip
Maybe yo
On 2017-05-04 21:27, jeff saremi wrote:
I have scoured the net for any hints on this. We have some prod machines where
we're not able to run MSI installations.
Is it possible to copy Python2.7 from say c:\Python2.7 from one machine to
another?
What other steps do we need beyond the following si
On Fri, Apr 15, 2016, at 03:48 PM, a3a95797 wrote:
>
> Sirs(s)
>
> I wish to have python 2.7 on a computer. I have not been able to get a
> working copy to work on my machine. I am prepared to follow instructions
> or to pay someone to install Python on my computer. Either the Debian or
> the
a3a95797 writes:
> I wish to have python 2.7 on a computer. I have not been able to get a
> working copy to work on my machine.
Welcome! Thank you for learning Python.
Please be aware that Python 2.7 is a dead end today. It will never get
any new features, and only bug fixes will ever be made.
On Sat, Apr 16, 2016 at 8:48 AM, a3a95797 wrote:
>
> Sirs(s)
>
> I wish to have python 2.7 on a computer. I have not been able to get a
> working copy to work on my machine. I am prepared to follow instructions or
> to pay someone to install Python on my computer. Either the Debian or the
>
On Saturday, August 15, 2015 at 2:36:44 AM UTC-4, Adam Meily wrote:
> I am working on a CPython library that serializes Python objects to disk in a
> custom format. I'm using _PyLong_NumBits() to determine whether
> PyLong_AsLong(), PyLong_AsUnsignedLong(), PyLong_AsLongLong(), or
> PyLong_AsUns
On Wed, Mar 25, 2015 at 10:44 AM, Ian Kelly wrote:
> On Wed, Mar 25, 2015 at 8:36 AM, Larry Martell
> wrote:
>> On Wed, Mar 25, 2015 at 8:26 AM, Grant Edwards
>> wrote:
>>> On 2015-03-25, Larry Martell wrote:
I have an app that works with 2.6, but in 2.7 it is failing. I traced
it d
On Wed, Mar 25, 2015 at 8:36 AM, Larry Martell wrote:
> On Wed, Mar 25, 2015 at 8:26 AM, Grant Edwards
> wrote:
>> On 2015-03-25, Larry Martell wrote:
>>> I have an app that works with 2.6, but in 2.7 it is failing. I traced
>>> it down to an issue with decimal.Decimal being passed a value of 0
On 25/03/2015 14:29, Oscar Benjamin wrote:
> On 25 March 2015 at 14:20, Larry Martell wrote:
>> I have an app that works with 2.6, but in 2.7 it is failing. I traced
>> it down to an issue with decimal.Decimal being passed a value of 0.0.
>> It 2.6 this is fine, but in 2.7 it throws an exception:
On Wed, Mar 25, 2015 at 8:26 AM, Grant Edwards wrote:
> On 2015-03-25, Larry Martell wrote:
>> I have an app that works with 2.6, but in 2.7 it is failing. I traced
>> it down to an issue with decimal.Decimal being passed a value of 0.0.
>> It 2.6 this is fine, but in 2.7 it throws an exception:
On 25 March 2015 at 14:20, Larry Martell wrote:
> I have an app that works with 2.6, but in 2.7 it is failing. I traced
> it down to an issue with decimal.Decimal being passed a value of 0.0.
> It 2.6 this is fine, but in 2.7 it throws an exception:
>
> TypeError: Cannot convert float to Decimal.
On 2015-03-25, Larry Martell wrote:
> I have an app that works with 2.6, but in 2.7 it is failing. I traced
> it down to an issue with decimal.Decimal being passed a value of 0.0.
> It 2.6 this is fine, but in 2.7 it throws an exception:
>
> TypeError: Cannot convert float to Decimal. First conve
Ok, and just tested MySQLdb connection to both XAMPP server instance on
same machine, as well as slightly remote connection to other machine over
wifi, and same error - so, seems issue is invoked/caused by MySQLdb
connection closing - if just put process to sleep for 30 seconds, nothing
happens
"Jacob Kruger"
To: "Dennis Lee Bieber"
Cc:
Sent: Tuesday, January 13, 2015 8:37 PM
Subject: Re: Python 2.7, on windows7 64 bit development machine,
inconsistent issue on similar machines
See answers below.
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants t
See answers below.
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."
- Original Message -
From: "Dennis Lee Bieber"
The very first hit /I/ get is:
https://social.technet.microsoft.com/Forums/windows/en-US/3932e3eb-c034-4eb
On Tue, Dec 30, 2014 at 5:34 PM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
>> Are .pyc files compatible across revisions? Could I carry this file to
>> a 2.7.9 and see if the crash still happens?
>
> PEP 6 requires that .pyc files for a particular major release mus
On Mon, Dec 29, 2014 at 11:34 PM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
>> Are .pyc files compatible across revisions? Could I carry this file to
>> a 2.7.9 and see if the crash still happens?
>
> PEP 6 requires that .pyc files for a particular major release mu
On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
> Are .pyc files compatible across revisions? Could I carry this file to
> a 2.7.9 and see if the crash still happens?
PEP 6 requires that .pyc files for a particular major release must
work with all the bug fix releases for that version.
--
On Tue, Dec 30, 2014 at 12:40 PM, Steven D'Aprano
wrote:
> Chris Angelico wrote:
>
>> Unlike playing with sre_constants.pyc, this one *does* result in a
>> different file after renaming away the .pyc. So somehow, SOMEHOW, the
>> .pyc file became corrupt. Is this something worth reporting? I now
>>
Chris Angelico wrote:
> Unlike playing with sre_constants.pyc, this one *does* result in a
> different file after renaming away the .pyc. So somehow, SOMEHOW, the
> .pyc file became corrupt. Is this something worth reporting? I now
> have what appears to be a file whose presence in the current dir
Chris Angelico wrote:
On Tue, Dec 30, 2014 at 7:17 AM, Ian Kelly wrote:
You could try renaming the .pyc instead of deleting it.
Hmm, and in doing so I just learned that they don't, after all, have
any sort of timestamp in them - I thought they did.
I think it contains the timestamp of the
On Tue, Dec 30, 2014 at 5:58 AM, Peter Otten <__pete...@web.de> wrote:
> OK. sre_constants.py looks pretty generic, the only module it imports (_sre)
> is a built-in and the interpreter is known-good. If the modules imported
> before sre_constants.py are known-good, too, and no other debian user se
On Tue, Dec 30, 2014 at 7:17 AM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 9:28 AM, Chris Angelico wrote:
>> Why is sre_constants segfaulting?! It's such a simple file! I assume
>> the "matches" comment means it thinks there's no problem with the .pyc
>> file; is it possible that, despite those
On Mon, Dec 29, 2014 at 9:28 AM, Chris Angelico wrote:
> Why is sre_constants segfaulting?! It's such a simple file! I assume
> the "matches" comment means it thinks there's no problem with the .pyc
> file; is it possible that, despite those checks, there's an issue
> there? I could delete the .py
Chris Angelico wrote:
> On Tue, Dec 30, 2014 at 4:28 AM, Peter Otten <__pete...@web.de> wrote:
>> Maybe the interpreter itself is corrupted? Google suggests that debsums
>> may be the tool to find out.
>
> That's part of what I'm trying to track down, but why it should have
> changed in the past
On Tue, Dec 30, 2014 at 4:28 AM, Peter Otten <__pete...@web.de> wrote:
> Maybe the interpreter itself is corrupted? Google suggests that debsums may
> be the tool to find out.
That's part of what I'm trying to track down, but why it should have
changed in the past few days is beyond me. There's no
Chris Angelico wrote:
> On Tue, Dec 30, 2014 at 3:05 AM, Irmen de Jong
> wrote:
>> On 29-12-2014 15:33, Chris Angelico wrote:
>>
>>> So clearly an empty 'site' can be imported safely, but running Python
>>> without -S segfaults.
>>>
>>> Can anyone advise as to where I should look for the cause of
On Tue, Dec 30, 2014 at 3:05 AM, Irmen de Jong wrote:
> On 29-12-2014 15:33, Chris Angelico wrote:
>
>> So clearly an empty 'site' can be imported safely, but running Python
>> without -S segfaults.
>>
>> Can anyone advise as to where I should look for the cause of the trouble?
>>
>> ChrisA
>
> Pe
On Tue, Dec 30, 2014 at 2:57 AM, Dave Angel wrote:
> My gut feeling is you should check if there is another site.py* anywhere on
> your system. (Use find rather than just manually checking the sys.path
> locations)
I used imp.find_module and it showed the one in
/usr/lib/python2.7/site.py would
On 29-12-2014 15:33, Chris Angelico wrote:
> So clearly an empty 'site' can be imported safely, but running Python
> without -S segfaults.
>
> Can anyone advise as to where I should look for the cause of the trouble?
>
> ChrisA
Perhaps starting python with -v provides some more info on when exa
On 12/29/2014 09:33 AM, Chris Angelico wrote:
rosuav@sikorsky:~$ python -S
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
[GCC 4.7.2] on linux2
rosuav@sikorsky:~$ python
Segmentation fault
This is the system Python on Debian Wheezy, and I haven't changed
site.py at all. This broke some time in
Hi Peter Otten
re:
There is no assignment
soup_atag = whatever
but there is one to atag. The whole session should when you omit the
offending line
> atag = soup_atag.a
or insert
soup_atag = soup
before it.
-
On Tue, Nov 25, 2014 at 10:56 PM, Steven D'Aprano
wrote:
> I think this conversation is going nowhere, so it's probably best to end it.
\0
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
Marko Rauhamaa wrote:
> Steven D'Aprano :
>
>> Marko Rauhamaa wrote:
>>
Py3's byte strings are still strings, though.
>>>
>>> Hm. I don't think so. In a plain English sense, maybe, but that kind of
>>> usage can lead to confusion.
>>
>> Only if you are determined to confuse yourself.
>>
>>
Steven D'Aprano :
> Marko Rauhamaa wrote:
>
>>> Py3's byte strings are still strings, though.
>>
>> Hm. I don't think so. In a plain English sense, maybe, but that kind of
>> usage can lead to confusion.
>
> Only if you are determined to confuse yourself.
>
> {...]
>
> In Python usage, "string" a
On Tue, Nov 25, 2014 at 9:56 AM, Steven D'Aprano
wrote:
> In all cases apart from an explicit "byte string", the word "string" is
> always used for the native array-of-characters type delimited by plain
> quotation marks, as used for error messages, user prompts, etc., regardless
> whether the imp
Marko Rauhamaa wrote:
>> Py3's byte strings are still strings, though.
>
> Hm. I don't think so. In a plain English sense, maybe, but that kind of
> usage can lead to confusion.
Only if you are determined to confuse yourself.
People are quite capable of interpreting correctly sentences like:
"
Chris Angelico :
> Py3's byte strings are still strings, though.
Hm. I don't think so. In a plain English sense, maybe, but that kind of
usage can lead to confusion.
For example,
A subscription selects an item of a sequence (string, tuple or list)
or mapping (dictionary) object:
subsc
On Mon, Nov 24, 2014 at 5:57 PM, Marko Rauhamaa wrote:
> Yes, people call strings "Unicdoe strings" because Python2 *did have*
> unicode strings separate from regular strings:
>
> Python2Python3
> --
> string bytes (byte strin
Gregory Ewing :
> Marko Rauhamaa wrote:
>> Unicode strings is not wrong but the technical emphasis on Unicode is as
>> strange as a "tire car" or "rectangular door" when "car" and "door" are
>> what you usually mean.
>
> The reason Unicode gets emphasised so much is that until relatively
> recently
On Sun, Nov 23, 2014, at 15:31, Dave Angel wrote:
> I didn't realize Windows shell (DOS box) had that bug. Course I don't
> use Windows much the last few years.
>
> it's one thing to not display it properly. It's quite another to supply
> faulty data to the clipboard. Especially since the Win
On Mon, Nov 24, 2014 at 9:51 AM, Gregory Ewing
wrote:
> Marko Rauhamaa wrote:
>>
>> Unicode strings is not wrong but the technical emphasis on Unicode is as
>> strange as a "tire car" or "rectangular door" when "car" and "door" are
>> what you usually mean.
>
>
> The reason Unicode gets emphasised
Marko Rauhamaa wrote:
Unicode strings is not wrong but the technical emphasis on Unicode is as
strange as a "tire car" or "rectangular door" when "car" and "door" are
what you usually mean.
The reason Unicode gets emphasised so much is that
until relatively recently, it *wasn't* what "string"
u
On Mon, Nov 24, 2014 at 7:31 AM, Dave Angel wrote:
> On 11/23/2014 01:13 PM, random...@fastmail.us wrote:
>>
>> On Sun, Nov 23, 2014, at 11:33, Dennis Lee Bieber wrote:
>>>
>>> Why would that be possible? Many truetype fonts only supply
>>> glyphs for
>>> single-byte encodings (ISO-Latin-1
On 11/23/2014 01:13 PM, random...@fastmail.us wrote:
On Sun, Nov 23, 2014, at 11:33, Dennis Lee Bieber wrote:
Why would that be possible? Many truetype fonts only supply glyphs for
single-byte encodings (ISO-Latin-1, for example -- pop up the Windows
character map utility and see what so
On Sun, Nov 23, 2014, at 11:33, Dennis Lee Bieber wrote:
> Why would that be possible? Many truetype fonts only supply glyphs for
> single-byte encodings (ISO-Latin-1, for example -- pop up the Windows
> character map utility and see what some of the font files contain.
With a bitmap font se
On Mon, Nov 24, 2014 at 3:33 AM, Dennis Lee Bieber
wrote:
> On Sat, 22 Nov 2014 20:52:37 -0500, random...@fastmail.us declaimed the
> following:
>
>>On Sat, Nov 22, 2014, at 18:38, Mark Lawrence wrote:
>>> ...
>>> That is a standard Windows build. He is again conflating problems with
>>> using the
On Sun, Nov 23, 2014 at 5:17 PM, Steven D'Aprano
wrote:
> If Python treated the character set as an implementation detail, the
> programmer would have no way of knowing whether
>
> s = u"ö"
>
> is legal or not, since you cannot know whether or not ö is a supported
> character in the running Python
random...@fastmail.us wrote:
> On Fri, Nov 21, 2014, at 23:38, Steven D'Aprano wrote:
>> I really don't understand what bothers you about this. In Python, we have
>> Unicode strings and byte strings. In computing in general, strings can
>> consist of Unicode characters, ASCII characters, Tron char
On Sat, Nov 22, 2014, at 21:11, Chris Angelico wrote:
> Is that true? Does WriteConsoleW support every Unicode character? It's
> not obvious from the docs whether it uses UCS-2 or UTF-16 (or maybe
> something else).
I was defining "every unicode character" loosely. There are certainly
display prob
On Sun, Nov 23, 2014 at 12:52 PM, wrote:
> On Sat, Nov 22, 2014, at 18:38, Mark Lawrence wrote:
>> ...
>> That is a standard Windows build. He is again conflating problems with
>> using the Windows command line for a given code page with the FSR.
>
> The thing is, with a truetype font selected, a
On Sat, Nov 22, 2014, at 18:38, Mark Lawrence wrote:
> ...
> That is a standard Windows build. He is again conflating problems with
> using the Windows command line for a given code page with the FSR.
The thing is, with a truetype font selected, a correctly written win32
console problem should be
On Fri, Nov 21, 2014, at 23:38, Steven D'Aprano wrote:
> I really don't understand what bothers you about this. In Python, we have
> Unicode strings and byte strings. In computing in general, strings can
> consist of Unicode characters, ASCII characters, Tron characters, EBCDID
> characters, ISO-88
On 22/11/2014 22:31, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 9:04 AM, Mark Lawrence wrote:
My favourite "find thousand and one ways to make Python crashing or
failing." but I don't recall a single bug report in the last two years from
anybody regarding problems with the FSR, or have I mis
On Sun, Nov 23, 2014 at 9:04 AM, Mark Lawrence wrote:
> My favourite "find thousand and one ways to make Python crashing or
> failing." but I don't recall a single bug report in the last two years from
> anybody regarding problems with the FSR, or have I missed something?
What you've missed is th
On 22/11/2014 20:17, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 5:17 AM, Mark Lawrence wrote:
Please don't feed him. Your average troll is bad enough but he really takes
the biscuit.
... someone was feeding him biscuits?
ChrisA
Surely it's better than feeding him unicode?
As I needed
On Sun, Nov 23, 2014 at 5:17 AM, Mark Lawrence wrote:
> Please don't feed him. Your average troll is bad enough but he really takes
> the biscuit.
... someone was feeding him biscuits?
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
On 22/11/2014 17:49, Marko Rauhamaa wrote:
wxjmfa...@gmail.com:
- By chance, I found on the web a German py dev who was commenting and
he had not an updated "DUDEN" (a German dictionnary).
That... leaves me utterly speachless!
Marko
Please don't feed him. Your average troll is bad enoug
wxjmfa...@gmail.com:
> - By chance, I found on the web a German py dev who was commenting and
> he had not an updated "DUDEN" (a German dictionnary).
That... leaves me utterly speachless!
Marko
--
https://mail.python.org/mailman/listinfo/python-list
On Saturday, November 22, 2014 8:14:15 PM UTC+5:30, Roy Smith wrote:
> Marko Rauhamaa wrote:
>
> > Steven D'Aprano:
> >
> > > You haven't given any good reason for objecting to calling Unicode
> > > strings by what they are. Maybe you think that it is an implementation
> > > detail, and that som
Roy Smith :
> For that matter, we will eventually get to the point where when people
> say, "just plain text", they will mean Unicode, in the same way that
> "just plain text" today really means ASCII (and the text/plain MIME
> type will become a historical curiosity).
MIME has:
Content-Type:
In article <87y4r348uf@elektro.pacujo.net>,
Marko Rauhamaa wrote:
> Steven D'Aprano :
>
> > You haven't given any good reason for objecting to calling Unicode
> > strings by what they are. Maybe you think that it is an implementation
> > detail, and that some version of Python might suddenl
Steven D'Aprano :
> You haven't given any good reason for objecting to calling Unicode
> strings by what they are. Maybe you think that it is an implementation
> detail, and that some version of Python might suddenly and without
> warning change to only supporting KOI8-R strings or GB2312 strings?
On Sun, Nov 23, 2014 at 12:50 AM, Steven D'Aprano
wrote:
> "Tire car" makes no sense. "Rectangular door" makes perfect sense, and in a
> world where there are dozens of legacy non-rectangular doors, it would be
> very sensible to specify the kind of door. Just as we specify sliding door,
> glass d
Marko Rauhamaa wrote:
> Steven D'Aprano :
>
>> In Python, we have Unicode strings and byte strings.
>
> No, you don't. You have strings and bytes:
Python has strings of Unicode code points, a.k.a. "Unicode strings",
or "text strings", and strings of bytes, a.k.a. "byte strings". These are
the p
Steven D'Aprano :
> In Python, we have Unicode strings and byte strings.
No, you don't. You have strings and bytes:
Textual data in Python is handled with str objects, or strings.
Strings are immutable sequences of Unicode code points. String
literals are written in a variety of ways: [...
Marko Rauhamaa wrote:
> Rustom Mody :
>
>> Likewise in 2014, and given the arguments, inconsistencies, etc
>> remembering the nuts-n-bolts below the strings-represented-as-unicode
>> abstraction may be in order.
>
> No need to hide Unicode, but talking about a
>
>Unicode string
>
> is like
On Sat, Nov 22, 2014 at 3:36 AM, Marko Rauhamaa wrote:
> No need to hide Unicode, but talking about a
>
>Unicode string
>
> is like talking about an
>
>electronic computer
>
>visible spectrum display
>
>mouse user interface
>
>ethernet socket
>
>magnetic file
>
>electri
Rustom Mody :
> Likewise in 2014, and given the arguments, inconsistencies, etc
> remembering the nuts-n-bolts below the strings-represented-as-unicode
> abstraction may be in order.
No need to hide Unicode, but talking about a
Unicode string
is like talking about an
electronic computer
On Sat, Nov 22, 2014 at 3:11 AM, Francis Moreau wrote:
> Yes I finally used str() since only setlocale() reported to have some
> issues with unicode_literals active in my appliction.
>
> Thanks Chris for your useful insight.
My pleasure. Unicode is a bit of a hobby-horse of mine, so I'm always
ha
On 11/20/2014 04:15 PM, Chris Angelico wrote:
> On Fri, Nov 21, 2014 at 1:14 AM, Francis Moreau
> wrote:
>> Hi,
>>
>> Thanks for the "from __future__ import unicode_literals" trick, it makes
>> that switch much less intrusive.
>>
>> However it seems that I will suddenly be trapped by all modules
On Friday, November 21, 2014 12:06:54 PM UTC+5:30, Marko Rauhamaa wrote:
> Chris Angelico :
>
> > On Fri, Nov 21, 2014 at 5:56 AM, Marko Rauhamaa wrote:
> >> I don't really like it how Unicode is equated with text, or even
> >> character strings.
> > [...]
> > Do you have actual text that you're
On 2014-11-22 02:23, Steven D'Aprano wrote:
> LATIN SMALL LETTER E
> COMBINING CIRCUMFLEX ACCENT
>
> then my application should treat that as a single "character" and
> display it as:
>
> LATIN SMALL LETTER E WITH CIRCUMFLEX
>
> which looks like this: ê
>
> rather than two distinct "characters"
On Sat, Nov 22, 2014 at 2:23 AM, Steven D'Aprano
wrote:
> Chris Angelico wrote:
>
>> On Fri, Nov 21, 2014 at 11:32 AM, Steven D'Aprano
>> wrote:
>>> (E.g. there are millions of existing files across the world containing
>>> text which use legacy encodings that are not compatible with Unicode.)
>>
Chris Angelico wrote:
> On Fri, Nov 21, 2014 at 11:32 AM, Steven D'Aprano
> wrote:
>> (E.g. there are millions of existing files across the world containing
>> text which use legacy encodings that are not compatible with Unicode.)
>
> Not compatible with Unicode? There aren't many character sets
On Fri, Nov 21, 2014 at 7:16 PM, Marko Rauhamaa wrote:
> Chris Angelico :
>
>> Then you need to read more about Unicode. The *codepoint* for the
>> letter 'A' is 65. That is not Unicode, that is one part of the Unicode
>> spec.
>
> I don't think Python users need to know anything more about Unicod
1 - 100 of 238 matches
Mail list logo
