#5106: [with patch, positive review, needs rebase] preparse bug with time and
generator assignment naming
----------------------------+-----------------------------------------------
 Reporter:  was             |        Owner:  was     
     Type:  defect          |       Status:  new     
 Priority:  major           |    Milestone:  sage-3.3
Component:  user interface  |   Resolution:          
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by mabshoff):

  * summary:  [with patch, positive review, needs rebase review] preparse
              bug with time and generator assignment naming
              => [with patch, positive review, needs rebase]
              preparse bug with time and generator assignment
              naming

Comment:

 Hi Robert,

 this patch is either not the right one or something else went wrong since
 it does not apply:
 {{{
 mabsh...@sage:/scratch/mabshoff/sage-3.3.rc1/devel/sage$ patch -p1 --dry-
 run < 5106-preparse-gens.patch
 patching file sage/misc/preparser.py
 Hunk #7 FAILED at 739.
 Hunk #8 FAILED at 825.
 2 out of 8 hunks FAILED -- saving rejects to file
 sage/misc/preparser.py.rej
 }}}

 At SD 12 there were some issues merging the preparser patches including
 #4405, so it sounds like a very good idea to rebase this against 3.3.rc1
 which will be out by the time you get this email on Monday :).

 Cheers,

 Michael

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5106#comment:11>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to