Basically there are two popular approaches: either pip + requirements.txt or buildout + versions.cfg.
Googling those should give you a good starting point :-) Sent from a phone, please excuse the brevity. On 05.08.2013, at 16:11, wilk <w...@flibuste.net> wrote: > Hi, > > I'm testing pyramid with success and now would like to deploy it in > production. To now i only used debian apt to install and upgrade my > packages, i wonder how it works with virtualenv ? > > I mean, how to make an upgrade just for security, without taking the > risk of a non compatible upgrade of one package ? > > In the source of pyramid i see that the packages required are >=, but > what will append if one of them release a new version not compatible > with the current pyramid ? > > Thanks to give me some keys... Sorry that it's not directly related to > pyramid. > > -- > William Dodé > Informaticien Indépendant > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
