Hi Nick, Holger,
this is a crazy fault of mine, see the end below.
I wrote:
I have a project that has its root somewhere on my machine.
This project has many folders and contains quite some modules.
There is a common root of the module tree, and I want to use
- either absolute imports
- relati
Dne 31.10.2012 23:15, Steven D'Aprano napsal(a):
I wonder if this message can be improved with a
pointer to the concept on when global variables become local?
If you have a suggestion for an improved message, please tell us. Or raise
an issue on the bug tracker.
I believe the "human problem"
On Mon, 12 Nov 2012 23:03:45 +0100 (CET)
victor.stinner wrote:
>
> +- Issue #16416: OS data are now always encoded/decoded to/from
> + UTF-8/surrogateescape, instead of the locale encoding (which may be ASCII
> if
> + no locale environment variable is set), to avoid inconsistencies with
> +
On Nov 5, 2012, at 4:51 PM, Greg Ewing wrote:
> Nick Coghlan wrote:
>> On Mon, Nov 5, 2012 at 10:08 PM, Mark Dickinson wrote:
>>> In Python 2, the 'exec' statement supports 'exec'-ing a (statement,
>>> globals, locals) tuple:
>
> If this is a deliberate feature, I'd guess it's because exec
> is
On 11/12/2012 7:30 AM, Jan Matějek wrote:
I believe the "human problem" here is that the one tends to gloss over
"local variable VARNAME", because it describes VARNAME and you already
think you know what that is, so you don't stop to think about it.
The following would be better in this rega
On Mon, Oct 29, 2012 at 4:47 AM, Daniel Holth wrote:
> I think Metadata 1.3 is done. Who would like to czar?
>
(Apologies for the belated reply, it's been a busy few weeks)
I'm happy to be BDFL delegate for these. I'd like to see PEP 425 updated
with some additional rationale based on Ronald's c
