Billions you say....! I'm all ears, surely there are workarounds but the right one will depend on what on earth you are doing with billions of references. a) Some would say you should never ever use more than one reference, the trick is usually within the multiplication itself, as in what works one 3 refs will work on 300 refs. if what you are doing is scalable from the ground up. b) This gets trickier when you start treating billions though and you will need to parse this pretty efficiently in order not to wait a lifetime for results, the big win there will presumably end up being something as simple as the difference between range and xrange, or even your choice in reader. c) Will need a workflow example in order to provide a more practical answer but if it helps make sure to treat each as one and disregard sloppyness and marginal overlooked things which don't matter when you only treat a few, cheapest thing in the book would be creating a bunch of dummy locators as placeholders while you import this so the clash never occurs then script a controlled merge based on the result, but that's no good if you are iterating over more than a few hundred...
* To quote Tim Peters;* >>> import this The Zen of Python, by Tim Peters [...] Namespaces are one honking great idea -- let's do more of those! >>> -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/a58d7e28-63ae-4b6c-99b9-6a96e9093d03%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
