[Trac-dev] Trac 0.12.3rc1 available for testing

Hello,

The first release of the year is getting nearer, if all goes well
0.12.3 will be released next Sunday, 5th of February 2012.

But before that, we need your help to test the 0.12.3rc1 packages
that we made available today:

  http://trac.edgewall.org/wiki/TracDownload#LatestReleaseCandidate

Should you find anything wrong with these packages (missing
files, test failing on some configuration, anything that doesn't
look satisfying for a release), please drop us a note in the
release coordination ticket:

  http://trac.edgewall.org/ticket/10548

While this is a not-so-exciting maintenance release, we
nevertheless fixed close to 80 tickets, so there is some room for
possible breakage in configurations we didn't test. If you could
have a test run on a copy of your production environment and
report back how it went, that would be very much appreciated!

And here's a last call for the translators: please have a look at
updating your .po files! (we did observe the string freeze... but
we didn't actually extract the messages  so there are at least
2 new messages left to translate if you want to reach 100%).

Enjoy!

[Trac-dev] I'm having trouble groking cursor.execute()

In the original Team Calendar plugin, I find:

         timetable_cursor.execute('SELECT ondate, username, availability '
                                  'FROM %s '
                                  'WHERE ondate >= "%s" AND ondate <= "%s" '
                                  'GROUP BY ondate, username' % 
(self.table_name,

from_date.isoformat(),

to_date.isoformat(),))

which fails in PostgreSQL.  I changed it to:

         timetable_cursor.execute("SELECT ondate, username, availability "
                                  "FROM %s "
                                  "WHERE ondate >= '%s' AND ondate <= '%s' "
                                  "GROUP BY ondate, username" % 
(self.table_name,

from_date.isoformat(),

to_date.isoformat(),))

That is, I reversed the use of single and double quotes.

Clearly neither of these can work on both MySQL and PostgreSQL.  But 
http://trac-hacks.org/ticket/7115#comment:5 says:

   An even simple alternative for the example above is just to pass it

[Trac-dev] pylint integration in PyDev

Hi,

I added chapter "pylint integration" to
DevelopmentWithEclipseAndPyDev, since I find it very useful, but it
didn't work properly at once, see [1].

Still there is always a error on this line:
from pkg_resources import resource_filename

As it is said on stackoverflow [2] you should use #@UnresolvedImport
to avoid that error. But I am wondering if there is not any other
(more global / nicer solution). Has anyone solved that problem?

Thank you,
Franz

[1] http://trac.edgewall.org/wiki/TracDev/DevelopmentWithEclipseAndPyDev#pylintintegration
[2] http://stackoverflow.com/questions/6336882/pylint-doesnt-like-pkg-resources-resource-filename

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Combining GET and POST request

[Trac-dev] Create new ticket vs reopen #9418 (if necessary ;)

Hi all !

My comment posted to #9580 @ t.h.o [1]_ makes me wonder whether it is
convenient to reopen #9418 @ t.e.o
I'll try to be more precise and add further details later , but I just
wanted to know if this is better discussed here in the ML or in the
ticket itself (i.e. #9418 @ t.e.o.)

Thnx in advance !

.. [1] Recursion after installing in Trac 0.13 (dev) <= ThemeEnginePlugin
        (http://trac-hacks.org/ticket/9580#comment:1)

--
Regards,

Olemis

Facebook => http://www.facebook.com/olemis
Twitter => http://www.twitter.com/olemislc (@olemislc)
Blog ES => http://simelo-es.blogspot.com
Blog EN => http://simelo-en.blogspot.com
Quora => http://www.quora.com/olemis
Youtube => http://youtube.com/user/greatsoftw

Featured article : Identificando números primos con expresión regular en Perl
http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-numeros-primos-con.html
Tweet: parsear RT @yudivian Cual es el equivalente correcto en el
español de "parsear"
Follow @olemislc Reply Retweet   15:58 Jan-18
  Get this email app!
Get a signature like this. CLICK HERE.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Call for help in favor of TracTicketsCustomTimeFields

Hello,

I've not been working on ticket t#1942 [1] for a while, but this has not
been due to lack of interest.

Quite the contrary is true: This code has become part of all of my Trac
application. Now I rely on bringing it to Trac core. And I'd certainly
like to obsolete a number of rather awkward attempts to work-around this
limitation in Trac core ASAP too, the most prominent being the
DateFieldPlugin [3].

This is an appeal for mentor-ship since Remy disclosed up-on request on
14-Jan-2012 in IRC channel #trac, that he'd probably not be able to push
this development within the next days/weeks/months but wouldn't mind, if
I'd find someone else to help instead.

First, I've put my Mercurial patch stack to BitBucket tonight [4].

Second, I've to declare, that patches applied cleanly against
trac-r10883, but not anymore. By chance I'd wait for some feedback,
before doing another pass over this.

Third, please feel welcomed to engage. I've granted write access to all
current Trac core developers.

 Think, if you could do something for this development.

I'm no Python professional by no means, will need further guidance on
Trac coding style, especially when it comes to unit and functional
tests. But I'm certainly willing to learn what's required to reach the
goal of this effort.

Not because I can do it all, but I'm confident, that it could be done:
I've started with virtually no Python coding experience 2 years ago.
After some progress my initial patches have been revised and greatly
reworked by Remy. I've done some more work at the end of last December
to adapt to recent changes. Especially Jun's great work to get
configuration and localization for date/time stamps into Trac `trunk`
come to my mind.

It works for me in production - 50+ users and a couple of environments
with hundreds to several thousand tickets, one or two custom time fields
in each. There is even Trac plugin support for custom time fields at
least by Wiki(Ticket)CalendarMacro [5] and  CustomFieldAdminPlugin [6]
(pending patch).

I was rather pessimistic about attempting to resolve such an old ticket.
OTOH I needed it. Simon, Remy and others encouraged me. It can't require
magic to finally bring it home now. Please help.

Looking forward to getting your response.

Sincerely,

Steffen Hoffmann

[1] http://trac.edgewall.org/ticket/1942
[2] http://trac.edgewall.org/wiki/TracTicketsCustomTimeFields
[3] http://trac-hacks.org/wiki/DateFieldPlugin
[4] https://bitbucket.org/hasienda/trac-1942
[5] http://trac-hacks.org/wiki/WikiCalendarMacro
[6] http://trac-hacks.org/wiki/CustomFieldAdminPlugin

[Trac-dev] Regression by 10892 for branches/0.12-stable

Hello,

it has been brought to my attention by a request in IRC #trac today,
that a user is experiencing following issue with report 6 in default
configuration on latest stable 0.12:

'My Tickets' is shown _after_ 'Active Tickets'

Before the changeset it was ok. Work-around is to rename groups or use

ORDER BY (COALESCE(owner, '') = '$USER') DESC, ...

instead of

ORDER BY (owner = '$USER') DESC, ...

Hint: The underlying query seem to not get the DESC rule, when the
column is added the new way, as SQL logging reveals ([2] last line).
Well, looks like there is simply no way to attach a 'DESC' to the
__group__ directive, right?

Since I'm not a SQL guru, I start with discussion here rather than
filing a ticket right-away.

Sincerely,

Steffen Hoffmann

[1] http://trac.edgewall.org/changeset/10892
[2] http://pastebin.com/G3criDRQ

[Trac-dev] Release 0.12.3rc1

Hello,

0.12.3 is a long due release, we have nearly everything ready, but
not quite.

== Prepare ChangeLog

I've started it (see the ChangeLog wiki page on t.e.o). There's
room for a few more items, so don't hesitate to suggest some.

== Sync the TracGuide

I've started this as well. If people could review the additions
and spot gross mistakes if any, please tell me (or better,
directly make the change in the Wiki, as I'll do another pass at
getting the last changes from t.e.o just before making the final
release).

See http://trac.edgewall.org/log/cboos?rev=trac-guide-0.12

== Last call for i18n!

Translators from all around the world, this is you last chance to
reach 100% coverage for Trac 0.12.3! You still have a good week
left.

== Tickets left

=== For Jun (jomae)

   - #10121 UnicodeEncodeError: 'ascii' codec can't encode
            character u'\xdc' in position 5: ordinal not in
            range(128)

    I've summarized on this ticket what's left to be done for it:
    2 small patches to apply, AFAICT.

	
=== For me

   - #9976 Permission check of Repository Browser does not work

     Need to go carefully through this one, should be doable this
     WE.  Goes with #10208 anyway.

=== For Felix (fschwarz)

    - #1013 wrong German translation of 'Annotate' in source browser	

      That one should really be easy - there are plenty of
      suggestions in the ticket and the last one in comment:27 looks
      good (kidding, I don't speak German  ).

=== For Rémy (rblank)

   - #10208 AuthzSourcePolicy does not conform to mod_authz_svn rules	

     Probably goes with #9976. We're on it 

My current target is a 0.12.3rc1 release for Sunday evening.
 From that point, we'll encourage people to test it and if no
regression from 0.12.2 is found in a one week period, we'll make
the release (+ eventually the i18n updates which came in the
meantime).

As usual, if for some reason a large fix is needed, we'll extend
the testing period by one more week.

-- Christian

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Can't deepcopy() a ticket?

In my TracPM module, I want to give schedulers free reign over ticket 
data.  I used to do:

     def computeSchedule(self, options, tickets):
         # Convert list to dictionary, making copies so schedule can
         # mess with the tickets.
         ticketsByID = {}
         for t in tickets:
             ticketsByID[t['id']] = t

         # Schedule the tickets
         self.scheduler.scheduleTasks(options, ticketsByID)

but changes made by the scheduler were carried back to the caller.  I 
started with:

     def computeSchedule(self, options, tickets):
         # Convert list to dictionary, making copies so schedule can
         # mess with the tickets.
         ticketsByID = {}
         for t in tickets:
             ticketsByID[t['id']] = copy.copy(t)

         # Schedule the tickets
         self.scheduler.scheduleTasks(options, ticketsByID)

         # Copy back the schedule results
         for t in tickets:
             for field in [ 'calc_start', 'calc_finish']:
                 t[field] = ticketsByID[t['id']][field]

But the ticket attritbutes weren't copied, only the references to them. 
  I tried but deepcopy() but that gives:

   File "build/bdist.linux-x86_64/egg/tracjsgantt/tracjsgantt.py", line 
558, in _add_tasks
     self.pm.computeSchedule(options, self.tickets)
   File "build/bdist.linux-x86_64/egg/tracjsgantt/tracpm.py", line 566, 
in computeSchedule
     ticketsByID[t['id']] = copy.deepcopy(t)
   File "/usr/lib/python2.6/copy.py", line 162, in deepcopy
     y = copier(x, memo)
   File "/usr/lib/python2.6/copy.py", line 255, in _deepcopy_dict
     y[deepcopy(key, memo)] = deepcopy(value, memo)
   File "/usr/lib/python2.6/copy.py", line 189, in deepcopy
     y = _reconstruct(x, rv, 1, memo)
   File "/usr/lib/python2.6/copy.py", line 322, in _reconstruct
     args = deepcopy(args, memo)
   File "/usr/lib/python2.6/copy.py", line 162, in deepcopy
     y = copier(x, memo)
   File "/usr/lib/python2.6/copy.py", line 235, in _deepcopy_tuple
     y.append(deepcopy(a, memo))
   File "/usr/lib/python2.6/copy.py", line 189, in deepcopy
     y = _reconstruct(x, rv, 1, memo)
   File "/usr/lib/python2.6/copy.py", line 323, in _reconstruct
     y = callable(*args)
   TypeError: __init__() takes exactly 3 arguments (1 given)

Is this a known restriction of some Trac classes?  A bug?  My misuse of 
deepcopy()?

This is in Trac 0.11.6.

Any insight appreciated.

                                                  Chris
-- 
Christopher Nelson, Software Engineering Manager
SIXNET - Solutions for Your Industrial Networking Challenges
331 Ushers Road, Ballston Lake, NY  12019
Tel: +1.518.877.5173, Fax: +1.518.877.8346 www.sixnet.com

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Trac account - where to register?

Hi all,

I would like to have an Trac account, because it's nasty to enter
always my email address to avoid being anonymous. But I haven't found
any page on Trac where I can register for an account - have I missed
it?

Thanks,
Franz

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Trac -> Software Freedom Conservancy?