On Fri, 27 May 2016 04:10 pm, Marko Rauhamaa wrote:
> Steven D'Aprano :
>> This concept of ASCII = "all character sets", or "nearly all", or
>> "okay, maybe not nearly all of them, but just the important ones" is
>> terribly Euro-centric. The very idea would be laughable in Japan and
>> other East
Steven D'Aprano :
> This concept of ASCII = "all character sets", or "nearly all", or
> "okay, maybe not nearly all of them, but just the important ones" is
> terribly Euro-centric. The very idea would be laughable in Japan and
> other East Asian countries, where Shift-JIS and Big5 still dominate.
Erik writes:
> On 26/05/16 08:21, Jussi Piitulainen wrote:
>> UTF-8 ASCII is nice
>>
>> UTF-16 ASCII is weird.
>
> I am dumbstruck.
I'm joking, of course.
But those statements do make sense when one knows to distinguish a
character set from its encoding as bytes, and then the UTF-8 encoding of
A
On Fri, 27 May 2016 07:12 am, Marko Rauhamaa wrote:
> However, I must correct myself slightly: ASCII refers to any
> byte-oriented character encoding scheme *largely coinciding with ASCII
> proper*. But since all of them *are* derivatives of ASCII proper,
> mentioning is somewhat redundant.
"All"
On 05/26/2016 05:57 PM, Michael Torrie wrote:
> You could try emailing the author who's email address is listed on the
> project's main github page. I suspect the project itself is abandoned.
Ahem. That should have been whose. Sigh.
--
https://mail.python.org/mailman/listinfo/python-list
On 05/26/2016 11:31 AM, Sean Son wrote:
> Hopefully those help in any troubleshooting steps that you all recommend to
> me!
>
> Thank you!
You could try emailing the author who's email address is listed on the
project's main github page. I suspect the project itself is abandoned.
Was this worki
Erik :
> On 26/05/16 10:20, Marko Rauhamaa wrote:
>> ASCII has taken new meanings. For most coders, in relaxed style, it
>> refers to any byte-oriented character encoding scheme. In C terms,
>>
>> ASCII == char *
>
> Is this really true? So by "taken new meanings" you are saying that it
> has
On 26/05/16 08:21, Jussi Piitulainen wrote:
UTF-8 ASCII is nice
UTF-16 ASCII is weird.
I am dumbstruck.
E.
--
https://mail.python.org/mailman/listinfo/python-list
On 26/05/16 10:20, Marko Rauhamaa wrote:
ASCII has taken new meanings. For most coders, in relaxed style, it
refers to any byte-oriented character encoding scheme. In C terms,
ASCII == char *
Is this really true? So by "taken new meanings" you are saying that it
has actually lost all mea
Here are the links to the other scripts mentioned in the error messages:
https://github.com/mz/androwarn/blob/master/androwarn/search/malicious_behaviours/device_settings.py
https://github.com/mz/androwarn/blob/master/androwarn/analysis/analysis.py
and the main androwarn.py script:
http
Hello all
>From what I can tell from the error message that I received, line 257 of
the util.py script is causing the error. Here is a link to this script:
https://github.com/mz/androwarn/blob/master/androwarn/util/util.py
I am not a python developer myself, unfortunately, so I have no idea
On 26/05/2016 15:31, alex wright wrote:
From the link:
"If you are a woman, know English and have a laptop you can apply for a
pass!"
So it would appear so.
On Thu, May 26, 2016 at 5:39 AM, Karim wrote:
On 26/05/2016 10:58, M.-A. Lemburg wrote:
We’re pleased to announce a Django Girls
From the link:
"If you are a woman, know English and have a laptop you can apply for a
pass!"
So it would appear so.
On Thu, May 26, 2016 at 5:39 AM, Karim wrote:
>
>
> On 26/05/2016 10:58, M.-A. Lemburg wrote:
>
>> We’re pleased to announce a Django Girls workshop on Sunday, July 17,
>> the f
thank you
On Thu, May 26, 2016 at 2:00 AM, wrote:
> Send Python-list mailing list submissions to
> python-list@python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/python-list
> or, via email, send a message with subj
On Thursday, May 26, 2016 at 1:41:41 PM UTC+5:30, Erik wrote:
> On 26/05/16 02:28, Dennis Lee Bieber wrote:
> > On Wed, 25 May 2016 22:03:34 +0100, Erik
> > declaimed the following:
> >
> >> Indeed - at that time, I was working with COBOL on an IBM S/370. On that
> >> system, we used EBCDIC ASCII.
On 26/05/2016 10:58, M.-A. Lemburg wrote:
We’re pleased to announce a Django Girls workshop on Sunday, July 17,
the first day of the EuroPython 2016 conference.
If you want participate or know someone who’d like to join, please
fill in our application form on the Django Girls’ website:
Erik :
> To break it down, Stephen was making the observation that people call
> all sorts of extended ASCII encodings (including proprietary things)
> "ASCII". So I took it to the extreme and called something that had
> nothing to do with ASCII a type of ASCII.
ASCII has taken new meanings. For
On Thu, May 26, 2016 at 7:11 PM, Marko Rauhamaa wrote:
> Python didn't come out unscathed, either. Multithreading is being
> replaced with asyncio
Incorrect. Threading is still important - it's not being replaced.
Asynchronous code support is being added to an existing pool of
multiprocessing tec
Jussi Piitulainen :
> UTF-16 ASCII is weird. Wierd. Probably all right in an environment
> that is otherwise set to use UTF-16.
>
> Nothing is as weird as a mix of different encodings of a foreign
> script in the same "plain text" file, said to be "Unicode".
Some children are just born under unl
Rustom Mody :
> On Wednesday, May 25, 2016 at 4:18:02 PM UTC+5:30, Marko Rauhamaa wrote:
>> Christopher Reimer:
>>
>> > Back in the early 1980's, I grew up on 8-bit processors and latin-1 was
>> > all we had for ASCII.
>>
>> You really were very advanced. According to > https://en.wikipedia.org/
We’re pleased to announce a Django Girls workshop on Sunday, July 17,
the first day of the EuroPython 2016 conference.
If you want participate or know someone who’d like to join, please
fill in our application form on the Django Girls’ website:
*** Django Girls EuroPython 2016 *
On 26/05/16 02:28, Dennis Lee Bieber wrote:
On Wed, 25 May 2016 22:03:34 +0100, Erik
declaimed the following:
Indeed - at that time, I was working with COBOL on an IBM S/370. On that
system, we used EBCDIC ASCII. That was the wierdest ASCII of all ;)
It would have to be... Extended
On Thursday, May 26, 2016 at 12:24:28 PM UTC+5:30, Jussi Piitulainen wrote:
> Rustom Mody writes:
>
> > On Wednesday, May 25, 2016 at 4:18:02 PM UTC+5:30, Marko Rauhamaa wrote:
> ...
> >> instead of ASCII, national 7-bit character set variants were being
> >> used. For example, you might see Pasc
On Thursday, May 26, 2016 at 12:52:09 PM UTC+5:30, Jussi Piitulainen wrote:
> UTF-16 ASCII is weird. Wierd. Probably all right in an environment that
> is otherwise set to use UTF-16.
In http://blog.languager.org/2015/03/whimsical-unicode.html
are some examples of why UTF-16 is bug-inviting
[ sect
Erik writes:
> On 25/05/16 11:19, Steven D'Aprano wrote:
>> On Wednesday 25 May 2016 19:10, Christopher Reimer wrote:
>>
>>> Back in the early 1980's, I grew up on 8-bit processors and latin-1
>>> was all we had for ASCII.
>>
>> It really, truly wasn't. But you can be forgiven for not knowing
>> t
25 matches
Mail list logo
