#13575: Add flexibility when creating exclusion-clauses using 'solve' from
boolean_polynomials.py
-------------------------------------+--------------------------------------
       Reporter:  cosh               |         Owner:  mvngu   
           Type:  enhancement        |        Status:  new     
       Priority:  trivial            |     Milestone:  sage-5.5
      Component:  cryptography       |    Resolution:          
       Keywords:  cryptography, SAT  |   Work issues:          
Report Upstream:  N/A                |     Reviewers:          
        Authors:                     |     Merged in:          
   Dependencies:                     |      Stopgaps:          
-------------------------------------+--------------------------------------

Comment (by malb):

 I've fixed the patch and removed the old patch.

 {{{
  - ``target_variables`` - a list of variables. The elements of the list
 are
    used to exclude a particular combination of variable assignments of a
    solution from any further solution. If ``target_variables`` is ``None``
    all variables appearing in the polynomials of ``F`` are used to
 construct
    exclusion clauses. (default: ``None``)
 }}}

 This isn't correct. If {{{target_variables is None}}} then all variables
 in the ring are used, not only those in {{{F}}}. Should we change that?

 Also, it should be mentioned that {{{target_variables}}} also filters what
 variable value pairs are returned.

 Finally, the commit message should be updated:

 > You are encouraged to write commit messages of the form Trac XXXX:
 <description-goes-here>
 > using the Trac ticket number and then have a concise description, e.g.
 “fix echelon form
 > error” or “add echelon form over finite fields.” Some people also write
 commit messages in
 > the form #xxxx: <description-goes-here>, which is also acceptable. A key
 information to
 > provide in a commit message is the ticket number.

 http://sagemath.org/doc/developer/walk_through.html#chapter-walk-through

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13575#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
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