[sage-devel] Re: Writing a piece about import in the developers guide.

2011-08-30 Thread leif
On 31 Aug., 04:15, leif wrote: > On 31 Aug., 03:21, Benjamin Jones wrote: > > Are there any tools for automating the process of finding out which imports > > aren't used in a large module? > > See for examplehttp://trac.sagemath.org/sage_trac/ticket/11749(h/t > Robert B.). P.S.: I've written a

[sage-devel] Re: Writing a piece about import in the developers guide.

2011-08-30 Thread leif
On 31 Aug., 03:21, Benjamin Jones wrote: > On Wed, Aug 31, 2011 at 1:09 AM, Volker Braun wrote: > > +1 for any tool to reduce/simplify the number of imports. Everybody adds > > imports if something is missing, but nobody takes out imports after > > rewriting a module. Its not hard to find unused

[sage-devel] Re: Writing a piece about import in the developers guide.

2011-08-29 Thread Maarten Derickx
Thanks for the usefull replies till so far. I've decides to keep the results of this discsion summarised on http://wiki.sagemath.org/import I hope that other people have the same interpretation of the arguments till so far as me. If not feel free to edit the wiki. I want to mention again that c

[sage-devel] Re: Writing a piece about import in the developers guide.

2011-08-29 Thread Eviatar
http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Import_Statement_Overhead has some good information. On Aug 29, 5:33 pm, Robert Bradshaw wrote: > On Mon, Aug 29, 2011 at 4:21 PM, William Stein wrote: > > On Mon, Aug 29, 2011 at 2:56 PM, Maarten Derickx > > wrote: > >> At the last sage-d