Hi,
On 01/06/2011 13.28, victor.stinner wrote:
http://hg.python.org/cpython/rev/35212b113730
changeset: 70574:35212b113730
user:Victor Stinner
date:Wed Jun 01 12:28:04 2011 +0200
summary:
test.support: add requires_mac_ver() function
I would expect this to be a decorator,
On 31/05/2011 23:59, Sandro Tosi wrote:
Hi all,
following http://docs.python.org/devguide/coverage.html doc you'll end
up with several "new" files/dirs in your checkout:
- .coverage, used by coveragepy to save its info
- coverage/ , the symlink to coveragepy/coverage
- htmlcov/ , the dir where t
On Jun 01, 2011, at 02:33 AM, Terry Reedy wrote:
>On 6/1/2011 1:37 AM, "Martin v. Löwis" wrote:
>>> The requested one character change is
>>> -DEFAULT_REPOSITORY = 'http://pypi.python.org/pypi'
>>> +DEFAULT_REPOSITORY = 'https://pypi.python.org/pypi'
>>>
>>> If Tarek (or perhaps Eric) agre
Wiadomość napisana przez Martin v. Löwis w dniu 2011-06-01, o godz. 08:48:
>> Le mercredi 25 mai 2011 à 18:46 +0200, Charles-François Natali a écrit :
>>> While we're at it, adding a "recursive" argument to this shutil.chown
>>> could also be useful.
>>
>> I don't like the idea of a recursive fl
Hi,
Looks like nobody cares enough about the packaging docs :) If there is
no feedback, here’s what I propose to do:
- Add new Doc/library/packaging* files (library reference for developers
of packaging tools)
- Add new packaging-based “Installing Python Projects” to Doc/install,
replacing old
2011/6/1 Éric Araujo :
> Hi,
>
> Looks like nobody cares enough about the packaging docs :)
Perhaps your solutions are perfect already. :)
> If there is
> no feedback, here’s what I propose to do:
>
> - Add new Doc/library/packaging* files (library reference for developers
> of packaging tools)
>
Hi Benjamin,
>> For users needing the legacy distutils docs in 3.3, I would move the
>> older distutils Doc/install/index.rst to Doc/distutils/install.rst, and
>> add a link to Doc/distutils in Doc/library/distutils (because the main
>> page would no longer link to Doc/distutils).
>
> Or we could
I do care :)
Looks fine
Please push, as we can always change and fix things afterwards in the tip
before 3.3 is out.
Le 1 juin 2011 19:38, "Éric Araujo" a écrit :
> Hi,
>
> Looks like nobody cares enough about the packaging docs :) If there is
> no feedback, here’s what I propose to do:
>
> - Ad
On Wed, 01 Jun 2011 19:15:54 +0200, wrote:
> Looks like nobody cares enough about the packaging docs :) If there is
> no feedback, hereâs what I propose to do:
I think you should go ahead and make your changes, and then we'll
be able to see what it really looks like and decide if anything
ough
If a Python program imported a module, say numpy for example, where in the
source is this line interpreted and then handled by import.c ?
Thank you in advance!
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyth
On Wed, 01 Jun 2011 10:54:13 -0700, Timothy Kadich wrote:
> If a Python program imported a module, say numpy for example, where in the
> source is this line interpreted and then handled by import.c ?
Your question is not as simple as you think (I think), but I'm
guessing you will want to look at
2011/6/1 Timothy Kadich :
> If a Python program imported a module, say numpy for example, where in the
> source is this line interpreted and then handled by import.c ?
Many different files. Start from TARGET(IMPORT_NAME) in ceval.c.
--
Regards,
Benjamin
_
I don't understand what you mean by "TARGET(IMPORT_NAME)". I can't find that
string in ceval.c.
On 1 June 2011 12:04, Benjamin Peterson wrote:
> 2011/6/1 Timothy Kadich :
> > If a Python program imported a module, say numpy for example, where in
> the
> > source is this line interpreted and then
Nevermind. In 2.6 (what I'm working with) it's "case IMPORT_NAME:"
Thank you for letting me know where to start.
On 1 June 2011 15:43, Timothy Kadich wrote:
> I don't understand what you mean by "TARGET(IMPORT_NAME)". I can't find
> that string in ceval.c.
>
>
> On 1 June 2011 12:04, Benjamin Pe
On 6/1/2011 6:50 PM, raymond.hettinger wrote:
- with open("mydata.txt") as fp:
- for line in iter(fp.readline, "STOP"):
> process_line(line)
As noted on the tracker, this will always loop forever. Even if "STOP"
is corrected to "STOP\n", it will still loop forever
15 matches
Mail list logo