On Thu, Aug 06, 2020 at 07:46:25PM -0500, Python wrote:
> On Thu, Aug 06, 2020 at 07:19:01PM -0500, Skip Montanaro wrote:
> Python is *actually* easy to work with... most of the time. "If you
> want more things for you buck there's no luck..." =8^)
[And yes, I'm aware the line is "beats" not "thi
On Thu, Aug 06, 2020 at 07:19:01PM -0500, Skip Montanaro wrote:
> >
> > When Excel reads a file, it looks for stuff and decides to upgrade its
> > type. Eg dates etc (particularly pernicious with US-style dates versus
> > the rest of the planet). Mojibake for data ensues.
> >
> > As always, I am r
>
> When Excel reads a file, it looks for stuff and decides to upgrade its
> type. Eg dates etc (particularly pernicious with US-style dates versus
> the rest of the planet). Mojibake for data ensues.
>
> As always, I am reminded of Heuer's Razor:
>
> If it can't be turned off, it's not a feat
On 07Aug2020 09:40, DL Neil wrote:
>On 07/08/2020 05:33, Skip Montanaro wrote:
>>Hmmm... Rename genes, fix Excel, or dump Excel in favor of Python? I know
>>what my choice would have been. :-)
>>
>>https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates
>
>
>
On 07/08/2020 05:33, Skip Montanaro wrote:
Hmmm... Rename genes, fix Excel, or dump Excel in favor of Python? I know
what my choice would have been. :-)
https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates
At the risk of screaming off-topic...
The ar
Hmmm... Rename genes, fix Excel, or dump Excel in favor of Python? I know
what my choice would have been. :-)
https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates
Skip
--
https://mail.python.org/mailman/listinfo/python-list
On Friday, May 1, 2015 at 4:50:45 AM UTC+5:30, Ben Finney wrote:
> Chris Angelico writes:
>
> > Very easily and simply: Python 3 and Python 2 will always install
> > separately, and the only possible conflicts are over the "python"
> > command in PATH and which program is associated with ".py" fi
Chris Angelico writes:
> Very easily and simply: Python 3 and Python 2 will always install
> separately, and the only possible conflicts are over the "python"
> command in PATH and which program is associated with ".py" files.
Using the ‘python’ command is now ambiguous, and with Python 2 slippi
