On 20/04/2010 4:51 AM, Michael Foord wrote:
Hello all,
I would like to propose Tim Golden as a Python committer. He has been
involved in Python for many years, is a capable Windows guy, and has
submitted many patches / documentation fixes - particularly for Windows
issues.
+1 - he has been an
On 3/03/2010 2:11 PM, Antoine Pitrou wrote:
That was also my sentiment. These issues seem to be overestimated, or
perceived as a lack of care for the Windows platform.
This perception is wrong, I do care as much as others about the Windows
platform.
That is not my perception. My perception is
On 3/03/2010 2:29 AM, Steve Holden wrote:
Antoine Pitrou wrote:
Le Tue, 2 Mar 2010 15:41:45 +0100,
Dirkjan Ochtman a écrit :
For the EOL issue, there is code, it needs testing. Martin Geisler
(the primary author so far) and I issued a call for testing on
python-dev last week, but without any r
Brett,
We really appreciate your work on this PEP, but I wonder if the process
itself isn't causing some of this friction:
> Can you guys please let me finish the PEP before you start worrying about
> whether we are going to switch? At least give me the chance to make a
> decision on whether
> And it is even covered in the "minimal setup" section:
> http://www.python.org/dev/peps/pep-0374/#hg
I can't make the mercurial instructions work; I'm yet to investigate why though.
But my wider point was that there doesn't seem to be a required level of
functionality, or even a blanket statem
[Brett writes]
> I guess I didn't make it clear enough in the survey. This is meant to gauge
> whether you think the DVCSs would be improvement over the status quo for us,
> which happens to be svn. I have changed the options to make it a comparison
> against the status quo and not svn specific
I'm not sure if this list or python-dev is appropriate for the more general
dvcs discussions - apologies if I got it wrong. There is one issue I'm yet
to see addressed - Windows line endings.
When the svn tree is checked out on windows, all text files have \r\n line
endings. While many dev tools
> There's an option missing in that survey:
>
> [ ] I see a need to switch to a DVCS at all.
To be fair, the survey isn't asking about a switch, just how they compare
against svn.
But I must admin that seems a little strange; while I just answered that I
believe hg and bzr are better than svn (I
> at such a script, which I promptly stopped looking at as soon as it
> worked
Which is quite obvious really given that:
> # nuke ourselves from argv
> del sys.argv[1]
is removing the wrong value!
Mark
___
python-committers mailing list
python-commit
> > * Better support for 2to3 in distutils (specifically, the support in
> > build_py is stale, plus 'build_scripts' and 'install_data' should
> > convert
> > .py files to py3k syntax.)
>
> Please do create a bug report for that. It sounds like it's easy to
> fix.
Yeah, build_py is fairly easy to
[when 2 mailing lists are not enough... :-]
> I'm seeing that people are just starting to download and play with 3.0.
> I expect that we'll start getting more feedback on conversion issues
+1 from this direction too. pywin32 has recently started looking seriously
at py3k, and while things are in
> sorry if you were aware of that already, but VC6 isn't the compiler for
> the official builds. The VC6 files are "only" alternative "Makefiles".
As far as I'm concerned, +1 for Gerhard being able to checkin vc6 related
makefiles to the trunk without review (notwithstanding any other
restrictions
12 matches
Mail list logo
