1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Custom Query (17 matches)


Show under each result:

Ticket Summary Created Modified Status Resolution Milestone Description
#200 Unable to create nillable instances of classes that require constructor arguments 11 months 9 months closed fixed PyXB 1.2.3 See https://sourceforge.net/p/pyxb/discussion/956708/thread/4647234c/ xs:dateTime inherits from datetime.datetime so attempts to create nil instances are rejected by the superclass constructor. This suggests we need a dummy class to produce instances of nil element values where there is no such thing as a nil instance of the type to which the value must conform.
#201 PluralBinding insert misbehavior 9 months 9 months closed fixed PyXB 1.2.3 See: https://sourceforge.net/p/pyxb/discussion/956708/thread/39867245 Looks like insert improperly assumes its second argument is an iterable when in fact it is a single value.
#216 attribute values bypass lexical-to-value conversion 7 months 7 months closed fixed PyXB 1.2.3 See: https://sourceforge.net/p/pyxb/discussion/956708/thread/6978e196
#204 fixed elements improperly create non-empty default 9 months 9 months closed fixed PyXB 1.2.3 See: https://sourceforge.net/p/pyxb/discussion/956708/thread/b6c1884d When #99 was fixed the reset value for an element was changed to the default values of its element content; prior to that element content was reset to `None`. The new reset doesn't take into account that a non-empty element may not be valid.
#202 attributes improperly inherit default namespace 9 months 9 months closed fixed PyXB 1.2.3 See: https://sourceforge.net/p/pyxb/discussion/956708/thread/b9d221e0/ [http://www.w3.org/TR/REC-xml-names/#scoping-defaulting Namespaces in XML 1.0] contains the following somewhat contradictory direction: Default namespace declarations do not apply directly to attribute names; the interpretation of unprefixed attributes is determined by the element on which they appear. ... The namespace name for an unprefixed attribute name always has no value. PyXB 1.2.2 applies default namespace rules to attributes when it should not.
#215 pyxb 1.3: clean up exception interface 7 months 7 months new -- PyXB 1.3.0 Some fields are attributes, some are properties, some are private variables with accessor functions. Let's be consistent for the next major release.
#211 invalid element with simple type misdiagnosed as mixed content error 7 months 7 months closed fixed PyXB 1.2.3 The 1.2.2 test for #189 includes a second element which is not accepted by the content model, but the diagnostic generated says the reason is that there is mixed content present. This is because simple elements are implicitly converted to text to satisfy the content model if mixed or simple content is allowed.
#207 unpickle failure for xsd:duration 7 months 7 months closed fixed PyXB 1.2.3 The PyXB duration class gets pickled as its underlying Python datetime.timedelta class, but the wrapper constructor fails to recognize the multiple arguments passed to it causing an exception when reading the value from a pickled file such as a binding archive.
#213 complex type with simple content should not fail by assert when content missing 7 months 7 months closed fixed PyXB 1.2.3 The complexTypeDefinition todom method raises an assert if simple content value is missing. It should raise a validation error instead.
#214 add facility to replace value of complex type with simple content 7 months 7 months new -- PyXB 1.3.0 There are all those attributes already configured properly, and there's the copy module which can create a duplicate; why can't we just change the underlying value?
#210 re-examine --wsdl-location in pyxbgen 7 months 7 months closed fixed PyXB 1.2.3 Whatever this is it seems to have redundant code.
#205 misleading ElementChangeError message 9 months 9 months closed fixed PyXB 1.2.3 When an attempt is made to set an element with fixed value "true" to the Python value False, an ElementChangeError is passed the rejected value, and when converted to a string displays it as: {{{ pyxb.exceptions_.ElementChangeError: Element Yes has fixed content False }}} which would naturally be interpreted to say the element's fixed content is False, making one wonder why the assignment was rejected.
#208 base type attribute qnames resolved in wrong namespace context 7 months 7 months closed fixed PyXB 1.2.3 When generating bindings for a type where the qname in the extension or restriction base attribute is not in scope at the containing complex type tag, the resolution of the type fails.
#203 toxml can generate xml with invalid element tag without warning 9 months 7 months closed fixed PyXB 1.2.3 When toxml() is asked to generate an XML document for a type instance that has no associated element it can substitute the type name. It should at least emit a warning, and arguably raise an exception. See: https://sourceforge.net/p/pyxb/discussion/956708/thread/1204a2fa/
#206 dateTime.aslocal does not work for non UTC datetimes 8 months 7 months closed fixed PyXB 1.2.3 Whenever a pyxb.binding.datatypes.dateTime instance contains a timezone different from UTC, aslocal return an incorrect date. Consider the following (with local timezone = +02:00): {{{ >>> import pyxb.binding >>> pyxb.PreserveInputTimeZone(True) True >>> print pyxb.binding.datatypes.dateTime("2013-08-30T11:56:45+04:00").aslocal() 2013-08-30 13:56:45+02:00 }}} Correct date should be 2013-08-30 '''09:56:45+02:00''' A simple check in aslocal method before replacing tzinfo should do the trick.
#212 simplify access to mixed content 7 months 7 months closed fixed PyXB 1.2.3 With content() deprecated and orderedContent() wrapping mixed content in an instance of NonElementContent, it's a pain to simply dump the catenated non-element content of an element. Provide a better interface. Do this without intruding another reserved symbol on _TypeBinding_mixin instances.
#217 Support XML Schema 1.1 7 months 7 months new -- PyXB 1.3.0 http://www.w3.org/TR/xmlschema11-1/ It's been out for over a year, and doesn't seem too frightening. This may also be an opportunity to use bindings instead of the hand-maintained parser for ``http://www.w3.org/2001/XMLSchema``, allowing diagnostics of schema errors as well as document errors.
Note: See TracQuery for help on using queries.