Just outline a few choices for the core team. First what is the standard way to package projects, eggs, sdist tar, or something else. I had used a egg because I had problems with sdist but if someone else knows how to get sdist working with all media files that would be a better option.
Should clone_project install project requirements.txt with pip by default? I recommend having a option to turn off this behaviour if you want to install requirements manually. Should "pinax-project" be the package keyword over a trove classifier? Being able to browse pypi's categories and see pinax projects would be great but until more people start using projects and their usage becomes clearer using a keyword makes sense. If your happy with the concepts and agree with how its working the only file that needs to be changed is clone_project.py. Right now my version is in proof of concept mode but its easy for me to fix if i know you want to use it. You do not need to update any of your existing projects as they will all still work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Pinax Core Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pinax-core-dev?hl=en -~----------~----~----~----~------~----~------~--~---
