Mailing List Archive: Zope: Coders

Issue 1891

Index | Next | Previous | View Threaded

sidnei at enfoldsystems

Sep 16, 2005, 5:32 PM

Post #1 of 3 (4864 views)
Permalink

Issue 1891

Issue 1891 has a patch to remove some references to the 'whrandom'
module, that has been deprecated since python2.1.

I've cleaned up that patch and expanded it to remove *all* references
to whrandom, including code that enabled it for use by 'Script (Python)'
and DTML.

It's my opinion that people using 'whrandom' explicitly should know
what they are doing and won't be harmed too much by the removal of
this.

Any thoughts?

--
Sidnei da Silva
Enfold Systems, LLC.
http://enfoldsystems.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders

jens at dataflake

Sep 17, 2005, 2:02 AM

Post #2 of 3 (4564 views)
Permalink

Re: Issue 1891 [In reply to]

On 17 Sep 2005, at 02:32, Sidnei da Silva wrote:

> Issue 1891 has a patch to remove some references to the 'whrandom'
> module, that has been deprecated since python2.1.
>
> I've cleaned up that patch and expanded it to remove *all* references
> to whrandom, including code that enabled it for use by 'Script
> (Python)'
> and DTML.
>
> It's my opinion that people using 'whrandom' explicitly should know
> what they are doing and won't be harmed too much by the removal of
> this.
>
> Any thoughts?

I'm all for removing deprecated stuff like that, the sticky point is
removing it in places that immediately breaks users' own scripts. You
can't do that within the 2.8 release cycle, sites breaking from one
third-dot release to the next is clearly a problem.

Can we handle the deprecation like other deprecations so far? For the
next release line, meaning Zope 2.9, emit deprecation warnings when
users have scripts with whrandom in Zope, and kill it completely in
2.10. On the other hand, all places where Zope uses whrandom
*internally* that don't have anything to do with user code could
probably be cleaned up right away.

jens

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders

sidnei at enfoldsystems

Sep 17, 2005, 6:14 AM

Post #3 of 3 (4576 views)
Permalink

Re: Issue 1891 [In reply to]

On Sat, Sep 17, 2005 at 11:02:45AM +0200, Jens Vagelpohl wrote:
| I'm all for removing deprecated stuff like that, the sticky point is
| removing it in places that immediately breaks users' own scripts. You
| can't do that within the 2.8 release cycle, sites breaking from one
| third-dot release to the next is clearly a problem.
|
| Can we handle the deprecation like other deprecations so far? For the
| next release line, meaning Zope 2.9, emit deprecation warnings when
| users have scripts with whrandom in Zope, and kill it completely in
| 2.10. On the other hand, all places where Zope uses whrandom
| *internally* that don't have anything to do with user code could
| probably be cleaned up right away.

I'm sure that can be done, probably by making whrandom import lazy in
the context of DTML methods and Python Scripts? (ie: just import when
it's used). I lack the time and knowledge to do that right now though.

--
Sidnei da Silva
Enfold Systems, LLC.
http://enfoldsystems.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads