Changes between Initial Version and Version 2 of Ticket #2180


Ignore:
Timestamp:
Feb 24, 2008, 12:26:35 AM (15 years ago)
Author:
Michael Abshoff
Comment:

I have seen this issue before and I believe the new caching code is at fault, so it should be assigned to Bobby Moretti. I have speculated that if you patch in a new file the time stamp of the new file is too old for the precomputed hashes to be recomputed.

Cheers,

Michael

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2180

    • Property Owner changed from William Stein to Bobby Moretti
    • Property Component changed from algebraic geometry to packages

  • Ticket #2180 – Description

    initial v2  
    11In 2.10.2.alpha0, there appears to be a small problem with the cython skipping
    2 step.  To illustrate the bug:
    3 1)  Start with a 2.10.2.alpha0 (with padic import patch) which is built
     2step.  To illustrate the bug:
     31)  Start with a 2.10.2.alpha0 (with padic import patch) which is built
    44up-to-date
    5 2)  Add a new patch which adds a new .pyx file
    6 3)  sage -br
    7 4)  The bug is that you get a message like:
     52)  Add a new patch which adds a new .pyx file
     63)  sage -br
     74)  The bug is that you get a message like:
    88building 'sage.rings.polynomial.multi_polynomial_factor' extension
    99error: unknown file type '.pyx'
    … …  
    1414This appears to arise because the new .pyx file is not in the cache and so the
    1515build optimizer believes that there are no .pyx files to build and just lets
    16 the ordinary disttools do their work.  Of course, the ordinary disttools
     16the ordinary disttools do their work.  Of course, the ordinary disttools
    1717don't know what to do with .pyx files.
    1818
    1919A work-around is to 'touch' a .pyx file anywhere in the tree which is already
    20 in the cache.  A build after the touch will build the touch'ed file and the
     20in the cache.  A build after the touch will build the touch'ed file and the
    2121new file.