[Python-Dev] Summary of Python tracker Issues

2010-06-04 Thread Python tracker

ACTIVITY SUMMARY (2010-05-28 - 2010-06-04)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue 
number.  Do NOT respond to this message.


 2727 open (+38) / 17988 closed (+15) / 20715 total (+53)

Open issues with patches:  1103

Average duration of open issues: 719 days.
Median duration of open issues: 504 days.

Open Issues Breakdown
   open  2706 (+38)
languishing12 ( +0)
pending 8 ( +0)

Issues Created Or Reopened (58)
___

Seconds range in time unit 2010-06-03
   http://bugs.python.org/issue2568reopened belopolsky  
 
   patch, easy 

26.rc1: test_signal issue on FreeBSD 6.3   2010-06-03
CLOSED http://bugs.python.org/issue3864reopened skrah   
 
   patch, easy, buildbot   

urllib2 basicauth broken in 2.6.5: RuntimeError: maximum recur 2010-06-04
   http://bugs.python.org/issue8797reopened orsenthil   
 
   

TZ offset description is unclear in docs   2010-06-04
   http://bugs.python.org/issue8810reopened belopolsky  
 
   easy, needs review  

truncate() semantics changed in 3.1.2  2010-05-28
   http://bugs.python.org/issue8840reopened tjreedy 
 
   

Condition.wait() doesn't raise KeyboardInterrupt   2010-05-28
   http://bugs.python.org/issue8844created  hobb0001
 
   

Expose sqlite3 connection inTransaction as read-only in_transa 2010-05-28
CLOSED http://bugs.python.org/issue8845created  r.david.murray  
 
   patch, easy 

cgi.py bug report + fix: tailing carriage return and newline c 2010-05-28
   http://bugs.python.org/issue8846created  wobsta  
 
   patch   

crash appending list and namedtuple2010-05-28
   http://bugs.python.org/issue8847created  benrg   
 
   

Deprecate or remove U and U# formats of Py_BuildValue()2010-05-29
   http://bugs.python.org/issue8848created  haypo   
 
   patch   

python.exe problem with cvxopt 2010-05-29
   http://bugs.python.org/issue8849created  jroach  
 
   

Remove w format of PyParse_ParseTuple()  2010-05-29
   http://bugs.python.org/issue8850created  haypo   
 
   

pkgutil document needs more markups2010-05-29
   http://bugs.python.org/issue8851created  mft 
 
   patch   

_socket fails to build on OpenSolaris x64  2010-05-29
   http://bugs.python.org/issue8852created  drkirkby
 
   patch   

getaddrinfo should accept port of type long2010-05-29
   http://bugs.python.org/issue8853created  AndiDog 
 
   patch   

msvc9compiler.py: find_vcvarsall() doesn't work with VS2008 on 2010-05-29
   http://bugs.python.org/issue8854created  lemburg 
 
   64bit   

Shelve documentation lacks security warning2010-05-30
   http://bugs.python.org/issue8855created  Longpoke
 
   

Error in ceval.c when building --without-threads   2010-05-30
CLOSED http://bugs.python.org/issue8856created  merwok  
 
   

socket.getaddrinfo needs tests 

Re: [Python-Dev] Windows registry path not ignored with Py_IgnoreEnvironmentFlag set

2010-06-04 Thread Mark Hammond

On 2/06/2010 11:32 AM, Farshid Lashkari wrote:

Hello,

I noticed that if Py_IgnoreEnvironmentFlag is enabled, the Windows
registry is still used to initialize sys.path during startup. Is this an
oversight or intentional?


I guess it falls somewhere in the middle - the flag refers to the 
'environment' so I believe it hasn't really been considered as applying 
to the registry - IOW, the reference to 'environment' probably refers to 
the specific 'environment variables' rather than the more general 
'execution environment'.



I assumed one of the intentions of this flag is to prevent embedded
Python interpreters from being affected by other Python installations.
Ignoring the Window registry as well as environment variables seems to
make sense in this situation.


I agree.


If this is an oversight, would it be too late to have this fixed in
Python 2.7?


Others will have opinions which carry more weight than mine, but I see 
no reason it should not be fixed for *some* Python version.  Assuming no 
objections from anyone else, I suggest the best way to get this to 
happen in the short to medium term would be to open a bug with a patch. 
 A bug without a patch would also be worthwhile but would almost 
certainly cause it to be pushed back to a future 3.x version...


Cheers,

Mark
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com