Am 06.12.2010 13:18, schrieb Ulrich Eckhardt:
> On Saturday 04 December 2010, Antoine Pitrou wrote:
>> Perhaps SVN doesn't get timestamps right.
>
> SVN doesn't touch timestamps explicitly, it just writes the files as they
> come
> and the system gives them the timestamps. This also makes sense,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2010 07:18 AM, Ulrich Eckhardt wrote:
> On Saturday 04 December 2010, Antoine Pitrou wrote:
>> Perhaps SVN doesn't get timestamps right.
>
> SVN doesn't touch timestamps explicitly, it just writes the files as they
> come
> and the system g
On Saturday 04 December 2010, Antoine Pitrou wrote:
> Perhaps SVN doesn't get timestamps right.
SVN doesn't touch timestamps explicitly, it just writes the files as they come
and the system gives them the timestamps. This also makes sense, because the
build system depends on them - you don't wan
> 1. Parts of the Makefile that use Python checked if Python is installed
> and generate a useful error if not.
> 2. All Python scripts that are part of the build should be 2-vs-3
> version agnostic for the time being (= until Python 2 is distant
> history, which won't happen soon)
I think this is
On Sat, Dec 4, 2010 at 15:41, Antoine Pitrou wrote:
> Le samedi 04 décembre 2010 à 13:39 +, Mark Dickinson a écrit :
> > On Sat, Dec 4, 2010 at 1:23 PM, Mark Dickinson
> wrote:
> > > On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou
> wrote:
> > >> Er, normally you don't need *any* Python ins
On Sat, Dec 4, 2010 at 1:40 PM, Benjamin Peterson wrote:
> You have to touch Include/Python-ast.h and Python/Python-ast.c. We do
> this for release tarballs.
Ah, that makes sense. Thanks.
Mark
___
Python-Dev mailing list
Python-Dev@python.org
http://m
Le samedi 04 décembre 2010 à 13:39 +, Mark Dickinson a écrit :
> On Sat, Dec 4, 2010 at 1:23 PM, Mark Dickinson wrote:
> > On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou wrote:
> >> Er, normally you don't need *any* Python installed to build Python (be
> >> it 3.x or 2.x).
> >
> > Are you su
2010/12/4 Mark Dickinson :
> On Sat, Dec 4, 2010 at 1:23 PM, Mark Dickinson wrote:
>> On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou wrote:
>>> Er, normally you don't need *any* Python installed to build Python (be
>>> it 3.x or 2.x).
>>
>> Are you sure about this? I remember needing an existin
On Sat, Dec 4, 2010 at 1:23 PM, Mark Dickinson wrote:
> On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou wrote:
>> Er, normally you don't need *any* Python installed to build Python (be
>> it 3.x or 2.x).
>
> Are you sure about this? I remember needing an existing Python to
> building Python 2.7
Le samedi 04 décembre 2010 à 13:23 +, Mark Dickinson a écrit :
> On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou wrote:
> > Er, normally you don't need *any* Python installed to build Python (be
> > it 3.x or 2.x).
>
> Are you sure about this? I remember needing an existing Python to
> build
On Sat, Dec 4, 2010 at 11:41 AM, Antoine Pitrou wrote:
> Er, normally you don't need *any* Python installed to build Python (be
> it 3.x or 2.x).
Are you sure about this? I remember needing an existing Python to
building Python 2.7 on a new python-less install of FreeBSD a couple
of months ago.
On Sat, 4 Dec 2010 11:20:57 +0200
Eli Bendersky wrote:
>
> I had the error pop out in a real build, so the time stamp is probably not a
> 100% guarantee. Therefore I think it's good that you made it version
> agnostic. This should be probably be a requirement for all scripts that are
> part of
On Dec 4, 2010, at 11:13, "Martin v. Löwis" wrote:
> Am 04.12.2010 09:48, schrieb Eli Bendersky:
>> To build the trunk Python 3k, it seems that Python 2 has to be installed.
>> This is because Objects/typeslots.py is called in the Makefile, and this
>> file uses Python 2 "print statement" syn
Am 04.12.2010 09:48, schrieb Eli Bendersky:
> To build the trunk Python 3k, it seems that Python 2 has to be installed.
> This is because Objects/typeslots.py is called in the Makefile, and this
> file uses Python 2 "print statement" syntax, which fails if $(PYTHON) is
> actually Python 3.
This sh
To build the trunk Python 3k, it seems that Python 2 has to be installed.
This is because Objects/typeslots.py is called in the Makefile, and this
file uses Python 2 "print statement" syntax, which fails if $(PYTHON) is
actually Python 3.
Can anyone reproduce this?
Eli
___
15 matches
Mail list logo
