[issue13674] crash in datetime.strftime

2011-12-29 Thread patrick vrijlandt

New submission from patrick vrijlandt patrick.vrijla...@gmail.com:

This causes a crash in python 3.2.2 and 3.2, but not in 2.7.2

C:\Python32python
Python 3.2 (r32:88445, Feb 20 2011, 21:29:02) [MSC v.1500 32 bit (Intel)] on 
win32
Type help, copyright, credits or license for more information.
 import datetime
 datetime.datetime(1899,12,31).strftime(%y)

The crash happens with %y but not with %Y.
The crash happens with any year  1900.
On 2.7.2 a ValueError is raised because strftime requires year = 1900. This is 
what IMHO should happen (and would have saved me a lot of time)

--
components: Library (Lib)
messages: 150323
nosy: patrick.vrijlandt
priority: normal
severity: normal
status: open
title: crash in datetime.strftime
type: crash
versions: Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13671] double comma cant be parsed in config module

2011-12-29 Thread Łukasz Langa

Łukasz Langa luk...@langa.pl added the comment:

Hello, Alexander. ConfigObj is an external library. It is not maintained by the 
core team. You can report your issue to the ConfigObj issue tracker here:

http://code.google.com/p/configobj/issues/list

--
components: +None -Regular Expressions
resolution:  - invalid
stage:  - committed/rejected
status: open - closed
versions:  -Python 2.7, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13671
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread maniram maniram

maniram maniram maniandra...@gmail.com added the comment:

This bug can not be reproduced in Python 3.2.2 on Ubuntu.
Since Python 2.7.2 on your system raises a ValueError for dates below 1900 
,your system's strftime probably does not allow dates below 1900 (unlike 
Ubuntu).
Python 3.2.2's datetime.strftime should handle this error from strftime().

--
nosy: +maniram.maniram

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue9260] A finer grained import lock

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

 It owns the lock, but hasn't yet updated the lock's owner
 (lock-tstate), so another thread calling detect_circularity() will
 think that this lock is available, and will proceed, which can
 eventually lead to a deadlock.

That's true. Do you think temptatively acquiring the lock (without
blocking) would solve the issue?

 Also, I think that locks will use POSIX semaphores on systems that
 support only a limited number of them (such as FreeBSD 7), and this
 might fail in case of nested imports (the infamous ENFILE). I'd have
 to double check this, though.

Isn't this limit only about named semaphores? Or does it apply to
anonymous semaphores as well?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9260
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12715] Add symlink support to shutil functions

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

Patch is now applied to 3.3, thank you for your patience :)

--
resolution:  - fixed
stage: commit review - committed/rejected
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12715
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13678] way to prevent accidental variable overriding

2011-12-29 Thread James Hutchison

New submission from James Hutchison jamesghutchi...@gmail.com:

In python is currently there a way to elegantly throw an error if a variable is 
already in the current scope?

For example:

def longfunc(self, filename):
FILE = open(filename);
header = FILE.readline();
... bunch of code ...
childfiles = self.children;
for child in childfiles:
 FILE = open(child);
 header = FILE.readline();
 ... do something with header ...
for line in FILE:
   ... etc ...

In this case, I'm accidentally overriding the old values of FILE and header, 
resulting in a bug. But I'm not going to catch this. I've had a couple of real 
life bugs due to this that were a lot more subtle and lived for months without 
anyone noticing the output data was slightly wrong.

This situation could be prevented if there was a way to say something along the 
lines of new FILE = open(child) or new header = FILE.readline() and have 
python throw an error to let me know that it already exists. This would also 
make code clearer because it allows the intended scope of a variable to become 
more apparent. Since new var = something is a syntax error, adding this 
functionality wouldn't break old code, as long as python would allow for 'new' 
(or whatever the keyword would end up being) to also be a variable name (like 
new new = 1 or new = 1)

--
components: Interpreter Core
messages: 150344
nosy: Jimbofbx
priority: normal
severity: normal
status: open
title: way to prevent accidental variable overriding
type: enhancement
versions: Python 3.2, Python 3.3, Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13678
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread Tim Golden

Tim Golden m...@timgolden.me.uk added the comment:

Yes, but the MS crt strftime *for %y* requires a year = 1900 (ie 
tm_year = 0). Looks like we need a special check.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12715] Add symlink support to shutil functions

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

I've checked the latest patch to work fine under Windows 7 (and Linux, of 
course).

--
stage:  - commit review

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12715
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12715] Add symlink support to shutil functions

2011-12-29 Thread Hynek Schlawack

Changes by Hynek Schlawack h...@ox.cx:


Added file: http://bugs.python.org/file24102/8330f2045f4d.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12715
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13675] IDLE won't open if it can't read recent-files.lst

2011-12-29 Thread Michael Foord

Michael Foord mich...@voidspace.org.uk added the comment:

Thanks

--
resolution:  - duplicate
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13675
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13673] SIGINT prevents raising of exceptions unless PyErr_CheckSignals() called

2011-12-29 Thread sbt

sbt shibt...@gmail.com added the comment:

I have tried the same with Python 2.7.1 on Linux.  The problem is the same, but 
one gets a partial traceback with no exception:

   import sys, testsigint
   testsigint.wait()
  ^CTraceback (most recent call last):
File stdin, line 1, in module

   sys.last_value
  RuntimeError()

Both on 2.7 and 3.3 sys.last_value gives RuntimeError().

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13673
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12715] Add symlink support to shutil functions

2011-12-29 Thread Hynek Schlawack

Hynek Schlawack h...@ox.cx added the comment:

Added new patch with protection for the remaining UF_NODUMPs in the test case. 
All raised issues should be fixed now. :)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12715
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread Florent Xicluna

Changes by Florent Xicluna florent.xicl...@gmail.com:


--
nosy: +belopolsky, flox, haypo
versions: +Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

I think calling PyErr_WriteUnraisable would be more appropriate than 
PyErr_Clear.
I also wonder whether it's ok to ignore the exception. Pressing e.g. Ctrl-C 
generally shouldn't fail to stop the program, even if another exception is 
being processed at that moment.
(of course, you could argue this is already the case when e.g. the signal is 
received while in a __del__)

--
nosy: +amaury.forgeotdarc, pitrou
stage:  - patch review

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13673
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12715] Add symlink support to shutil functions

2011-12-29 Thread Roundup Robot

Roundup Robot devn...@psf.upfronthosting.co.za added the comment:

New changeset cf57ef65bcd0 by Antoine Pitrou in branch 'default':
Issue #12715: Add an optional symlinks argument to shutil functions (copyfile, 
copymode, copystat, copy, copy2).
http://hg.python.org/cpython/rev/cf57ef65bcd0

--
nosy: +python-dev

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12715
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread STINNER Victor

STINNER Victor victor.stin...@haypocalc.com added the comment:

timemodule.c has the following check:

#if defined(_MSC_VER) || defined(sun)
if (buf.tm_year + 1900  1 ||   buf.tm_year + 1900) {
PyErr_SetString(PyExc_ValueError,
strftime() requires year in [1; ]);
return NULL;
}
#endif

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13677] correct docstring for builtin compile

2011-12-29 Thread Jim Jewett

New submission from Jim Jewett jimjjew...@gmail.com:

The current docstring for compile suggests that the flags are strictly for 
selecting future statements.  These are not the only flags.

It also suggests that the source must be source code and the result will be 
bytecode, which isn't quite true.

I suggest changing:

The flags argument, if present, controls which future statements influence the 
compilation of the code.

to:

The flags argument, if present, largely controls which future 
statements influence the compilation of the code.  (Additional 
flags are documented in the AST module.)

--
assignee: docs@python
components: Documentation
files: bltinmodule.c.patch
keywords: patch
messages: 150337
nosy: Jim.Jewett, docs@python
priority: normal
severity: normal
status: open
title: correct docstring for builtin compile
type: behavior
Added file: http://bugs.python.org/file24105/bltinmodule.c.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13677
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13675] IDLE won't open if it can't read recent-files.lst

2011-12-29 Thread Roger Serwy

Roger Serwy roger.se...@gmail.com added the comment:

This is a duplicate of issue4625 and was fixed.

The silently failing is part of issue13582.

--
nosy: +serwy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13675
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread Tim Golden

Tim Golden m...@timgolden.me.uk added the comment:

This is happening on Windows x86 against the current tip. The MS C runtime can 
handle older dates; it's just that we're taking 1900 off the year at some 
point. (At least, I think that's what's happening). FWIW you only need 
time.strftime to reproduce the error:

  import time
  time.strftime(%y, (1899, 1, 1, 0, 0, 0, 0, 0, 0))

If no-one gets there first I'll dig into the timemodule strftime wrapper.

--
nosy: +tim.golden

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt

sbt shibt...@gmail.com added the comment:

Attached is a patch for the default branch.

Before calling PyFile_WriteString() the patch saves the current exception.  
Then it calls PyErr_CheckSignals() and clears the current exception if any.  
After calling PyFile_WriteString() the exception is restored.

I am not sure this is an appropriate fix.

--
components: +Interpreter Core
keywords: +patch
Added file: http://bugs.python.org/file24106/traceback_checksignals.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13673
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread Tim Golden

Tim Golden m...@timgolden.me.uk added the comment:

... and that's because the tm struct defines the tm_year field as an offset 
from 1900. Sorry for the false start. I'll look at the MS runtime stuff instead

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13676] sqlite3: Zero byte truncates string contents

2011-12-29 Thread Petri Lehtinen

New submission from Petri Lehtinen pe...@digip.org:

Inserting a string with embedded zero byte only inserts the string up to the 
first zero byte:

import sqlite3

connection = sqlite3.connect(':memory:')
cursor = connection.cursor()

cursor.execute('CREATE TABLE test (value TEXT)')
cursor.execute('INSERT INTO test (value) VALUES (?)', ('foo\x00bar',))

cursor.execute('SELECT value FROM test')
print(cursor.fetchone())
# expected output: (u'foo\x00bar',)
# actual output: (u'foo',)

Also, if there's already data inserted to a table like above with embedded zero 
bytes, the sqlite-API-to-Python-string conversion truncates the strings to just 
before the first zero byte.

Attaching a patch against 3.3 that fixes the problem. Basically, it uses 
PyUnicode_AsStringAndSize and PyUnicode_FromStringAndSize instead of the 
non-size variants.

Please review, as I'm not sure it covers each possible case.

--
components: Library (Lib)
files: sqlite3_zero_byte.patch
keywords: needs review, patch
messages: 150329
nosy: ghaering, petri.lehtinen
priority: normal
severity: normal
status: open
title: sqlite3: Zero byte truncates string contents
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file24104/sqlite3_zero_byte.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13676
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13675] IDLE won't open if it can't read recent-files.lst

2011-12-29 Thread Michael Foord

New submission from Michael Foord mich...@voidspace.org.uk:

Reported by a user. Reported on Windows but probably not Windows specific.

If IDLE doesn't have permission to read the recent-files.lst file then it 
crashes. (When launched with pythonw.exe on Windows it silently fails to open 
with no error message to the user.)

As the recent file list isn't core functionality, IDLE should be able to run 
without access to this file. 

Attached is a screenshot of the traceback when IDLE is launched from the 
console.

--
components: IDLE
files: Python problem.JPG
messages: 150327
nosy: michael.foord
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE won't open if it can't read recent-files.lst
versions: Python 2.7, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file24103/Python problem.JPG

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13675
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue9260] A finer grained import lock

2011-12-29 Thread Charles-François Natali

Charles-François Natali neolo...@free.fr added the comment:

IIUC, the deadlock avoidance code just checks that acquiring a
per-module lock won't create a cycle.
However, I think there's a race, because the cycle detection and the
lock acquisition is not atomic.

For example, let's say we have a thread exactly here in in
acquire_import_lock():
PyThread_acquire_lock(lock-lock, 1);
/* thread inside PyEval_RestoreThread(), waiting for the GIL */
PyEval_RestoreThread(saved);
lock-waiters--;
}
assert(lock-level == 0);
lock-tstate = tstate;

It owns the lock, but hasn't yet updated the lock's owner
(lock-tstate), so another thread calling detect_circularity() will
think that this lock is available, and will proceed, which can
eventually lead to a deadlock.

Also, I think that locks will use POSIX semaphores on systems that
support only a limited number of them (such as FreeBSD 7), and this
might fail in case of nested imports (the infamous ENFILE). I'd have
to double check this, though.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9260
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt

sbt shibt...@gmail.com added the comment:

I think I have found the problem.  PyTraceBack_Print() calls 
PyFile_WriteString(), which calls PyFile_WriteObject(), which calls 
PyObject_Str() which begins with 

  PyObject_Str(PyObject *v)
  {
  PyObject *res;
  if (PyErr_CheckSignals())
  return NULL;
  ...

Since PyErr_CheckSignals() returns -1, PyTraceBack_Print() fails.

(Changed title.)

--
title: SIGINT prevents raising of exceptions unless PyErr_CheckSignals() called 
- PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not 
called
type:  - behavior
versions: +Python 2.7, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13673
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13678] way to prevent accidental variable overriding

2011-12-29 Thread Eric Snow

Eric Snow ericsnowcurren...@gmail.com added the comment:

Interesting thought, the syntax seems unnecessary. Adding new syntax to the 
language is something that happens rarely and only with a _lot_ of 
consideration.

As a slightly more verbose alternative, currently you can do this:

def fail_if_defined(*args, namespace):
for name in args:
if name in namespace:
raise AlreadyBoundError(name)

And in your code you would put the following where you cared about it:

fail_if_defined(FILE, header, namespace=locals())

You could even drop the namespace parameter (since it's sort of boilerplate):

def fail_if_defined(*args):
namespace = inspect.currentframe().f_back.f_locals
for name in args:
if name in namespace:
raise AlreadyBoundError(name)

However, if you are going to the trouble of sticking those in place (or of 
selectively using a new syntax), you are likely paying attention to the the 
situation already, rendering either solution unnecessary.

Ultimately, this is something better addressed instead by keeping your 
functions small, by being a little more cautious in naming, and particularly by 
careful unit testing.

--
nosy: +eric.snow

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13678
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13678] way to prevent accidental variable overriding

2011-12-29 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

I think this more the domain of pylint/pyflakes.

--
nosy: +benjamin.peterson
resolution:  - rejected
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13678
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7719] distutils: ignore .nfsXXXX files

2011-12-29 Thread Zbyszek Szmek

Zbyszek Szmek zbys...@in.waw.pl added the comment:

Review of both patches (python-2.5.1-distutils-aixnfs.patch and 
dir_util.py.diff) as they are essentially the same:

I think that the test is in wrong place: we would want to ignore those .nfs* 
files always, not just when checking for symlinks. A separate test
at the top of the loop would be better:
for n in names:
+   if n.startswith('.nfs'):
+   continue
src_name = os.path.join(src, n)
dst_name = os.path.join(dst, n)
if preserve_symlinks and os.path.islink(src_name):


BTW: under linux 2.6.20 I see files like: .nfs059241390036, always 
of this length, with hexadecimal digits after .nfs).

--
nosy: +zbysz
versions: +Python 3.3 -3rd party, Python 3.1

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7719
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13678] way to prevent accidental variable overriding

2011-12-29 Thread James Hutchison

James Hutchison jamesghutchi...@gmail.com added the comment:

For starters, this would be most efficient implementation:

def unique(varname, value, scope):
assert(not varname in scope);
scope[varname] = value;

Usage:
unique('b', 1, locals());
print(b);

But you can't put that in a loop else it will false trigger. Ideally this 
wouldn't false trigger. This could be done by having python internally 
associate a line number with each explicit variable declaration.

Anyways, an external python function would be too slow for my use case. 
Likewise, since it would be something you could use a lot, it should be 
implemented in the underlying C code to give it minimal overhead.

Keeping functions small is very impractical at times. I shouldn't create 50 
randomly named one use functions in my class as a safeguard against accidental 
overwriting when I have a legitimately complicated piece of code that can't be 
dissected without becoming unreadable. In many cases I might need 8 or 9 locals 
at a time in a single line in each loop section.

I don't see how this is the area of pylint/pyflakes at all. The idea is to make 
it so the human doesn't have to carefully inspect their code in order to decide 
if they made a mistake or not. Inspecting a long list of warnings is no better, 
and arguably I could pull up a bunch of python language design decisions and 
ask why they were made if pylint/pyflakes exists.

If such a change would have be implemented after much consideration and 
discussion, I don't see how closing my post helps accomplish that.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13678
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13645] import machinery vulnerable to timestamp collisions

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

Here is a patch adding the source code size to the pyc header.
The number of places where details of the pyc file format are hard coded is 
surprisingly high...
Unfortunately, I had to modify importlib's public API (path_mtime - 
path_stats). I find it unfortunate that importlib's API is vulnerable to pyc 
format changes.

--
keywords: +patch
title: test_import fails after test_coding - import machinery vulnerable to 
timestamp collisions
versions:  -Python 3.2
Added file: http://bugs.python.org/file24107/impsize.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13645
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13678] way to prevent accidental variable overriding

2011-12-29 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

I suggest you mail python-ideas.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13678
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt

sbt shibt...@gmail.com added the comment:

 I think calling PyErr_WriteUnraisable would be more appropriate than 
 PyErr_Clear.

You mean just adding

PyErr_CheckSignals();
if (PyErr_Occurred())
PyErr_WriteUnraisable(NULL);

before the call to PyFile_WriteString()?  That seems to work:

   from testsigint import *; wait()
  ^CException KeyboardInterrupt ignored
  Traceback (most recent call last):
File stdin, line 1, in module
  RuntimeError

 I also wonder whether it's ok to ignore the exception. Pressing e.g. 
 Ctrl-C generally shouldn't fail to stop the program, even if another 
 exception is being processed at that moment.

The ignoring and clearing of exceptions also happens higher (lower?) in the 
call stack in print_exception() and print_exception_recursive().  For example, 
print_exception() ends with

  /* If an error happened here, don't show it.
 XXX This is wrong, but too many callers rely on this behavior. */
  if (err != 0)
  PyErr_Clear();
  }

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13673
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13674] crash in datetime.strftime

2011-12-29 Thread patrick vrijlandt

patrick vrijlandt patrick.vrijla...@gmail.com added the comment:

Is it relevant that 2.7.2 _does_ throw a correct exception?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13674
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13676] sqlite3: Zero byte truncates string contents

2011-12-29 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

Where are the tests? :)

--
nosy: +pitrou

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13676
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13645] import machinery vulnerable to timestamp collisions

2011-12-29 Thread Arfrever Frehtes Taifersar Arahesis

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:


--
nosy: +Arfrever

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13645
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

New submission from Rock Achu rockac...@gmail.com:

running this script repeatedly causes corruption in the console window. 

Just before posting this report, it led to a complete windows system freeze.

running python 2.7 x86 on windows x64.

The programs seems to run a couple times (when it is supposed to run once), 
with the output becoming more and more corrupted. 
One time it printed lots of triple quotes () and import os messages, even 
though none of those are in the script.

To reproduce run the spawner.test.bat file inside the zip.

Remember not to run with stuff you wont want to lose open.

--
components: Windows
files: issue.zip
messages: 150355
nosy: Rock.Achu
priority: normal
severity: normal
status: open
title: Multiprocessing system crash
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file24108/issue.zip

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

I hit Ctrl-C right after opening the bat file and got this mess:

--
Added file: http://bugs.python.org/file24109/error.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

On a hunch opened task manager. There were over 9000 python processes open. 
Shocking. 

That was probably the cause of the system freeze.

However I only had 20 threads open. Why so many processes?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

Or did I only have 20 threads?
if the program was running in a loop, then it would have spawned 20 threads 
each, leading to the huge amount of processes, and probably the other issues.


So why does it run so many times?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

Ok, using other code, I narrowed it down to this code and before:
for i in xrange(10):
spawner.newproc(run=True)

repeating infinitely


which only should set a variable (self.busy) to false

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

By inserting print statements and feverishly killing the process, I narrowed it 
down to the statement:
self.thread.start()
that causes the issue.
which runs _M_Process.func() in a multiprocessing.Process

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

More clues:

the function _M_Process.func isn't being called.




--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

Changing the function name and removing the argument (self) passed to func 
doesn't change  a thing.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

Alright. The issue stays here. Passing nothing to multiprocessing.Process still 
reproduces the issue.


someone else know how to deal with this?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13679] Multiprocessing system crash

2011-12-29 Thread Rock Achu

Rock Achu rockac...@gmail.com added the comment:

Alright. Just running:

import multiprocessing
thread = multiprocessing.Process()
thread.start()

raw_input()


-
Causes the crash. This time there is no output, so it is essentailly invisible. 
Caught me by surprise.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13679
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com