Are there any disadvantages about using eggs through easy-install
compared to the "traditional" packages/modules/libs?
A common question I get about cutting eggs is, “why would I want to do this?” The most common answer is that most breeders simply can't wait for the eggs to hatch on their own. It is a time-sensitive decision for ball python snake owners to make.
Cutting eggs (pipping) stops weaker baby ball pythons from drowning inside their eggs. The cutting process should be done after 50 days. Done correctly, it will result in more successful hatches. But if you aren't experienced or make a mistake, you could cut the snake.
A “Python egg” is a logical structure embodying the release of a specific version of a Python project, comprising its code, resources, and metadata. There are multiple formats that can be used to physically encode a Python egg, and others can be developed.
One (potential) disadvantage is that eggs are zipped by default unless zip_safe=False
is set in their setup()
function in setup.py
. If an egg is zipped, you can't get at the files in it (without unzipping it, obviously). If the module itself uses non-source files (such as templates) it will probably specify zip_safe=False
, but another consequence is that you cannot effectively step into zipped modules using pdb
, the Python debugger. That is, you can, but you won't be able to see the source or navigate properly.
Using eggs does cause a long sys.path
, which has to be searched and when it's really long that search can take a while. Only when you get a hundred entries or so is this going to be a problem (but installing a hundred eggs via easy_install is certainly possible).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With