Old Discussion: Python Implementation? (Bugzilla:Languages)

[Stephanie Daugherty]

I'm not sure honestly what the desirability of a port would be at this
stage, but I'm guessing if it happened, it would be in order to bring it in
line with the same frameworks and standards that other Mozilla web projects
such as AMO follow... ie ( https://github.com/mozilla/playdoh)

Might be interesting to see... but really can't say what the demand for it
would be.



On Wed, Apr 24, 2013 at 4:27 PM, Matthew Bogosian <mtb19 at columbia.edu>wrote:

> I have been casually fantasizing about reimplementing Bugzilla in Python.
> I am aware of the Bugzilla:Languages page<https://wiki.mozilla.org/Bugzilla:Languages> (and
> corresponding discussion page<https://wiki.mozilla.org/Bugzilla_Talk:Languages>),
> but note that it hasn't undergone any revisions for over four years, and a
> lot has changed since then. For example, many of the "Cons" listed under
> Python may have been addressed in later releases, especially v3.***
>
> If I were to make a sincere effort, I would concentrate on producing a
> faithful replica of the stable branch (with refactoring where appropriate
> to bridge any gap between the two languages/architectures/libraries such as
> template engines). In other words, I would not make any attempt to fix
> design issues or add new features in order to preserve as much value of the existing
> knowledge base<https://bugzilla.mozilla.org/describecomponents.cgi?product=Bugzilla> as
> possible. Obviously competent help would be greatly appreciated, as this
> would not be my day job.
>
> However, I am reluctant to embark on such an undertaking without having
> some assurances that the effort would be useful, or that it would be a
> realistic candidate for becoming the adopted standard (assuming I do my
> part to competently comport with existing bugzilla philosophies, standards,
> and conventions wherever possible).
>
> I have two questions:
>
> 1) If I was magically done today (with some approval of validity by
> existing developers), what is the likelihood that a Python implementation
> would (sometime over the following 6-12 months) be adopted as the primary
> architecture? I.E., how much inertia can realistically be attributed to
> Perl as an architecture (including comfort, emotional attachment,
> institutional knowledge, etc.)?
>
> 2) Assuming a 60%-or-better chance of adoption, does any onlooker have the
> desire and ability to assist (specifically with a Python "port")?****
>
> Thanks, and I look forward to any discussion.
>
>
>     --Matt
>
>
> *** This e-mail is not directly intended to trigger a debate of tradeoffs,
> but such a debate may be necessary before my questions may be meaningfully
> answered. I'm guessing the biggest hurdle Python faces is a lack of a
> built-in "taint" mode which would necessitate the adoption of different
> coding standards/conventions. (There is an academic project<http://revista.python.org.ar/1/html-en/taint.html> which
> claims to provide similar functionality, but I've never used it, and I
> don't know anything about its performance.)
>
> I know that the subject has been briefly broached several<https://lists.bugzilla.org/cgi-bin/mj_wwwusr?user=ossipov@inf.fu-berlin.de&passw=&list=developers&brief=on&func=archive-get-part&extra=200210/67>
>  times<https://lists.bugzilla.org/cgi-bin/mj_wwwusr?user=benwei@veriwave.com&passw=&list=developers&brief=on&func=archive-get-part&extra=200903/20> on
> this list, but not substantively as far as I can tell.
>
> In the interest of full disclosure, I have more experience with Python
> than Perl. I *like* Python. I do not like Perl. For the sake of this
> discussion, please consider this a disclosure of my emotional biases and
> attribute no weight to them.
>
> **** Before answering, you should be aware that this would be a substantial
> undertaking <http://www.ohloh.net/p/bugzilla>. I say this only because I
> am trying to realistically gauge sincere interest.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20130424/493bc68d/attachment.html>