I've been waiting for a green light to resume my work on it. I'm not aware
of any other activity.
On Thursday, December 29, 2016 at 7:12:43 PM UTC-5, i...@iprcom.com wrote:
>
> I may be jumping the gun a bit as a 1.3.2 (jinga2) tag hasn't been
> declared yet, but what is the state of the
Thanks, I upgraded https://code.djangoproject.com and don't see any issues
so far.
On Monday, September 19, 2016 at 5:55:26 PM UTC-4, RjOllos wrote:
>
>
>
> On Monday, September 19, 2016 at 4:46:19 AM UTC-7, Tim Graham wrote:
>>
>> Hi Ryan,
>>
>> Do you
Hi Ryan,
Do you figure it's relatively safe to test in production? We don't have a
test environment for Django.
If we had to roll back to 1.0.x would it be feasible?
Do you have a planned date in mind for the final release (assuming all
reported bugs can be fixed in a timely manner)?
Thanks,
nd search for "Pull
requests:" The code that generates that is
https://github.com/django/code.djangoproject.com/blob/669bc946bdd378fa6e086acb3e8af80bfd319eb9/trac-env/htdocs/tickethacks.js#L99-L208
On Tuesday, August 23, 2016 at 8:56:44 PM UTC-4, RjOllos wrote:
>
>
>
> On Tuesday, Au
/contributing/committing-code/#handling-pull-requests
On Tuesday, August 23, 2016 at 4:41:54 PM UTC-4, RjOllos wrote:
>
>
>
> On Tuesday, August 23, 2016 at 1:16:05 PM UTC-7, Tim Graham wrote:
>>
>> Hi,
>>
>> I wonder if there's any objection among the Trac team
Hi,
I wonder if there's any objection among the Trac team for moving toward
accepting pull requests on GitHub? Is there a reason you prefer attaching
patches to tickets instead? Django used to only accept patches that way,
but since we started accepting pull requests some years ago, anytime
ld version of Python, are
you likely to want the latest and greatest Trac / Django / ?
On Wednesday, March 16, 2016 at 5:51:25 AM UTC-4, RjOllos wrote:
>
>
>
> On Tue, Mar 15, 2016 at 5:30 PM, Tim Graham <timog...@gmail.com
> > wrote:
>
>> If Python 3 support for Tr
Hi Ryan, could you give an update on the release of Trac 1.2? I see some
discussion on https://trac.edgewall.org/ticket/12120 but a high level
update to this mailing list would be great. If you list the remaining
tasks, maybe some other people would help chip in if you're overloaded.
Thanks!
If Python 3 support for Trac won't be released until 2017, I think there's
no need to support Python 3.3 which is end-of-life in September 2017
(already the most recent release of Django supports Python 3.4+, for
example). I think Python 3.5+ would be a fine target, but if people feel
that
>From a familiarity standpoint, I know that Django developers would
appreciate this change as Jinja2 is similar to the Django Template Language
and we recently added native support for Jinja2 in Django.
On Thursday, February 4, 2016 at 8:14:52 PM UTC-5, cboos wrote:
>
> Hello,
>
> Inspired by
Sounds good to me. You wouldn't intentionally break support in already
released versions of Trac, just no longer fix new issues, correct?
As a data point, Django 1.9 (released Dec 1, 2015) switched to jQuery 2.x
which has the same API as jQuery 1.x, but does not support Internet
Explorer 6, 7,
+1 for the guideline change. Django's Trac adds checkboxes on each ticket
for "Has patch", "Patch needs improvement", "Needs documentation", "Needs
tests". That makes it easy to construct queries to find patches that are
ready for review ("Has patch" and "no" for the other 3 criteria).
On
Publishing prereleases to the Edgewall server works for me.
Thanks for the upgrade tips and update on the timetable for the release.
On Tuesday, September 29, 2015 at 2:36:16 PM UTC-4, RjOllos wrote:
>
> On Tuesday, September 29, 2015 at 10:48:11 AM UTC-7, Tim Graham wrote:
>>
>&g
I was wondering if there are any plans to make prereleases (e.g.
alpha/beta/release candidate) available on PyPI for the Trac 1.2 release so
it can be more easily tested before a final release? For Django, we figured
out that if you upload a wheel file only for prereleases, no version of pip
or to vendor
a copy of it. Currently I have it as a dependency.
On Sunday, July 19, 2015 at 2:06:41 PM UTC-4, RjOllos wrote:
On Sun, Jul 19, 2015 at 10:56 AM, Tim Graham timog...@gmail.com
javascript: wrote:
I put together a few initial patches (some is rebased from Jun's work)
which should be fine
I put together a few initial patches (some is rebased from Jun's work)
which should be fine to merge now, even if Python 2.6 is still supported.
https://github.com/timgraham/trac/pull/1
Is attaching patches to Trac tickets the best way to submit this work? That
workflow seems painful from a
I'm a developer on the Django team and we use Trac as our bug tracker. I'm
interested in moving our infrastructure to Python 3, but need Trac to
support Python 3 in order to do so. Django supports Python 2 and 3, so I
have some experience in maintaining a code base that supports both. I
Thanks for the feedback. As suggested, I'll try to work on some smaller
patches at first to get familiar with contributing and wait until 1.2 is
released before submitting any major changes.
Looking at Jun's work, it seems he is more or less reimplementing a subset
of the functionality that
18 matches
Mail list logo
