As soon as you post or find a counter argument in favour of Trump that isn ' t just Hillary did worse ahhhh then sure thing . <| sep |> Easily done if you can justify the cost exactly as per your other comment . <| sep |> Funny how I ' d submitted this earlier . Let ' s see how long this sub let ' s it stay up . <| sep |> My school had one for awhile . After a few months of unserviceable problems , we attempted a return . MakerBot , being shady as they are , gave us hell and wouldn ' t let us return it . We threatened to get our school lawyer involved , and they gave us our money back . We ' ve got Ultimaker 2 ' s now , and they ' ve been a dream to own and operate . Love those Ultimakers . <| sep |> Is importing actually a problem for most cases though ? Will it affect anything other than startuptime and memory usage ? I am mostly using Python for web development , where neither is a huge issue . Is it really an issue in other parts of the ecosystem ? The proposed solution of delaying imports seems a bit error prone . Imagine a long running report script that crashes at the end because it turns out you forgot to install termcolor or some other output prettifier . I am a bit confused by Well , the most standard way is not putting the imports in the toplevel scope . Just use local imports and try to keep your public API simple simple APIs are much better than complex APIs Does it matter if I have the imports deeper down in the library when I import from those files in my top level scope which I assume is my main init . py ? Will dependencies not be imported anyway ?