On Fri, 18 Jan 2019, Gene Heskett wrote:
I had one client, a hedge fund, that I fixed literally 1000's of Y2K
issues for. When Y2K came and there were no problems, the owner said
to me "You made such a big deal about the Y2K thing, and nothing
happened." --
I would quite cheerfully have
m, may need to start newer programs that use
> the 3.X or beyond version as no back-ported version exists. The bubble
> may enlarge and may eventually burst.
>
> -Original Message-----
> From: Python-list
> On Behalf Of
> Larry Martell
> Sent: Friday, January 18, 2019 10
and communicate with them, may need to
> start newer programs that use the 3.X or beyond version as no back-ported
> version exists. The bubble may enlarge and may eventually burst.
>
> -Original Message-
> From: Python-list On
> Behalf Of Larry Martell
> Sent:
, 2019 10:47 AM
To: Python
Subject: Re: Pythonic Y2K
On Fri, Jan 18, 2019 at 10:43 AM Michael Torrie wrote:
>
> On 01/16/2019 12:02 PM, Avi Gross wrote:
> > I recall the days before the year 2000 with the Y2K scare when
> > people worried that legacy software might
nguage than the
more modern python, fine.
-Original Message-
From: Python-list On
Behalf Of Michael Torrie
Sent: Friday, January 18, 2019 10:36 AM
To: python-list@python.org
Subject: Re: Pythonic Y2K
On 01/16/2019 12:02 PM, Avi Gross wrote:
> I recall the days before the year 200
On 17/01/2019 02:34, Avi Gross wrote:
but all it took was to set the clock forward on a test system and
look for anomalies.
You're new to programming or you're not very old and certainly haven't
run much pre-Y2k software. ;-)
Issues that needed solving:
2 digits only for the date
use
On 2019-01-18, Dennis Lee Bieber wrote:
> Hey... I'm still waiting for a novelization of the TRS-DOS date "bug".
> TRS-DOS directory structure only allocated 3-bits for the year.
Three bits for the year? they didn't expect those computers to last
long, eh?
[My current Thinkpad is over
Torrie
Sent: Friday, January 18, 2019 10:36 AM
To: python-list@python.org
Subject: Re: Pythonic Y2K
On 01/16/2019 12:02 PM, Avi Gross wrote:
> I recall the days before the year 2000 with the Y2K scare when people
> worried that legacy software might stop working or do horrible things once
>
On Fri, Jan 18, 2019 at 10:43 AM Michael Torrie wrote:
>
> On 01/16/2019 12:02 PM, Avi Gross wrote:
> > I recall the days before the year 2000 with the Y2K scare when people
> > worried that legacy software might stop working or do horrible things once
> > the clock turned. It may even have been
On 01/16/2019 12:02 PM, Avi Gross wrote:
> I recall the days before the year 2000 with the Y2K scare when people
> worried that legacy software might stop working or do horrible things once
> the clock turned. It may even have been scary enough for some companies to
> rewrite key applications and
On Behalf Of
Avi Gross
Sent: Thursday, January 17, 2019 5:46 PM
To: python-list@python.org
Subject: RE: Pythonic Y2K
Ian,
You just scared me. It is 2019 which has four digits. In less than 8,000
years we will need to take the fifth to make numbers from 10,000 to 10,999.
90,000 years later we
Back in the computer world, Y2K gave such managers some cover. There was a
FIRM deadline. I wonder how many used the impending arrival of the year 2000
as an excuse to perhaps clean up other parts of their act and charge it to
prevention. I mean they might suggest they rewrite some legacy COBOL
in 2000 B.C.
-Original Message-
From: Python-list On
Behalf Of Ian Kelly
Sent: Thursday, January 17, 2019 2:14 PM
To: Python
Subject: Re: Pythonic Y2K
On Wed, Jan 16, 2019 at 9:57 PM Avi Gross wrote:
>
> The forthcoming UNIX 2038 problem will, paradoxically happen on
> Janu
for 2020.
-Original Message-
From: Python-list On
Behalf Of Schachner, Joseph
Sent: Thursday, January 17, 2019 1:46 PM
To: Python
Subject: RE: Pythonic Y2K
I'd like to add one more thing to your list of what companies will have to
consider:
6) The ability to hire and retain employees who
On Fri, Jan 18, 2019 at 8:47 AM DL Neil wrote:
>
> On 17/01/19 6:53 PM, Chris Angelico wrote:
> > On Thu, Jan 17, 2019 at 3:55 PM Avi Gross wrote:
> >> The forthcoming UNIX 2038 problem will, paradoxically happen on January 19.
> >>
> >
> > Paradoxically? What do you mean by that?
>
>
> First we
On 17/01/19 6:53 PM, Chris Angelico wrote:
On Thu, Jan 17, 2019 at 3:55 PM Avi Gross wrote:
The forthcoming UNIX 2038 problem will, paradoxically happen on January 19.
Paradoxically? What do you mean by that?
First we had to duck the Y2K problem.
By moving everything to 64-bits, we duck
On 2019-01-17, Schachner, Joseph wrote:
> I'd like to add one more thing to your list of what companies will have to
> consider:
>
> 6) The ability to hire and retain employees who will be happy to
>program in an obsolete version of Python. A version about which
>new books will probably
On Wed, Jan 16, 2019 at 9:57 PM Avi Gross wrote:
>
> The forthcoming UNIX 2038 problem will, paradoxically happen on January
19. I wonder what they will do long before then. Will they just add a byte
or four or 256 and then make a date measurable in picoseconds? Or will they
start using a number
On Fri, Jan 18, 2019 at 5:48 AM Schachner, Joseph
wrote:
>
> I'd like to add one more thing to your list of what companies will have to
> consider:
>
> 6) The ability to hire and retain employees who will be happy to program in
> an obsolete version of Python. A version about which new books
: Chris Angelico
Sent: Wednesday, January 16, 2019 2:15 PM
To: Python
Subject: Re: Pythonic Y2K
On Thu, Jan 17, 2019 at 6:04 AM Avi Gross wrote:
>
> I see messages like the following where someone is still asking how to
> do something in some version of python 2.X.
>
> I recall
On Thu, Jan 17, 2019 at 3:55 PM Avi Gross wrote:
> The forthcoming UNIX 2038 problem will, paradoxically happen on January 19.
>
Paradoxically? What do you mean by that?
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
ssage-
From: Python-list On
Behalf Of DL Neil
Sent: Wednesday, January 16, 2019 11:04 PM
To: Python
Subject: Re: Pythonic Y2K
On 17/01/19 4:45 PM, Larry Martell wrote:
> On Wed, Jan 16, 2019 at 9:35 PM Avi Gross wrote:
>>
>> Chris,
>>
>> The comparison to Y2K wa
one way, it is great.
If you want them to be able to read existing code and modify it, it can be a
headache especially when people abuse language features. And yes, I am an
abuser in that sense.
-Original Message-
From: Python-list On
Behalf Of Larry Martell
Sent: Wednesday, January 16, 2
On 17/01/19 4:45 PM, Larry Martell wrote:
On Wed, Jan 16, 2019 at 9:35 PM Avi Gross wrote:
Chris,
The comparison to Y2K was not a great one. I am not sure what people did in
advance, but all it took was to set the clock forward on a test system and
look for anomalies. Not everything would be
On Wed, Jan 16, 2019 at 9:35 PM Avi Gross wrote:
>
> Chris,
>
> The comparison to Y2K was not a great one. I am not sure what people did in
> advance, but all it took was to set the clock forward on a test system and
> look for anomalies. Not everything would be found but it gave some hints.
To: Python
Subject: Re: Pythonic Y2K
On Thu, Jan 17, 2019 at 6:04 AM Avi Gross wrote:
>
> I see messages like the following where someone is still asking how to
> do something in some version of python 2.X.
>
> I recall the days before the year 2000 with the Y2K scare when pe
On Thu, Jan 17, 2019 at 6:04 AM Avi Gross wrote:
>
> I see messages like the following where someone is still asking how to do
> something in some version of python 2.X.
>
> I recall the days before the year 2000 with the Y2K scare when people
> worried that legacy software might stop working or
27 matches
Mail list logo
