[issue2874] Remove use of the stat module in the stdlib

Brett Cannon added the comment: OK, this ain't ever going to happen, so I am just going to close this issue. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon added the comment: At this point it is a nice idea that no one wants to deal with to make happen. Dropping the priority but leaving open for now until I get around to making a final decision as to whether to just give up on this to finally allow closure on PEP 3108 once profile/c

[issue2874] Remove use of the stat module in the stdlib

Jack Diederich added the comment: The stat module wasn't deprecated in 3.1, so is this now a non-issue? If not, is it related to issue#1820? -- nosy: +jackdied ___ Python tracker __

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon added the comment: We never came to an agreement on how to handle this so it's just been sitting here. -- ___ Python tracker ___

[issue2874] Remove use of the stat module in the stdlib

Antoine Pitrou added the comment: What's the story on this? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue2874] Remove use of the stat module in the stdlib

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Deferring to 2.7/3.1 as discussed on the mailing list. -- priority: release blocker -> critical versions: +Python 2.7, Python 3.1 -Python 2.6 ___ Python tracker <[EMAIL PROTECTED]>

[issue2874] Remove use of the stat module in the stdlib

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: critical -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Wed, Jul 16, 2008 at 3:05 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > > Georg Brandl <[EMAIL PROTECTED]> added the comment: > > Why deprecate the functions then? > If they are made into methods on the object returned by os.stat(), what is

[issue2874] Remove use of the stat module in the stdlib

Georg Brandl <[EMAIL PROTECTED]> added the comment: Why deprecate the functions then? ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Wed, Jul 16, 2008 at 2:12 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > > Georg Brandl <[EMAIL PROTECTED]> added the comment: > > I don't like the name "os.stats". The os module is already so full of > constants and functions that one could a

[issue2874] Remove use of the stat module in the stdlib

Georg Brandl <[EMAIL PROTECTED]> added the comment: I don't like the name "os.stats". The os module is already so full of constants and functions that one could argue the few from stat won't hurt anymore :) ___ Python tracker <[EMAIL PROTECTED]>

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon <[EMAIL PROTECTED]> added the comment: I just finished taking Georg's idea and fleshing it out. Problem is that when I went to change the docs for 'stat', I noticed how many other function in the os module rely on the stat module for its constants. Should we move the constants over t

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Sun, Jul 13, 2008 at 4:04 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: > > Brett Cannon <[EMAIL PROTECTED]> added the comment: > > Another option is to eliminate the use of PyStructSequence and handle > the creation of a named tuple and a clas

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon <[EMAIL PROTECTED]> added the comment: Another option is to eliminate the use of PyStructSequence and handle the creation of a named tuple and a class with the methods in os.py. Then stat() can just return a tuple and the Python code can create the instances from that. _

[issue2874] Remove use of the stat module in the stdlib

Georg Brandl <[EMAIL PROTECTED]> added the comment: This is a proof of concept how to add methods to a structseq type. Of course PyStructSequence_InitType could also get a companion PyStructSequence_InitTypeEx that takes a PyMethodDef* array. -- keywords: +patch nosy: +georg.brandl Adde

[issue2874] Remove use of the stat module in the stdlib

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Perhaps collections.namedtuple() can be used with a custom subclass? In any case, it's not worth holding up the first beta for this. We can fix it after beta. Knocking this down to critical. -- nosy: +barry priority: release block

[issue2874] Remove use of the stat module in the stdlib

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Can't you just inherit PyStructSequence with tp_base? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> __

Re: [issue2874] Remove use of the stat module in the stdlib

On Fri, May 16, 2008 at 11:56 AM, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote: > > Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: > > Brett wrote: >> This will require moving over to using the named tuple features of >> os.stat() along with adding methods to the object that the stat

[issue2874] Remove use of the stat module in the stdlib

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: Brett wrote: > This will require moving over to using the named tuple features of > os.stat() along with adding methods to the object that the stat module > has as functions. How do you add new methods to a PyStructSequence? -

[issue2874] Remove use of the stat module in the stdlib

New submission from Brett Cannon <[EMAIL PROTECTED]>: The stat module is slated to go in Python 3.0, but that can't happen until all uses of the module are gone. This will require moving over to using the named tuple features of os.stat() along with adding methods to the object that the stat m