Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

[Lennart Regebro]

On Tue, Feb 17, 2009 at 00:50, Guido van Rossum  wrote:
> Can you explain the difficulty with porting setuptools in more detail?

Oh, it just exposes a bug in distutils. It probably means I'll have to
make a test for python version, and if it is 3.0.1, monkey-patch
distutils. I haven't really looked into if there is any other
possibilities yet, I'm concentrating to make it run for 3.1 trunk
first.

-- 
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
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

Re: [Python-Dev] Issues to be closed: objections?

[Stephen J. Turnbull]

Daniel (ajax) Diniz writes:
 > M.-A. Lemburg wrote:
 > >> http://bugs.python.org/issue1231081 platform.processor() could be smarter
 > 
 > Thanks, Marc-Andre!
 > 
 > If anyone else feels like closing some of these issues, go ahead (no
 > need to report back, I'll find it out later). My rather bureaucratic
 > approach is just to avoid a possible trigger-happiness on my part
 > :)

What you are doing is "formal process."  It only becomes "bureaucracy"
when you try to make others do the same. ;-)

Thank you very much for the work and letting us know about the process
you follow!

___
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

[Python-Dev] Tracker cleanup roadmap

[Daniel (ajax) Diniz]

This is the janitorial plan I mentioned earlier...
It's so humongously huge by now that I'm not sure whether I should
submit it to e.g. the Python Papers or just print it and set it on
fire and run screaming. Fortunately, a tl;dl summary is provided :)

Daniel

Summary
Let's improve the tracker UI to better fit our needs. Then, classify
them bugs and separate garbage from real development. Lastly, bug
reporters should get a better UI. That's it,  any help is welcome.

The wall of text

Developer time constraints are arguably the main bottleneck in
handling tickets, which is only a subset of Python development.
Optimizing the application of main/core developers' time to Python
issues is a no-brainer. Being able to add volunteers to the productive
time pool is also very desirable. This document outlines a tentative
plan to move towards a better workflow in the Python Tracker.

Summary of tracker issues
The Python Tracker contains more than 17000 tickets, with
approximately 2350 still open. Of the open tickets, 500 were last
updated more than a year ago, while about 1150 were created before
that.

Current problems
Core developers, volunteers and newcomers are burdened with a lot of
inefficient and/or nonproductive chores when handling issues.
Requesting and waiting for feedback/confirmation/patch testing,
performing multiple searches, missing relevant discussion in
similar/duplicated issues and other low-level tasks and gotchas get in
the way of solving real problems.

The low signal/noise ratio of open issues is a major component of this
burden. At least 850 issues have outdated/missing version information,
while about 850 don't have a type (RFE, behavior, crash) set. About
800 issues have patches. Priorities carry little information, mostly
because they are left in the default setting: 1200 issues are set to
'normal' (a SF.net artifact) and 750 have no priority (a Roundup
artifact). Less than 200 tickets have 'low' priority. Most of these
issues boil down to tracker features being underused.

Another relevant time-sink consists of inadequacies of the current
interface. Many search features are hard to use or notice, among them
date spans and entering multiple inputs as lists. Other search
features are lacking, mostly simple boolean relations, e.g. those
including more than one keyword, full search terms, type, component,
etc. Besides searching, the lack of interfaces (and backend support)
for selecting and working with multiple issues tends to waste
considerable amounts of time.

Proposed plan
The suggested approach consists of a three parts effort focusing first
on developer-side tracker UI, then on massive issue categorization and
lastly on user-side UI. This optimizes the work of a single tracker
janitorveloper, but can be better partitioned if more janitorvelopers
are available.

The developer-side UI effort will focus, in this order, on making
available tracker features easier to use, adding new search features
and mass-handling of issues. This should improve both developers' and
tracker janitors' workflow.

Issue categorization will look like this last Bug Season (adding
details to tickets), but hopefully with a saner workflow. There are a
few clear sets of similar issues, e.g. about socket, handling of
characters on network protocol and format parsing modules, Tkinter +
IDLE, etc., that could use grouping and closing of duplicates. A
suggested form of grouping would be 'umbrella' or 'grab-bag' issues,
with existing issues of a topic as dependencies.

Finally, bug-reporter UI. The idea is to make it easier for users to
provide good bug reports, make the options clearer and minimize the
need for (preliminary) issue post-processing by developers. This might
include a template or wizard for reports, adding information about
which versions receive fixes or RFE, etc.

Deliverables (WIP)

Developer-side UI
  Patches for client-side Roundup:
- add missing fields/options to search (e.g. Stages, fix 'not closed')
- allow multiple choices for versions, components and keywords
- add checkboxes to multiselects
- avoid drop-downs above multiselects (janitors misclick a lot!)
- support for mass-selection/display (3rd party patch available)
- add a clutter-free 'search in all issues' button
  Patches for server-side Roundup:
- boolean searches
- support for mass-updates (3rd party patch available)
- maybe add regex support (3rd party patch available)

Issue categorization
- present better statistics about the open issues
- maybe add grab-bag issues (3rd party patch available)
- assorted closing, updating and poking old issues

User-side interface
  Patches for client-side Roundup:
- inline help for fields in issue creation
- adapt current docs (and Brett's guide) for easy access during reporting
  Patches for server-side Roundup:
- maybe add a wizard for filling bugs (3rd party patch available)

Timeline
TBD, first part should definitely be done before PyCo

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

[Calvin Spealman]

FWIW; I think a 3.0.2 would be useful socially (even volunteer projects have
marketting issues to consider). It says "we are committed to making 3.x
work", while the quick jump to 3.1 with only a limited minor fix release to
3.0 says "we stumbled into this and have to just brush this under the rug.
But we got it right this time! I hope.."

On Feb 16, 2009 2:08 PM, "Lennart Regebro"  wrote:

I discovered some remaining cmp() in 3.0.1, 38 minutes after Benjamin
fixed them. :) Unfortunately, that means porting setuptools to 3.0.1
will be a bit difficult. So my question is: Will there be a 3.0.2 with
those fixes, or should I add workaround code for 3.0.1?

--
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
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/ironfroggy%40gmail.com
___
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

[Python-Dev] Anyone want to lead the sprints at PyCon this year?

[Brett Cannon]

Or am I doing it again as usual because I was stupid enough to ask this
question?

-Brett
___
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

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

[Benjamin Peterson]

On Mon, Feb 16, 2009 at 5:50 PM, Guido van Rossum  wrote:
> Can you explain the difficulty with porting setuptools in more detail?

Basically setuptools invokes a functions in distutils that was still
using cmp(). (See the latest messages in issue #1717 for all the
details.)



-- 
Regards,
Benjamin
___
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

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

[Guido van Rossum]

[Resend, hopefully bag.python.org is fixed now.[

Can you explain the difficulty with porting setuptools in more detail?

On Mon, Feb 16, 2009 at 11:08 AM, Lennart Regebro  wrote:
> I discovered some remaining cmp() in 3.0.1, 38 minutes after Benjamin
> fixed them. :) Unfortunately, that means porting setuptools to 3.0.1
> will be a bit difficult. So my question is: Will there be a 3.0.2 with
> those fixes, or should I add workaround code for 3.0.1?

--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
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

Re: [Python-Dev] Wow!

[Greg Ewing]

Leif Walsh wrote:


If only we had a second Earth to mess with, we could just copy and swap.


Or we could use a generational approach, doing all our
messy stuff around the moon and copying to earth when
we've got our traffic control issues sorted out.

--
Greg
___
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

Re: [Python-Dev] Tracker cleanup report

[Jack Jansen]

On  16-Feb-2009, at 20:40 , Daniel (ajax) Diniz wrote:


There are about 20 Mac-related, 24 invalid/outdated and four IRIX
issues on the 'will be closed unless someone voices disagreement'
queue, so we have a good chance of totaling a hundred closed issues in
ten days.



I had a cursory look at these issues as they came by, and I didn't see  
any that struck me as still being relevant.

--
Jack Jansen, , http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma  
Goldman




___
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

Re: [Python-Dev] Adding T_SIZET to structmember.h

[Martin v. Löwis]

> Martin, I was not clear enough. Please, just tell me: Do you believe
> that this addition do make sense? Would you reject it for some reason
> (other than a bad patch) ?

I would be +0. All other integral types support both signed and signed
fields, why not size_t.

Regards,
Martin
___
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

Re: [Python-Dev] Tracker cleanup report

[Nick Coghlan]

Paul Moore wrote:
> 2009/2/16 Daniel (ajax) Diniz :
>> Hi,
>> Here's a summary of what's been accomplished and what's almost done.
>> This kinda marks the end of this Bug Season for me, but I'd like to do
>> at least one more installment before PyCon.
> 
> Can I, for one, offer a *huge* round of applause for what you've
> achieved. It's great to see the tracker getting some serious
> attention.

Hear, hear!

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
---
___
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

Re: [Python-Dev] Tracker cleanup report

[Brett Cannon]

On Mon, Feb 16, 2009 at 12:37, Paul Moore  wrote:

> 2009/2/16 Daniel (ajax) Diniz :
> > Hi,
> > Here's a summary of what's been accomplished and what's almost done.
> > This kinda marks the end of this Bug Season for me, but I'd like to do
> > at least one more installment before PyCon.
>
> Can I, for one, offer a *huge* round of applause for what you've
> achieved. It's great to see the tracker getting some serious
> attention.


Ditto from me! And I will eventually get to the bugs assigned to me
(hopefully starting some time this week).

-Brett
___
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

Re: [Python-Dev] Issues to be closed: objections?

[Benjamin Peterson]

On Mon, Feb 16, 2009 at 2:14 PM, Terry Reedy  wrote:
> Daniel (ajax) Diniz wrote:
>>
>> Hi,
>> I've marked some issues (25 now) to close, mostly because:
>> - there was no reply from OP, nor a clear justification for the issue;
>> - there are messages explaining why the issue is invalid;
>> - the OSes/versions of the report suggest the issue is currently invalid;
>>
>> However, I've been mistaken about the desirability of leaving an issue
>> open a couple of times in last days. So, I'd really appreciate if
>> someone could take a quick look at the issues below to avoid any
>> undesirable closing.
>>
>> I'll also mark them as pending later today, and plan to wait until the
>> weekend before closing. Any suggestion/criticism about this plan would
>> be welcome too.
>
> I believe items changed from open to pending get closed automatically after
> a couple of weeks (this should be documented, I hope), so that there is no
> need to revisit.

No, that feature hasn't yet been implemented.



-- 
Regards,
Benjamin
___
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

Re: [Python-Dev] Tracker cleanup report

[Paul Moore]

2009/2/16 Daniel (ajax) Diniz :
> Hi,
> Here's a summary of what's been accomplished and what's almost done.
> This kinda marks the end of this Bug Season for me, but I'd like to do
> at least one more installment before PyCon.

Can I, for one, offer a *huge* round of applause for what you've
achieved. It's great to see the tracker getting some serious
attention.

Paul.
___
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

Re: [Python-Dev] Issues to be closed: objections?

[Terry Reedy]

Daniel (ajax) Diniz wrote:

Hi,
I've marked some issues (25 now) to close, mostly because:
- there was no reply from OP, nor a clear justification for the issue;
- there are messages explaining why the issue is invalid;
- the OSes/versions of the report suggest the issue is currently invalid;

However, I've been mistaken about the desirability of leaving an issue
open a couple of times in last days. So, I'd really appreciate if
someone could take a quick look at the issues below to avoid any
undesirable closing.

I'll also mark them as pending later today, and plan to wait until the
weekend before closing. Any suggestion/criticism about this plan would
be welcome too.


I believe items changed from open to pending get closed automatically 
after a couple of weeks (this should be documented, I hope), so that 
there is no need to revisit.




Thanks everybody for all the support, helping, patience and enduring the spam!

Daniel

http://bugs.python.org/issue1231081 platform.processor() could be smarter

http://bugs.python.org/issue1251921 Fail codecs.lookup() on 'mbcs' and 'tactis'

http://bugs.python.org/issue1248119 pdb 'next' does not skip list comprehension

http://bugs.python.org/issue1169633 Install fail code 2932 after fail
to copy python_icon.exe

http://bugs.python.org/issue100 csv reader barfs encountering
quote when quote_none is set

http://bugs.python.org/issue1044299 compile error with stlport

http://bugs.python.org/issue1047540 Turtle.py hangs Idle

http://bugs.python.org/issue995956 TclError with intel's hypertheading

http://bugs.python.org/issue1001150 hotspot profiler does not work
correctly on P4 CPUs with HT

http://bugs.python.org/issue974635 Slice indexes passed to __getitem__
are wrapped

http://bugs.python.org/issue974159 Starting a script in OSX within a
specific folder

http://bugs.python.org/issue949667 file write() method and non-blocking mode.

http://bugs.python.org/issue815753 SCO_SV: many modules cannot be imported

http://bugs.python.org/issue727732 getpath.c-generated prefix wrong
for Tru64 scripts

http://bugs.python.org/issue875654 add support for installations
compiled for debugging

http://bugs.python.org/issue872815 How to pass the proxy server use socket

http://bugs.python.org/issue854918 Configurable SSL handshake

http://bugs.python.org/issue835176 [2.3.2] bz2 test failure on AIX
4.3.2, Tru64 UNIX

http://bugs.python.org/issue809887 Improve pdb breakpoint feedback

http://bugs.python.org/issue780354 socket.makefile() isn't compatible
with marshal/cPickle/etc

http://bugs.python.org/issue775340 OSX 'freeze' bug

http://bugs.python.org/issue4191 urlparse normalize URL path

http://bugs.python.org/issue1682241 Problems with urllib2 read()

http://bugs.python.org/issue1210326 comma separated cookie values

http://bugs.python.org/issue5072 urllib.open sends full URL after GET
command instead of local path
___
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/python-python-dev%40m.gmane.org



___
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

Re: [Python-Dev] Wow!

[Leif Walsh]

On Fri, Feb 13, 2009 at 9:14 PM, Greg Ewing  wrote:
> Also it sounds like they could do with a really good
> garbage collection algorithm just now.

If only we had a second Earth to mess with, we could just copy and swap.

-- 
Cheers,
Leif
___
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

[Python-Dev] Tracker cleanup report

[Daniel (ajax) Diniz]

Hi,
Here's a summary of what's been accomplished and what's almost done.
This kinda marks the end of this Bug Season for me, but I'd like to do
at least one more installment before PyCon.

We have closed 51 issues so far (sorry if I missed some):

*   Barry
**  Benjamin
**  Daniel
*   Georg
*   Guilherme
*   Hirokazu
*   Marc-Andre
*** Mark
**  Martin
*   Raymond
**  Terry
**  Victor

Thanks, guys!

There are about 20 Mac-related, 24 invalid/outdated and four IRIX
issues on the 'will be closed unless someone voices disagreement'
queue, so we have a good chance of totaling a hundred closed issues in
ten days.

I estimate to have updated about 400-500 issues in the last seven
days. I'm now nosy in 200 of these, that's karma for spamming
python-dev and python-bugs.

I'll pause the digging effort for the next days: besides having less
free time, I think it'll help us digest all those updates.

Obviously, the cleaning is far from complete: there are lots of issues
with 2.5 as version, lots of similar issues (e.g. for socket,
HTMLParser), etc. I'll soon post a tentative plan to attack these. The
goal would roughly be making it easier to pick good issues for PyCon
sprints and fixing in / adding to 2.7 and 3.1.

Cheers,
Daniel
___
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

[Python-Dev] To 3.0.2 or not to 3.0.2?

[Lennart Regebro]

I discovered some remaining cmp() in 3.0.1, 38 minutes after Benjamin
fixed them. :) Unfortunately, that means porting setuptools to 3.0.1
will be a bit difficult. So my question is: Will there be a 3.0.2 with
those fixes, or should I add workaround code for 3.0.1?

-- 
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
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

Re: [Python-Dev] Buildbots for 2.6 and 3.0

[Jim Kleckner]

Martin v. Löwis wrote:

Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots
for the release26-maint and release30-maint branches. Is someone working on 
that?


Yes. I won't enable 2.6 build slaves until 2.5.3 is released, but will
afterwards.


How does one actually download the resulting .msi for a build?
I poked a 2.6 build to try out the fix for issue4566:
 http://www.python.org/dev/buildbot/2.6/x86%20XP-4%202.6/builds/90

But searching around I don't see where the resulting files are stored.
Where are they located?

They used to go in here for 2.6 development:
 http://www.python.org/dev/daily-msi/

___
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

Re: [Python-Dev] Issues to be closed: objections?

[Daniel (ajax) Diniz]

M.-A. Lemburg wrote:
>> http://bugs.python.org/issue1231081 platform.processor() could be smarter

Thanks, Marc-Andre!

If anyone else feels like closing some of these issues, go ahead (no
need to report back, I'll find it out later). My rather bureaucratic
approach is just to avoid a possible trigger-happiness on my part :)

Daniel
___
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

Re: [Python-Dev] Issues to be closed: objections?

[M.-A. Lemburg]

On 2009-02-16 18:50, Daniel (ajax) Diniz wrote:
> Hi,
> I've marked some issues (25 now) to close, mostly because:
> - there was no reply from OP, nor a clear justification for the issue;
> - there are messages explaining why the issue is invalid;
> - the OSes/versions of the report suggest the issue is currently invalid;
> 
> However, I've been mistaken about the desirability of leaving an issue
> open a couple of times in last days. So, I'd really appreciate if
> someone could take a quick look at the issues below to avoid any
> undesirable closing.
> 
> I'll also mark them as pending later today, and plan to wait until the
> weekend before closing. Any suggestion/criticism about this plan would
> be welcome too.
> 
> Thanks everybody for all the support, helping, patience and enduring the spam!
> 
> Daniel
> 
> http://bugs.python.org/issue1231081 platform.processor() could be smarter

FYI: I've closed this one.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 16 2009)
>>> Python/Zope Consulting and Support ...http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/


::: Try our new mxODBC.Connect Python Database Interface for free ! 


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
___
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

Re: [Python-Dev] Mark old distutils as deprecated

[M.-A. Lemburg]

On 2009-02-16 17:54, Tarek Ziadé wrote:
> 2009/2/9 M.-A. Lemburg :
>> On 2009-02-08 11:15, Tarek Ziadé wrote:
>>> Hello
>>>
>>> To avoid confusion, as suggested by Akira who works on cleaning the
>>> Distutils pages on the python.org website,
>>> I would like to move http://svn.python.org/view/distutils/trunk into a
>>> branch and add a README.txt in an empty trunk
>>> to explain the current status of the package.
>>>
>>> Any objection ?
>> No.
>>
>> It be worthwhile keeping just the setup code and adjust that
>> to take the distutils package from the python/ dir in order to
>> build separate releases of the code for upload to PyPI (ones
>> that basically provide the code as released in Python 2.x as
>> separate download for 2.(x-1) and 2.(x-2)).
> 
> Indeed, and for any Python version in fact, to get early feedbacks
> between two Python releases.
> 
> I will make releases as you mentioned, and also a development release
> using the svn revision,
> so people can try out the current trunk.
> 
 '%sdev-r69676' % sys.version.split()[0]
> '2.7a0dev-r69676'

Great !

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 16 2009)
>>> Python/Zope Consulting and Support ...http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/


::: Try our new mxODBC.Connect Python Database Interface for free ! 


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
___
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

[Python-Dev] Issues to be closed: objections?

[Daniel (ajax) Diniz]

Hi,
I've marked some issues (25 now) to close, mostly because:
- there was no reply from OP, nor a clear justification for the issue;
- there are messages explaining why the issue is invalid;
- the OSes/versions of the report suggest the issue is currently invalid;

However, I've been mistaken about the desirability of leaving an issue
open a couple of times in last days. So, I'd really appreciate if
someone could take a quick look at the issues below to avoid any
undesirable closing.

I'll also mark them as pending later today, and plan to wait until the
weekend before closing. Any suggestion/criticism about this plan would
be welcome too.

Thanks everybody for all the support, helping, patience and enduring the spam!

Daniel

http://bugs.python.org/issue1231081 platform.processor() could be smarter

http://bugs.python.org/issue1251921 Fail codecs.lookup() on 'mbcs' and 'tactis'

http://bugs.python.org/issue1248119 pdb 'next' does not skip list comprehension

http://bugs.python.org/issue1169633 Install fail code 2932 after fail
to copy python_icon.exe

http://bugs.python.org/issue100 csv reader barfs encountering
quote when quote_none is set

http://bugs.python.org/issue1044299 compile error with stlport

http://bugs.python.org/issue1047540 Turtle.py hangs Idle

http://bugs.python.org/issue995956 TclError with intel's hypertheading

http://bugs.python.org/issue1001150 hotspot profiler does not work
correctly on P4 CPUs with HT

http://bugs.python.org/issue974635 Slice indexes passed to __getitem__
are wrapped

http://bugs.python.org/issue974159 Starting a script in OSX within a
specific folder

http://bugs.python.org/issue949667 file write() method and non-blocking mode.

http://bugs.python.org/issue815753 SCO_SV: many modules cannot be imported

http://bugs.python.org/issue727732 getpath.c-generated prefix wrong
for Tru64 scripts

http://bugs.python.org/issue875654 add support for installations
compiled for debugging

http://bugs.python.org/issue872815 How to pass the proxy server use socket

http://bugs.python.org/issue854918 Configurable SSL handshake

http://bugs.python.org/issue835176 [2.3.2] bz2 test failure on AIX
4.3.2, Tru64 UNIX

http://bugs.python.org/issue809887 Improve pdb breakpoint feedback

http://bugs.python.org/issue780354 socket.makefile() isn't compatible
with marshal/cPickle/etc

http://bugs.python.org/issue775340 OSX 'freeze' bug

http://bugs.python.org/issue4191 urlparse normalize URL path

http://bugs.python.org/issue1682241 Problems with urllib2 read()

http://bugs.python.org/issue1210326 comma separated cookie values

http://bugs.python.org/issue5072 urllib.open sends full URL after GET
command instead of local path
___
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

Re: [Python-Dev] Irix still supported? (was Re: Tracker archeology)

[Daniel (ajax) Diniz]

Daniel (ajax) Diniz wrote:
> Can I close these other IRIX issues?
>
> http://bugs.python.org/issue2048
> http://bugs.python.org/issue1086642
> http://bugs.python.org/issue1178510
> http://bugs.python.org/issue1070140

So, I'll close these later this week (citing that "Irix is long dead
and we don't support it in any form or version") unless opposition  is
voiced :)

Daniel
___
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

Re: [Python-Dev] Mark old distutils as deprecated

[Tarek Ziadé]

2009/2/9 M.-A. Lemburg :
> On 2009-02-08 11:15, Tarek Ziadé wrote:
>> Hello
>>
>> To avoid confusion, as suggested by Akira who works on cleaning the
>> Distutils pages on the python.org website,
>> I would like to move http://svn.python.org/view/distutils/trunk into a
>> branch and add a README.txt in an empty trunk
>> to explain the current status of the package.
>>
>> Any objection ?
>
> No.
>
> It be worthwhile keeping just the setup code and adjust that
> to take the distutils package from the python/ dir in order to
> build separate releases of the code for upload to PyPI (ones
> that basically provide the code as released in Python 2.x as
> separate download for 2.(x-1) and 2.(x-2)).

Indeed, and for any Python version in fact, to get early feedbacks
between two Python releases.

I will make releases as you mentioned, and also a development release
using the svn revision,
so people can try out the current trunk.

>>> '%sdev-r69676' % sys.version.split()[0]
'2.7a0dev-r69676'

Regards
Tarek

-- 
Tarek Ziadé | Association AfPy | www.afpy.org
Blog FR | http://programmation-python.org
Blog EN | http://tarekziade.wordpress.com/
___
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

Re: [Python-Dev] RELEASED Python 3.0.1

[Benjamin Peterson]

On Sun, Feb 15, 2009 at 9:15 PM, Ned Deily  wrote:
>
> It would be great if someone could add OS X links for the 3.0.1 and
> 2.6.1 to the main download page, too:
>   

I've now added them to the main download page.




-- 
Regards,
Benjamin
___
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

Re: [Python-Dev] Adding T_SIZET to structmember.h

[Lisandro Dalcin]

Martin, I was not clear enough. Please, just tell me: Do you believe
that this addition do make sense? Would you reject it for some reason
(other than a bad patch) ?

On Fri, Feb 13, 2009 at 10:35 PM, "Martin v. Löwis"  wrote:
>> Mark, the patch is not trivial, I cannot spend time on this until this
>> is accepted. Hope you understand.
>
> I certainly do understand. So it's likely not going to happen.
>
> Regards,
> Martin
>



-- 
Lisandro Dalcín
---
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594
___
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

Re: [Python-Dev] No 2.x->3.x porting documentation?

[Antoine Pitrou]

 pobox.com> writes:
> 
> I'm making a naive stab at converting nose to Python3 so I can hopefully run
> the lockfile test cases under Python 3.

Apparently, Jason Pellerin has started a py3k branch for the same purpose:
http://groups.google.com/group/nose-dev/browse_thread/thread/621c3767bbce3abc
https://python-nose.googlecode.com/svn/branches/py3k

Regards

Antoine.


___
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

Re: [Python-Dev] No 2.x->3.x porting documentation?

[Martin v. Löwis]

> I'm making a naive stab at converting nose to Python3 so I can hopefully run
> the lockfile test cases under Python 3.  (Again, I'm offline and have no
> idea at this point if it's been done already.)  I ran 2to3 then tried
> installing.  I got an immediate error about the compiler.consts module being
> missing.  (All nose does is import CO_GENERATOR from compiler.consts.)  I
> found that in the inspect module.  Then it complained about ClassType being
> missing from the types module.  I found no mention of changes to the types
> module in Misc/NEWS or Doc/whatsnew/3.0.rst.  I didn't find anything which
> looked like a "porting" document.
> 
> If neither of these changes could be handled by 2to3 I think it would have
> been useful to at least document the changes (in whatsnew/3.0.rst?) and
> maybe offer humans some workaround ideas.  If there is a wiki page
> collecting porting wisdom it should be referenced.  If I'm missing something
> fundamental about how people are expected to approach porting 2.x code to
> 3.x, please let me know.

I think you are missing the fact that it is nearly impossible to produce
a complete list of changes between 2.x and 3.x, or, if such a list would
be produced, it would have the size of the unified diff between the
source trees.

Instead, porters are expected to think a bit on what might have been the
most natural cause for a change (of course, some changes are arbitrary
and have no cause other than personal taste). For example, ClassType
used to be the type of old-style classes. Now that old-style classes are
gone, ClassType is gone as well (FWIW in 59217, and indeed without a
mentioning in NEWS, or even in the commit message). The removal of the
compiler package is mentioned in NEWS:

http://svn.python.org/view/python/branches/p3yk/Misc/NEWS?rev=55322&view=markup

Regards,
Martin
___
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