#2226: Release TG2 to pypi
--------------------------+-------------------------------------------------
 Reporter:  jorge.vargas  |        Owner:  mramm 
     Type:  defect        |       Status:  new   
 Priority:  highest       |    Milestone:  2.0rc1
Component:  TurboGears    |      Version:  trunk 
 Severity:  normal        |   Resolution:        
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by jorge.vargas):

 Replying to [comment:5 mramm]:
 > Also it will do no good to have the TG2 egg in pypi if their
 dependencies aren't available in at least some form.  I think this is now
 the case, but we should test it.

 what dependencies?
 {{{
 requirements = open('b6requirements.txt').readlines()

 for package in requirements:
     print 'Searching for ' + package,
     name,version = package.split('==')

     import urllib
     result = urllib.urlopen('http://pypi.python.org/pypi/%s/%s' %
 (name,version)).read()
     if result == 'Not Found\n\n':
         print name,version,'missing',
     else:
         print name,version,'ok',
     print
 }}}

 requrements file from #2182

 That only shows PEAK-rules and prioritized-methods 0.2.1

  - http://pypi.python.org/pypi/PEAK-Rules
  - http://pypi.python.org/pypi/prioritized-methods

 the first is a bug in the name of the pypi package, the second is not
 released, which I believe it's alberto's stuff used by TurboJson, #2212
 again :)

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2226#comment:7>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to