On Sat, 23 Aug 2014 00:21:18 +0200, Oleg Broytman wrote:
>I'm involved in developing and maintaining a few big commercial
> projects that will hardly be ported to Python3. So I'm stuck with
> Python2 for many years and I haven't tried Python3. May be I should try
> a small personal project, bu
On Sat, Aug 23, 2014 at 8:26 AM, Oleg Broytman wrote:
> On Sat, Aug 23, 2014 at 07:04:20AM +1000, Chris Angelico
> wrote:
>> On Sat, Aug 23, 2014 at 6:17 AM, Glenn Linderman
>> wrote:
>> > "cp1251 of utf-8 encoding" is non-sensical. Either it is cp1251 or it is
>> > utf-8, but it is not both.
On Sat, Aug 23, 2014 at 07:04:20AM +1000, Chris Angelico
wrote:
> On Sat, Aug 23, 2014 at 6:17 AM, Glenn Linderman
> wrote:
> > "cp1251 of utf-8 encoding" is non-sensical. Either it is cp1251 or it is
> > utf-8, but it is not both. Maybe you meant "or" instead of "of".
>
> I'd assume "or" mean
On Fri, Aug 22, 2014 at 11:53:01AM -0700, Chris Barker
wrote:
> Back in the day, paths were "just strings", and that worked OK with
> py2 strings, because you could put arbitrary bytes in them. But the "py2
> strings were perfect" folks seem to not acknowledge that while they are
> nice for match
On Fri, Aug 22, 2014 at 01:17:44PM -0700, Glenn Linderman
wrote:
> >in cp1251 of utf-8 encoding
>
> "cp1251 of utf-8 encoding" is non-sensical. Either it is cp1251 or
> it is utf-8, but it is not both. Maybe you meant "or" instead of
> "of".
But of course!
Oleg.
--
Oleg Broytman
On Sat, Aug 23, 2014 at 6:17 AM, Glenn Linderman wrote:
> "cp1251 of utf-8 encoding" is non-sensical. Either it is cp1251 or it is
> utf-8, but it is not both. Maybe you meant "or" instead of "of".
I'd assume "or" meant there, rather than "of", it's a common typo.
Not sure why 1251, specifically
On Thu, Aug 21, 2014 at 7:42 PM, Oleg Broytman wrote:
> On Thu, Aug 21, 2014 at 05:30:14PM -0700, Chris Barker - NOAA Federal <
> chris.bar...@noaa.gov> wrote:
> > This brings up the other key problem. If file names are (almost)
> > arbitrary bytes, how do you write one to/read one from a text fi
On Fri, Aug 22, 2014 at 10:09 AM, Glenn Linderman
wrote:
> What encoding does have a text file (an HTML, to be precise) with
> text in utf-8, ads in cp1251 (ad blocks were included from different
> files) and comments in koi8-r?
>Well, I must admit the HTML was rather an exception, but ha
On 8/22/2014 11:50 AM, Oleg Broytman wrote:
On Fri, Aug 22, 2014 at 10:09:21AM -0700, Glenn Linderman
wrote:
On 8/22/2014 9:52 AM, Oleg Broytman wrote:
On Fri, Aug 22, 2014 at 09:37:13AM -0700, Glenn Linderman
wrote:
On 8/22/2014 8:51 AM, Oleg Broytman wrote:
What encoding does have a
On Fri, Aug 22, 2014 at 10:09:21AM -0700, Glenn Linderman
wrote:
> On 8/22/2014 9:52 AM, Oleg Broytman wrote:
> >On Fri, Aug 22, 2014 at 09:37:13AM -0700, Glenn Linderman
> > wrote:
> >>On 8/22/2014 8:51 AM, Oleg Broytman wrote:
> >>>What encoding does have a text file (an HTML, to be precis
On 8/22/2014 9:52 AM, Oleg Broytman wrote:
On Fri, Aug 22, 2014 at 09:37:13AM -0700, Glenn Linderman
wrote:
On 8/22/2014 8:51 AM, Oleg Broytman wrote:
What encoding does have a text file (an HTML, to be precise) with
text in utf-8, ads in cp1251 (ad blocks were included from different
fil
On Fri, Aug 22, 2014 at 09:37:13AM -0700, Glenn Linderman
wrote:
> On 8/22/2014 8:51 AM, Oleg Broytman wrote:
> >What encoding does have a text file (an HTML, to be precise) with
> >text in utf-8, ads in cp1251 (ad blocks were included from different
> >files) and comments in koi8-r?
> >W
On 8/22/2014 8:51 AM, Oleg Broytman wrote:
What encoding does have a text file (an HTML, to be precise) with
text in utf-8, ads in cp1251 (ad blocks were included from different
files) and comments in koi8-r?
Well, I must admit the HTML was rather an exception, but having a
text file with
ACTIVITY SUMMARY (2014-08-15 - 2014-08-22)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4621 (+19)
closed 29399 (+28)
total 34020 (+47)
Open issues wit
Hi!
On Sat, Aug 23, 2014 at 01:19:14AM +1000, Steven D'Aprano
wrote:
> On Fri, Aug 22, 2014 at 04:42:29AM +0200, Oleg Broytman wrote:
> > On Thu, Aug 21, 2014 at 05:30:14PM -0700, Chris Barker - NOAA Federal
> > wrote:
> > > This brings up the other key problem. If file names are (almost)
> >
Am 22.08.14 01:56, schrieb Glenn Linderman:
> 0 and 47 are certainly originally derived from ASCII. However, there
> could be lots of encodings that are not ASCII compatible (but in
> practice, probably very few, since most encodings _are_ ASCII
> compatible) that could be fit those constraints.
>
On Fri, Aug 22, 2014 at 04:42:29AM +0200, Oleg Broytman wrote:
> On Thu, Aug 21, 2014 at 05:30:14PM -0700, Chris Barker - NOAA Federal
> wrote:
> > This brings up the other key problem. If file names are (almost)
> > arbitrary bytes, how do you write one to/read one from a text file
> > with a pa
17 matches
Mail list logo
