[py3porters-devel] Pylons and snapshot.debian.org

[Morten Linderud]

Semi-reated another thread. But i think it would be neat if we could get everything under
a public github org for this project. Better overview of all porting projects.
Might be easier for new people to contribute aswell.


On 04/19/2015 07:51 PM, Matt Singleton wrote:
> Cool. I'm quite fond of Flask myself.
> 
> I'm guessing we'll need to clone the repo somewhere that we can collaborate since I'm guessing many of us (me!) won't have direct commit privileges.
> 
> Bitbucket? I'll go ahead and set it up if y'all are cool with that.
> 
> Matt
> 
>> On Apr 19, 2015, at 1:21 PM, Justin Alan Ryan <justin at angelops.net <mailto:justin at angelops.net>> wrote:
>>
>> +1 for Flask as well, was only offering pyramid insight.  I concur that both Pyramid and Django are too heavy, though both could probably be used in some lightweight manner.  This app appears to be
>> mostly about custom routes and search, Flask should be great.
>>
>>> On Apr 19, 2015, at 10:08 AM, Johannes <j_schn14 at uni-muenster.de <mailto:j_schn14 at uni-muenster.de>> wrote:
>>>
>>> +1 for flask. Django seems to much overhead.
>>>
>>> Bg,
>>> Johannes
>>>
>>> Von meinem Sony Xperia™-Smartphone gesendet
>>>
>>>
>>>
>>> ---- Matt Singleton schrieb ----
>>>
>>> Cool, that was my assessment as well.
>>>
>>> I got some responses on the debian-snapshot list. They seem happy to have us do this work however we see fit, but they suggested that Pyramid isn't really used elsewhere in Debian and that Flask or
>>> Django are the preferred web frameworks.
>>>
>>> For a project like this, I'd say that Flask is probably the better fit. Its pluggable design is a lot closer to Pylons and will probably let us re-use a lot more code. If we went with Django, we'd
>>> have extra work porting templates and DB code into its templating and ORM languages. My experience with Django is all pre-1.0, though, so if it's become more modular since then, my argument could
>>> be moot.
>>>
>>> Matt
>>>
>>> > On Apr 18, 2015, at 4:34 PM, Justin A Ryan <bitmonk at icloud.com <mailto:bitmonk at icloud.com>> wrote:
>>> >
>>> > As I suspected, the guts of the actual archive is mostly dynamic routes.  It looks like a simple app, obviously if original authors / past maintainers want to help, that would be awesome.
>>> >
>>> >> On Apr 18, 2015, at 11:19 AM, Matt Singleton <matt at xcolour.net <mailto:matt at xcolour.net>> wrote:
>>> >>
>>> >> I'm digging around the code a bit here: http://anonscm.debian.org/cgit/mirror/snapshot.debian.org.git/
>>> >>
>>> >> Don't see anything in the bug tracker about moving away from Pylons. I'm going to reach out to the maintainer(s) to see how they'd like to be involved in the project.
>>> >>
>>> >> Matt
>>> >>
>>> >>> On Apr 18, 2015, at 2:03 PM, Justin A Ryan <bitmonk at icloud.com <mailto:bitmonk at icloud.com>> wrote:
>>> >>>
>>> >>> I’m familiar with Pyramid (formerly Zope) and would be willing to look into this.
>>> >>>
>>> >>>> On Apr 18, 2015, at 10:59 AM, Matt Singleton <matt at xcolour.net <mailto:matt at xcolour.net>> wrote:
>>> >>>>
>>> >>>> Hi all,
>>> >>>>
>>> >>>> Looking through the lovely SVG, I noticed that snapshot.debian.org <http://snapshot.debian.org/> metapackage relies on Pylons, which seems really unlikely to get a py3 port given that it's in
>>> maintenance mode and all the active development is happening on Pyramid now.
>>> >>>>
>>> >>>> I wonder if the snapshot maintainers already have any plans underway to migrate to a maintained web framework? I've worked with Pylons before, but I've never done a Pyramid migration. My
>>> understanding is that it amounts more or less to a rewrite.
>>> >>>>
>>> >>>> Matt
>>> >>>> _______________________________________________
>>> >>>> py3porters-devel mailing list
>>> >>>> py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>>> >>>> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>> >>>
>>> >>
>>> >> _______________________________________________
>>> >> py3porters-devel mailing list
>>> >> py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>>> >> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>> >
>>> >
>>> > _______________________________________________
>>> > py3porters-devel mailing list
>>> > py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>>> > https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>>
>>>
>>> _______________________________________________
>>> py3porters-devel mailing list
>>> py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>>> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>> _______________________________________________
>>> py3porters-devel mailing list
>>> py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>>> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>>
>> _______________________________________________
>> py3porters-devel mailing list
>> py3porters-devel at lists.alioth.debian.org <mailto:py3porters-devel at lists.alioth.debian.org>
>> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
> 
> 
> 
> _______________________________________________
> py3porters-devel mailing list
> py3porters-devel at lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel
>