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 imports, as a random example
> sage/rings/polynom
+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 imports, as a random example
sage/rings/polynomial/polynomial_rational_flint.pyx imports is_Polynomial
but
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-days there were some people working on making sage start up
>> faster. I think it would be nice to have a short piece in the documentation
>> about "best practices
On Mon, Aug 29, 2011 at 2:56 PM, Maarten Derickx
wrote:
> At the last sage-days there were some people working on making sage start up
> faster. I think it would be nice to have a short piece in the documentation
> about "best practices for importing" so that all sage developers have a
> reference
At the last sage-days there were some people working on making sage start up
faster. I think it would be nice to have a short piece in the documentation
about "best practices for importing" so that all sage developers have a
reference point on how to deal with these difficulties.
Before I can w
