On Tue, Jul 24, 2012 at 8:25 PM, Vincenzo Ampolo
wrote:
> On 07/24/2012 06:46 PM, Guido van Rossum wrote:
>>
>> You're welcome.
>
> Hi Guido,
>
> I'm glad you spent your time reading my mail. I would have never
> imagined that my mail could come to your attention.
Stop brownnosing already. :-) If
On 07/24/2012 06:46 PM, Guido van Rossum wrote:
>
> You're welcome.
Hi Guido,
I'm glad you spent your time reading my mail. I would have never
imagined that my mail could come to your attention.
> Have you read PEP 410 and my rejection of it
> (http://mail.python.org/pipermail/python-dev/2012-F
On Tue, Jul 24, 2012 at 9:46 PM, Guido van Rossum wrote:
> I didn't read the entire bug, but it mentioned something about storing
> datetimes in databases. Do databases support nanosecond precision?
>
MS SQL Server 2008 R2 has the datetime2 data type which supports 100
nanosecond (.1 microsecond
On Tue, Jul 24, 2012 at 5:58 PM, Vincenzo Ampolo
wrote:
> Hi all,
>
> This is the first time I write to this list so thank you for considering
> this message (if you will) :)
You're welcome.
> I know that this has been debated many times but until now there was no
> a real use case. If you look
Hi all,
This is the first time I write to this list so thank you for considering
this message (if you will) :)
I know that this has been debated many times but until now there was no
a real use case. If you look on google about "python datetime
nanosecond" you can find more than 141k answer about
> If building with VS11.0, is there more than just applying the
> equivalent VS10.0 patch to also include VS11?
I think nobody *really* knows at this point. Microsoft has a tradition
of breaking Python with every VS release, by making slight incompatible
changes in the C library. With VS 2012, on
On Tue, Jul 24, 2012 at 1:02 PM, Wim Colgate wrote:
> Please forgive me if this is not the prescribed method for asking this
> question.
>
> For various reasons, I would like to build python 2.7.3 from source
> using the latest VS tools (VS11.0 is in RC -- which is close enough
> for my purposes).
Please forgive me if this is not the prescribed method for asking this
question.
For various reasons, I would like to build python 2.7.3 from source
using the latest VS tools (VS11.0 is in RC -- which is close enough
for my purposes). I have seen the various sub-directories (VC6, VS7.1
and VS8.0)
On 24 Jul 2012, at 11:52, Devin Jeanpierre wrote:
> On Tue, Jul 24, 2012 at 6:07 AM, Michael Foord
> wrote:
>>> This is not an ideal world and 2to3 is not good enough to convert files
>>> without further intervention and testing.
>>
>> It is if you design your code *to be converted* by 2to3 an
On Tue, Jul 24, 2012 at 6:07 AM, Michael Foord
wrote:
>> This is not an ideal world and 2to3 is not good enough to convert files
>> without further intervention and testing.
>
> It is if you design your code *to be converted* by 2to3 and do regular
> testing of the result.
That's hardly without
On Jul 24, 2012 10:32 AM, "Terry Reedy" wrote:
>
> On 7/24/2012 12:44 AM, anatoly techtonik wrote:
>
>> Python 3 check explicitly tells the reader that 2to3 should only be
>> used in Python 3. Otherwise everybody need to guess when this *_2to3
>> tools are triggered. As for me, I see no technical
On 24 Jul 2012, at 10:30, Terry Reedy wrote:
> On 7/24/2012 12:44 AM, anatoly techtonik wrote:
>
>> Python 3 check explicitly tells the reader that 2to3 should only be
>> used in Python 3. Otherwise everybody need to guess when this *_2to3
>> tools are triggered. As for me, I see no technical li
On 7/24/2012 12:44 AM, anatoly techtonik wrote:
Python 3 check explicitly tells the reader that 2to3 should only be
used in Python 3. Otherwise everybody need to guess when this *_2to3
tools are triggered. As for me, I see no technical limitations why
*_2to3 can not be run by Python 2 (PyPy, RPy
On 24.07.12 00:44, mar...@v.loewis.de wrote:
42 is most likely not the right answer, as the size should be a
multiple of four.
>>> ''.__sizeof__()
25
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
14 matches
Mail list logo
